Trust is an architecture,
not a badge wall
Hiring an infrastructure firm means handing someone the ability to change, and to destroy, the systems your business runs on. Here is exactly how that access is scoped, gated, and recorded: first for consulting engagements, then for The Stoop platform, and an honest statement of where our compliance program stands.
How we work in your environment
When our consultants are in your systems, these are the rules of the engagement.
Your access, your revocation
We work through access you create, scope, and can revoke at any moment: named identities for the resources on your engagement, a cross-account role on AWS or federated credentials on Azure when cloud work needs them. We don't hold long-lived credentials to your environment.
No silent changes
Nothing changes in your environment without a plan you've seen and an approval you've given. Destructive work is called out ahead of time and confirmed with you before it happens, never discovered after.
Documentation as we go
Plans, decisions, and as-built records are produced as the work happens, so the paper trail an audit needs already exists. And because we work in your accounts, your own audit logging independently sees everything we do.
Built for the bad day
We design to resilience levels with stated RTO/RPO, rehearse recovery by cloning rather than hoping, and plan clean-room rebuilds that restore into isolation while a forensic hold protects the compromised original as evidence. The resilience practice does this work.
AI helps us work. Your data stays out.
Where AI assists our delivery, the models are commercially licensed and your content is not used to train anyone's models. The boundary between AI and identifying data is enforced in software and verified by a live test battery, not promised in a policy.
We run on our own discipline
Row House Tech's own infrastructure is managed under the same rules we bring to yours: least-privilege identities, no root usage, and every change reviewed and documented. We sell the practices we operate.
The same philosophy, enforced in software
These controls are specific to The Stoop, where the platform, not a person, holds the keys, so the guardrails are built into the pipeline itself.
Every change gated
Every change is planned before it's applied, scanned by a security review, priced before it's approved, and approved by a named human before it runs. Destructive operations are classified in the diff, and teardown requires explicit confirmation.
A hard stop on spend
Every plan is priced against the environment's cumulative monthly cost, and each tier's ceiling is a hard stop in the pipeline. No approval, customer or operator, moves a build past it.
Your account, no stored keys
The platform provisions into your own AWS or Azure account through scoped, short-lived, keyless credentials you can revoke. No long-lived cloud keys for your account are stored in the pipeline.
Tenant isolation in the data layer
Customer data is separated with row-level security and owner-scoped access enforced in the database, not just the application. Access keys are scoped per capability and per customer, with per-account limits.
Your data never meets the AI
Identifying data is replaced with neutral tokens before any AI call; real values are injected into configurations by script, never by the model. Screening is server-enforced at every AI entry point with a hard credential-transmission backstop, and the boundary is verified by a live test battery.
An audit trail by construction
Designs, plans, cost estimates, approvals, applies, drift events, and teardowns are all recorded on the environment's timeline, and as-built documents export on demand. Platform credentials live in a managed secrets vault, referenced by name and never committed to code.
Where we honestly stand
We're a young firm with a platform still in pilot, and we won't decorate this page with badges we haven't earned. Current status, plainly (the technical controls below are the platform's):
What we hold, and what we don't
What we store
- Engagement records: designs, plans, approvals, and the as-built history of what we built for you
- Infrastructure code and as-built metadata for your environments
- Account and billing information
What we don't
- Long-lived credentials to your AWS or Azure account
- Your application data — it lives in your account, behind your controls
- Your identifiers in AI prompts — the model only ever sees anonymized tokens
Questions about a specific control, our subprocessors, or responsible disclosure? Email contactus@rowhousetech.com.
Put our answers in front of your security team
Request the whitepaper and questionnaire, or bring your review — we'll show up prepared.