Open Source Visitor Management System
A visitor log is two records at once. It is the compliance and evacuation list a fire marshal or auditor can demand without warning, and it is a sensitive pile of names, photos, signatures, and arrival times that you are now responsible for storing and deleting on schedule. Commercial kiosk services solve the first job while quietly taking custody of the second, moving your visitor data into their cloud. The open source systems here run check-in, badge printing, and host notification on your own tablet, kiosk, or server, so the log and everything in it stays on your network, under retention rules you set rather than a vendor's default. That ownership is the main reason to self-host a front desk.
visitor management
Visitor management system for digital check-in, entry and exit logging, and visit history
T.C.E.D.I. OVMS
Web-based visitor check-in, badge printing, and receptionist monitoring for internal facilities
VisitorPortal
Web-based visitor management system for pre-registration, reception check-in, badges, and welcome displays
Our picks
Three options for a self-hosted front desk, differing mostly in stack maturity and how far the authentication goes.
Most complete out of the box: visitor management This visitor management tool is the fullest of the three, covering digital check-in with entry and exit logging, pre-registered and repeat visitors, photo capture, badge printing, legal-document eSignatures, and an appointment scheduler, plus dashboards and email or SMS alerts. Built on Blazor and .NET with SQL Server, it ships a docker-compose HTTPS setup and a live demo, which makes it easy to evaluate before you commit hardware.
Receptionist-led badge printing: T.C.E.D.I. OVMS T.C.E.D.I. OVMS is a lean, staffed-desk system for enterprise internal use: browser check-in and check-out, direct DYMO LabelWriter printing over IPP, an optional NDA before the badge prints, and an on-screen keyboard for touch panels. Receptionists can monitor who is in the facility and check out visitors who forgot to. It runs on a familiar PHP and MySQL stack and descends from the older phpVisitorBadge projects.
Modern stack and SSO, still hardening: VisitorPortal VisitorPortal brings the most modern authentication of the group, with pre-registration, PDF badges, a welcome monitor, host notifications, and role-based access backed by optional MFA and OIDC single sign-on for Entra ID, Keycloak, or Okta. It is worth a pilot for those features, but be honest about its stage: the authors state it should not be used in a real organization without additional security and privacy review.
What to weigh before a system reaches the front desk
Reception flow is the first test, because a sign-in system that slows the morning rush gets abandoned for a paper book within a week. Watch how each tool handles the real lobby: pre-registered guests, walk-ins, repeat vendors, and the visitor who arrives without the invitation email. All three options here cover the core loop of check-in, badge printing, and check-out, but they differ in polish. The tool listed as visitor management adds photo capture, an appointment scheduler, and email or SMS alerts; T.C.E.D.I. OVMS focuses on a fast receptionist view with direct DYMO badge printing and an on-screen keyboard for touch panels; VisitorPortal leans on host notifications and a welcome monitor for scheduled arrivals.
Treat the visitor log as regulated personal data from the start. These systems can hold photos, signatures, NDA acknowledgments, and arrival times, so decide what you actually need to collect and how long to keep each field. Access control and authentication matter here: VisitorPortal is the only one of the three with optional multi-factor authentication and OIDC single sign-on for Entra ID, Keycloak, or Okta, though its own authors caution that it needs a further security and privacy review before real deployment. If your site captures NDAs, confirm the system records which policy version each visitor accepted, not merely that a signature exists.
This is a small, curated set, and the tools sit on different stacks - .NET on SQL Server, PHP on MySQL, and Laravel on MariaDB - so let your existing hosting skills narrow the field. Plan the offline path too. A front desk still has to admit expected visitors when the network, tablet, or badge printer fails, so keep a manual fallback and make sure the day's bookings can be exported or viewed without the full system running.
Related categories
Frequently asked questions
Can these run on a lobby tablet or self-service kiosk?+
They are browser-based, so a tablet in kiosk mode is the usual setup, but test it before rollout. The tool listed as visitor management ships a docker-compose HTTPS install and runs a public demo you can try first, and T.C.E.D.I. OVMS includes an on-screen keyboard designed for touch panels. Confirm camera access, kiosk lockdown, and how the flow behaves when a visitor gets stuck.
Do they print visitor badges, and on what hardware?+
All three print badges, but the mechanism differs. T.C.E.D.I. OVMS drives DYMO LabelWriter hardware directly over IPP and has been tested with CUPS. VisitorPortal produces printable PDF badges you send to any printer, and visitor management includes badge printing as part of its check-in flow. Verify your exact label size and printer driver early, since badge formatting is where lobby rollouts most often stall.
How are hosts told when their visitor has arrived?+
VisitorPortal is built around this, with host notifications by email and in-app plus a welcome monitor that greets scheduled visitors on a shared screen. The visitor management tool sends configurable email and SMS alerts using its own templates. T.C.E.D.I. OVMS leans more on a staffed receptionist view that monitors who is in the building, so match the notification model to whether your desk is attended.
Can visitors sign an NDA or site policy at check-in?+
Yes, this is common. The visitor management tool captures legal-document eSignatures during sign-in, and T.C.E.D.I. OVMS can require a non-disclosure agreement before it prints a badge. The detail to nail down is proof: you want a record of which policy version the visitor accepted and when, and whether an updated policy forces a fresh signature, so the acceptance holds up if it is ever questioned.
How is sensitive visitor data protected and access controlled?+
Each tool offers role-based access so reception, hosts, and administrators see different things. VisitorPortal goes furthest on authentication with optional MFA, required for admin roles, and OIDC single sign-on, though its authors flag that it still needs a security and privacy review before production use. Pair whichever you choose with tight retention rules, since photos and signed documents are the fields that turn a log into a liability.
Can one system cover multiple offices or sites?+
VisitorPortal is explicitly designed for one organization per instance with multiple sites inside it, which is the clearest multi-site model of the three. The others are oriented toward a single facility, so for several buildings you would run separate instances or check how visit records and permissions separate by location. Confirm that local reception can manage its own site without seeing every office's visitor history.
How do pre-registered visits usually work?+
A host or receptionist creates the visit ahead of time with the visitor's name, company, and expected arrival, and the visitor confirms details at the desk or kiosk on the day. Both VisitorPortal and the visitor management tool support pre-registration and repeat visitors. Check how each handles the messy cases: late arrivals, a substitute host, group bookings, and the guest who shows up without the confirmation email.