Cloud platforms, engineered to be handed over.
DAxWorks designs and builds production cloud platforms for organisations that need reliable infrastructure without building a platform engineering function of their own.
Start a conversationWhat we do
- Cloud platform engineering
- Production environments on AWS, designed around the failure domains and recovery requirements the workload actually has.
- Infrastructure automation
- Terraform in independently deployed stacks, policy-checked, applied through CI/CD without long-lived credentials. Environments are created from code, not by hand.
- Delivery engineering
- Pipelines built around a quality gate that nothing bypasses, federated identity instead of stored deployment keys, and versioned releases.
- Observability and reliability
- Alarms on the conditions that matter, routed to someone who can act. Recovery procedures that have been exercised rather than assumed.
- Security and cost governance
- Least-privilege access, encryption, secrets management and network isolation. Tagging and cost allocation, so operating cost is understood before the invoice arrives.
- Media and content platforms
- Upload, processing, transcoding and delivery pipelines, with the infrastructure and content platforms behind them.
- AWS
- Terraform
- GitHub Actions
- Checkov
- TFLint
- Gitleaks
- ShellCheck
How we work
- Design
- Build
- Prove
- Operate
- Hand over
A capability is not delivered until it is demonstrated.
Configuration is not evidence. A backup that has never been restored is not a recovery capability.
Infrastructure cost belongs to the client, at cost.
Cloud resources stay the client's operating expense, paid directly. DAxWorks does not treat increased cloud consumption as a source of margin.
An engagement that cannot end is a dependency, not a delivery.
Platforms are documented for a competent engineer who was not there, and built so their owners can operate, change or transfer them.
About
DAxWorks was founded in Montreal in 2019. We build production cloud infrastructure and the engineering practice around it: written standards, reviewed changes, recorded architecture decisions, and documentation that outlives the engagement.
Every engagement is scoped against ten capability domains, each at a named level, so what is being bought, and what is not, is written down before implementation begins.
- Availability
- Recoverability
- Scalability
- Reproducibility
- Deployability
- Access control
- Data protection
- Observability
- Cost governance
- Operability
Client work is private by contract.