01
Scope
A 60-minute working session with the engineer who would lead the build. We tell you whether we can help and what it would take.
The work between "it works" and "it scales." CDK-first architecture, multi-account guardrails, and a fractional cloud lead — handed off to a team that can run it without us.
Ark is what Orion does when our platforms don't fit your problem directly. You need a real architect in your seat — designing the AWS or Azure landing zone, writing the CDK, working through the multi-account boundaries, shepherding the migration cutover.
The engineer scoping your project is the engineer doing the work. We do not partner-pitch and junior-staff. The same person you talk to in week one is the person who runs the production cutover with your team in week eight.
We bring what we've built and operated for ourselves: Sprintsail for IaC, our own reusable Terraform modules, the runbooks we use on our own platforms. None of this is theoretical. All of it has been operated through real incidents before it lands in your stack.
One team, one timeline. We scope, build, operate, and hand off. No rotating consultants.
A 60-minute working session with the engineer who would lead the build. We tell you whether we can help and what it would take.
A written architecture proposal — CDK-first, multi-account where it fits, with security and cost guardrails baked in. Reviewed with your team before any code.
Implementation in your AWS or Azure accounts. Reproducible from source, documented, version-controlled. Your team pairs with us throughout.
Runbooks, documentation, training. Your team takes over. We stay available for as long as the engagement scopes — or as a retainer.
Cloud architecture proposal. Written, reviewed, signed off before we write code. Includes the runtime topology, IAM model, network design, observability, cost model, and the parts we deliberately won't do.
IaC (CDK by default, Terraform on request). Reproducible from source. Multi-environment. Versioned. Your team owns it on day one.
Multi-account guardrails. AWS Organizations + Control Tower + SCPs sized to your blast radius. Identity model that won't be embarrassing under audit.
Observability and runbooks. CloudWatch + X-Ray (or Datadog/Grafana if that's your stack). The runbook your on-call team reads at 2am.
Fractional cloud leadership. Optional retainer where one of our senior engineers attends your architecture reviews and weighs in on decisions you don't yet have someone to weigh in on.
Tell us what you are building. We will tell you honestly whether we can help and what it would take.