Pricing scales with your sites and scope.
Day1.bot is deployed into your Azure tenant, licensed annually, and managed by us. We do not publish a generic per-seat SaaS table because deployment scope, sites, ratings, and data requirements matter.
Commercial model
Request pricing for your repair-station deployment.
For the first repair stations deploying Day1.bot into their own Azure tenants.
- Part 145 and AS9110 readiness baseline
- Managed deployment into your Azure tenant
- Calibration, training, document, traceability, CAPA, and internal-audit domains
- Audit Packet Export
- Managed operations, updates, monitoring, and support
For repair-station groups that need consistent readiness across multiple sites or ratings.
- Standardized readiness templates
- Site and rating-level reporting
- Role-based access and audit trails
- Optional historical data migration
- Shop-specific customization without forking the core
For teams that want readiness data connected to BI, APIs, governance, and reporting.
- Readiness data for your BI environment
- API and export support
- Data warehouse support
- SSO and enterprise governance options
- Advanced security and audit support
Scoped by site and rating
Pricing follows the number of sites, ratings, readiness domains, and deployment scope.
Runs in your Azure tenant
This is not shared-cloud SaaS. The deployment lives inside your environment and is managed by us.
Design-partner stage
We are taking a small number of repair stations into first deployments so the product stays honest to the shop floor.
Questions repair stations ask first.
Is this SaaS?
No. Day1.bot is deployed inside your own Azure tenant. Your compliance data never sits in a shared multi-tenant cloud.
Where does my data live?
In your own Azure environment. It stays inside your boundary. We operate the deployment; we do not hold your data in a shared cloud.
Which standards does it cover?
FAA Part 145 and AS9110 for repair stations. If you also hold AS9100 as a manufacturer/MRO hybrid, talk to us about the manufacturing modules.
What about the new revision of the standard?
That is the point. Day1.bot is built to help your shop re-baseline before your next surveillance audit.
How long does it take to deploy?
Days, not months. It ships as a managed deployment into your tenant, so your team does not have to stand up infrastructure.
What about our legacy data?
You can start clean and be useful in days. Historical migration is an optional, scoped add-on, not a prerequisite to value.
Who updates and maintains it?
We do. Managed operations, patches, monitoring, and support are part of the relationship.
Want a scoped price for your repair station?
Book a readiness conversation and we will map the sites, ratings, records, and tenant deployment model that drive pricing.