Back to the shelf

006

Visitor Management System

A visitor and security system for pharma facilities: pre-registration, check-in, badges, check-out, and a complete audit trail.

Launched · Started July 2025 · System · Vibe-Coded

That's the whole thing.

The site's sound is off. The narration still plays.

This reading didn't load. The transcript is below.

Read the transcript

A pharmaceutical facility cannot afford uncertainty about who is inside. Compliance, security, and accountability all rest on a clear record. And the clear record was a paper logbook.

I built this for the security department at Venus Remedies. A digital system covering the full visitor lifecycle: pre-registration and check-in, badge generation, and check-out. Role-based access for the security team. Support for several manufacturing units. A complete audit trail that holds up when it has to.

I started it in July twenty twenty-five. One of the first handful of things I vibe-coded with AI. Built on Laravel and PHP. It is launched.

If accountability interests you, follow along with how I build.

Narrated in my own cloned voice, generated with ElevenLabs v4.

A pharma facility can’t afford uncertainty about who’s inside. The record was a paper logbook.

I built this for the security department at Venus Remedies, a pharmaceutical company with several manufacturing units. Compliance and traceability matter in that environment, and a logbook gives you neither. This replaced it with a digital system that brings accountability, faster check-in, and a record you can actually stand behind.

The system handles the whole visitor lifecycle: pre-registration before a visit, check-in, badge generation, and check-out. Security staff get role-based access, it supports several manufacturing units, and every action is recorded in a complete audit trail. If you need to know who was inside a facility at any point, the answer is in the system.

I built it on Laravel, PHP, SQLite, and Vite. Vibe-coded with AI, started July 2025: one of the first handful of things I built that way. It’s launched.

The making

  • Laravel
  • PHP
  • SQLite
  • Vite

01 · The problem

Before it existed

What hurt

A pharma facility cannot be unsure who is inside. The paper logbook was the only record – no speed, no traceability.

Who uses it

  • Security team
  • Management
  • Compliance and audit reviewers

02 · The flow

4 steps, in the order they happen

  1. 01 / 04

    Pre-register a visit

    You
    Enters a visit before the day
    It answers
    Holds the visit details and the manufacturing unit, ready for arrival
  2. 02 / 04

    Check in and issue a badge

    You
    Checks the visitor in at the gate
    It answers
    Records the arrival against the right unit and generates a badge for the visit
  3. 03 / 04

    Check the visitor out

    You
    Closes the visit on departure
    It answers
    Records the exit, so anyone still inside is known
  4. 04 / 04

    Ask who was inside

    You
    Searches by unit and time
    It answers
    Answers from a complete audit trail

03 · What was special

What it stands on

  1. Every action on the record

    Each step of a visit is logged, so who was inside a facility at any point can be answered.

  2. Several units, one system

    Visitors are tracked across the manufacturing units from a single place.

  3. Access follows the role

    Security staff work inside role-based access, defined by their role.

A paper logbook replaced by a record that stands up to audit.

Making-Of

A paper logbook, rebuilt as a record that holds up when it has to.

The Notion build hub and its brief

  1. The world before

    Visitor control at the pharma facilities ran on a paper logbook – no speed, little traceability.

  2. One day

    29 July 2025. The brief: a digital system for the security department covering the whole visitor lifecycle.

  3. Because of that

    1. Pre-registration, check-in, badges and check-out were scoped as one lifecycle.
    2. Role-based access and support for several manufacturing units were built in.
    3. A complete audit trail was made part of the design, since pharma audits demand traceability.
  4. Until finally

    It is launched and replaced the manual logbook.

  5. Since then

    It is one of the first handful of things built with AI direction.

The evidence Process, hands, and artifacts

Process

  1. Brief

    Replace the logbook; cover the full visitor lifecycle

  2. Access

    Role-based access for security staff

  3. Units

    Track visitors across several manufacturing units

  4. Record

    A complete audit trail for compliance

Hands

Akshansh

  • The brief and the scope of the lifecycle
  • Direction of the build for the security department

Agents

  • AI coding agentsWrote the application under direction