Pilot / Current Stage
Validated locally. Ready for bounded dealer pilots.
The public site describes the operating model directly. This page defines the exact local-pilot baseline and the work a production deployment requires.
Works today in the validated local pilot
Five accepted local-pilot capability statements.
- Individual pilot sign-in
- Role-scoped access
- Local PostgreSQL-backed persistence
- Private local-pilot attachment handling
- A locally tested backup-and-restore procedure
What that does not establish
Local validation is not a production claim.
The baseline does not establish production identity services, MFA or SSO, independently audited access controls, managed hosting, production object storage, automated off-site backup, disaster-recovery capability, defined recovery objectives, or unattended-operation readiness.
Product workflow versus deployment readiness
Commercial conversations start with the operating picture.
Scale Passport is developed and validated around the workflows of a multi-location independent scale sales and service company. The public product pages describe the connected record. A dealer pilot defines the approved scope, data handling, operating roles, and deployment requirements before real operating data is accepted.
Next deployment work
Production deployment adds the controls and connections selected for that dealer.
Dealer requirements determine which hosting, identity, storage, connector, monitoring, and recovery controls the next deployment adds.
- Production hosting
- Deployment-specific identity hardening
- MFA or SSO if selected
- Production object storage
- Live email delivery
- Selected ERP, calendar, document, or fleet connector
- Monitoring
- Managed backup and recovery requirements
Pilot conversation