Evaluation path

Try the product locally, then decide whether to self-host it.

Local evaluation starts with an administrator running the app. Operator staff then use the browser to import a schedule, check feeds, review realtime, and see the next issue.

Tour the workflow Review self-hosting

Local Evaluation

Start the appAn administrator runs the local startup command from the repository or release package.
Open local sign-inStaff open /admin/local-login on localhost and choose Start setup.
Use the private consoleStart at /admin/operations and follow the first missing or blocked step.
Review the resultDecide whether the workflow fits your schedule, vehicles, feed URLs, and maintenance needs.

Move From Local To Self-Hosted

Question	Local evaluation	Self-hosted reference operation
Where does the console run?	On a local machine after startup.	On an operator-owned server behind private admin access.
Where are feed URLs served?	Local or demo URLs for evaluation.	Stable deployment-owned URLs through the public feed paths.
Who owns secrets?	The local administrator.	The deployment owner, with private env files and rotation plans.
When can URLs be shared?	For local review only.	Only after agency and deployment-owner review authorizes sharing.

When An Administrator Is Needed

Startup and shutdownDocker, ports, database migrations, and local app lifecycle.
ValidatorsInstalling and configuring static GTFS and GTFS Realtime validator tooling.
Secrets and device tokensCreating, rotating, and storing credentials outside public docs and screenshots.
Self-hostingDNS, TLS, reverse proxy, systemd, backups, monitoring, and update planning.

Limits

Local evaluation helps you inspect the workflow. It is not proof of compliance, production readiness, consumer acceptance, hosted service availability, vendor compatibility, SLA coverage, production AVL reliability, or ETA quality.