LancerLogin 2.0.0 · self-hosted attendance

Attendance your organization operates

LancerLogin runs in your own GitHub and Cloudflare accounts. Members check in and out at Raspberry Pi kiosks, and Administrators and Operators run meetings, rosters, and reports from a web dashboard. Fingerprint templates stay inside the reader unless an Administrator turns on cloud storage.

Install LancerLogin Read the privacy notice

Choose what you need to do

Install

Create a private repository from the template, add a Cloudflare token and three secrets, and run the installation workflow.

Install LancerLogin

Sign in and set up

Create the first Admin, choose modules, and finish Attendance setup with rules, a first meeting, and your roster.

First sign-in and setup

Add kiosks

Assemble a Raspberry Pi kiosk, run the installer from the dashboard, and pair it with a one-time key.

Kiosk guide

Run attendance

Schedule meetings, correct or excuse attendance, manage the roster, and export reports.

Operate LancerLogin

Update

Update the dashboard from Settings, update each kiosk from the Kiosks page, and manage plugins.

Update LancerLogin

Fix a problem

Find the cause of common installation, sign-in, kiosk, and update problems.

Troubleshoot

Modules and plugins

LancerLogin 2 is built from modules. Core always provides accounts, the roster, reports, integrations, backups, and updates. An Administrator chooses which modules to turn on.

Module	How it is included	What it does
Attendance	Built in	Meetings, kiosk check-in and check-out, corrections, excuses, attendance rules, and kiosk management.
Outreach Participation	Official plugin, included by default	Outreach activities and participation hours submitted by members.
Carpool	Optional plugin	Ride planning to and from events.
Guest Visits	Optional plugin	Guest visit records, which can also be counted in Outreach once an Administrator grants access.

Plugins are added to an installation from Settings › Modules › Manage modules or from the installation's private repository. See Add, update, or remove plugins.

How an installation fits together

Your private GitHub repository holds the deployment workflows and secrets. The public repository provides reviewed releases.
Your Cloudflare account runs the dashboard on Pages, the API on a Worker, and the data in a D1 database.
Each Raspberry Pi kiosk or web kiosk on a touchscreen laptop or tablet pairs with the dashboard and keeps an offline queue, so check-ins are saved while the network is down.

Community support is best-effort.Questions and responsible security or privacy reports can be sent to robolancers@gmail.com. There is no response-time or uptime commitment.

Release boundaries

An installation can pair several kiosks: Raspberry Pi kiosks and web kiosks on touchscreen laptops or tablets.
Dashboard updates and kiosk updates are separate steps.
Reports export as CSV. Backups are JSON files from Settings, or D1 exports for large installations.
This documentation never contains credentials, private repository details, attendance records, or backup contents.