Prerequisites
Target environment, network access policy, identity provider, SMTP relay, and the storage and compute footprint are agreed before any installation begins.
Deployment overview
How an AXOS deployment is delivered
This page outlines what to expect before, during, and after an AXOS deployment. Detailed operational runbooks are shared privately with the customer engineering team during the engagement.
Deployment phases
Each phase is walked through jointly with the customer engineering team. Exact timing depends on environment readiness and scope agreed in the proposal.
Domains and TLS
Customer-owned domains are pointed at the AXOS web and API services. Certificates are managed by the customer or via a reverse proxy of their choice.
Database and migrations
Application database is provisioned inside the customer environment. Schema migrations are run before the API accepts traffic.
Email delivery
Outbound mail (verification codes, demo credentials, internal notifications) is sent through an SMTP relay configured by the customer or ScotiTech under agreement.
Secrets and credentials
Database credentials, SMTP credentials, and any service tokens are stored in the customer-controlled secret store and never committed to source control.
Health checks
Service-level health checks for the web, API, and database are wired into the customer monitoring stack so service state matches what users see.
Rollback path
The previous working image or commit is retained and a documented rollback procedure is agreed for each release.
Pre-launch verification
Before go-live, the customer and ScotiTech walk through homepage, registration, authentication, email delivery, and admin actions to confirm the deployment is healthy.
Responsibility
Customer
- Provides infrastructure, network access, and the operating model
- Owns secrets, identity provider, and reverse proxy configuration
- Approves change windows and production sign-off
Responsibility
ScotiTech
- Delivers AXOS images, schema migrations, and configuration guidance
- Runs the joint deployment session and pre-launch verification
- Provides support, advisories, and release updates during the engagement
Operational runbooks are shared privately
Hostnames, monitoring queries, container commands, and incident procedures are not published on this page. They are shared directly with the customer engineering and security teams during onboarding, and updated through the support channel agreed in the engagement.