The Stoop
The Stoop is our infrastructure practice, turned into software — the front door to cloud environments you own. The same assessment, the same guardrails, the same teardown discipline our engineers apply on enterprise engagements, packaged so your team can drive it. It runs today for our own infrastructure; the private pilot opens soon, and self-serve accounts follow.
Why "The Stoop"?
In a row house neighborhood, the stoop is the front step — the part of the house that faces the street, where you're met before you're let in. That's what this is for your infrastructure: the welcoming, well-lit step up to environments that are unmistakably yours. You come to The Stoop to design, price, and approve; what gets built lives in your own cloud account, as code you own, behind your own keys.
What's live today — and what's next
The engine is built and has provisioned and destroyed real infrastructure on both AWS and Azure. What's next is the front door: a private pilot opening soon, then self-serve accounts.
- Live and proven: the full build lifecycle on AWS and Azure: design, security review, cost estimate, approval, provision, drift check, as-built documentation, and confirmed teardown.
- Pilot opening soon: a small first group, onboarded personally. Put your name on the pilot list.
- Not yet: open self-serve signup, published platform pricing, and programmatic access (a REST API exists in preview; an MCP surface for AI agents is on the roadmap).
- In the meantime: our cloud & platform practice delivers the same outcome with engineers instead of a portal, and everything they build lands in your account as code you own.
Consulting discipline, minus the meeting
Every environment we build by hand goes through the same gauntlet. The Stoop is that gauntlet, automated, so the discipline survives after the engagement ends.
Designed from vetted blueprints
Describe an environment or draw it on a canvas. It's composed from security-reviewed blueprints and a vetted add-on catalog, and you get exactly what you drew, with improvements offered rather than imposed.
Priced and gated before it runs
Every plan is costed before anything is created and checked against a ceiling that can't be waived in the moment. A named human approves each change; destructive diffs are called out rather than buried.
Yours, and reversible
It provisions into your own AWS or Azure through scoped, keyless access you can revoke, with no markup on your bill. One gated action tears an environment down and proves what it destroyed.
Cloud automation first. Then more of what we do.
Cloud environments were the obvious place to start: they're the work we do most, the work with the clearest guardrails, and the work where a mistake shows up on a bill within hours.
The intent is broader. Anywhere our practices do something repeatable and rule-governed (recovery rehearsals, posture reviews, cost health checks) there's a version a customer could run themselves, with our engineers available when the answer isn't routine. That's the product we're building toward: not a tool that replaces the firm, but the firm's discipline available at 2am without booking anyone.
We'll ship it the way we ship everything else: one capability at a time, honestly labeled, with the consulting team behind it.
The AI designs the shape. Your data never meets it.
AI drives intake, generation, and documentation, behind a data boundary enforced by architecture, not policy. Your identifiers are tokenized before any AI call and re-injected by script; screening is server-enforced at every entry point; models are commercially licensed and don't train on your content; and the whole boundary is exercised by a live test battery. The same posture we bring to AI governance engagements.
Want in? The pilot opens soon.
Put your name down and we'll reach out as pilot seats open, and you'll be first in line when self-serve accounts follow. No commitment, no card, no countdown clock. What you tell us you'd build shapes what ships first. Need it before then? The practice does it with you today.