The way we build, ship and run software.
Every Qbits engagement is delivered against a documented standard — for infrastructure, release engineering, security, observability and organisational change. This library is the public reference for those standards.
Start here
The five-phase delivery model, the gates between phases, and what you receive at each one.
Every standard in this library, organised by the work a delivery team does and aligned to the Well-Architected pillars.
How we assess organisational readiness and recommend change that survives contact with the business.
The reusable agendas, registers, checklists and reports we use on engagements.
Practice areas
Practice map →Terraform module standards, remote state, account structure, and policy that is enforced rather than documented.
Repository conventions, branching models, release workflows and the build/test gates every change passes.
Deployment strategy selection, Elastic Beanstalk, containers and serverless, with the trade-offs behind each choice.
Metrics, logs, alarms, tracing and runbooks — designed against workload health KPIs from day one.
Shift-left DevSecOps, IAM and network baselines, Config policy, guardrails and detection.
RTO/RPO planning, backup architecture, restore drills and Resilience Hub assessment.
How to read a standard
Every page follows the same shape, so you can compare standards and see how they fit together.
This site publishes the parts of the Qbits practice that are reusable and safe to share: methodology, engineering standards and customer-facing templates. Client engagements, contracts, account identifiers and customer data are deliberately excluded.
Principles
Tools are selected to fit the customer's existing stack and constraints, not the other way around.
Infrastructure, policy, pipelines and runbooks live in version control and are reviewed like software.
Every practice leaves an artefact — a plan output, a pipeline run, a dashboard, a report.
Backups, rollback and runbooks are planned at design time, not after the first incident.