Reference deployment
Run the same operator workflow on your own infrastructure.
Self-hosted operation keeps the private Operations Console, public feed URLs, credentials, validators, backups, and monitoring under the deployment owner.
Deployment Owner Checklist
- Prepare the serverUse an operator-owned Linux host, database, reverse proxy, and private service account.
- Configure secretsSet database, admin, CSRF, and device-token secrets in private env files.
- Run migrationsApply database migrations before starting app services.
- Start private servicesRun agency-config, telemetry ingest, and feed services behind the reverse proxy.
- Open the consoleUse the private Operations Console to set up the agency and import a schedule.
- Check the five feedsConfirm discovery, schedule, Vehicle Positions, Trip Updates, and Alerts paths.
- Plan operationsReview validators, backups, support summaries, monitoring destinations, and update procedure.
Who Owns What
| Area | Owner | Where to review |
|---|---|---|
| Agency metadata, license, contact | Administrator with agency input | /admin/operations/setup |
| Schedule import and active feed version | Operator or administrator | /admin/operations/gtfs-import |
| Public feed base URL and reverse proxy | Deployment owner | /admin/operations/feed-health |
| Vehicle data, device tokens, sidecars | Administrator and integrator | /admin/operations/devices |
| Backups, validators, monitoring, updates | Deployment owner | /admin/operations/maintenance |
Limits
The reference deployment guide is an implementation path, not evidence that a deployment exists or is ready for production. Stronger public statements require deployment-specific review and authorization.