Questions

The standard foundation: five AWS accounts in one region (management, log archive, security, production, and development) with single sign-on and MFA, guardrails, an audit trail nobody can edit, threat detection, a private network, encryption, and budget alerts. You get it as Terraform in your repository, with a pipeline, a README, a one-page list of every control we turned on, and a walkthrough with your team. Azure and Google Cloud follow the same pattern.

Anything beyond the standard scope, such as more accounts or regions, a VPN or private link to an office, data center, or another cloud, or controls mapped to a framework like SOC 2 or ISO 27001. We call that an extended foundation. It starts at $12,500, and we quote the total and the timeline in writing before any work starts. Very large estates are scoped as their own project.

The standard foundation takes 15 to 30 days, counted from the day we agree the accounts, network, and access with you. If those are ready on day one, expect something closer to 15. For an extended scope, we confirm the timeline with your quote.

Yours. We build everything in your own AWS, Azure, or Google Cloud environment, and you keep full control. Your cloud provider bills you directly for usage, including security services like threat detection and logging, and that is separate from our fee.

Tell us which accounts you need, share your IP ranges and anything the network has to reach, name your identity provider and who gets which access, and give us an administrator who can grant access on day one. We help you write these decisions down, and the clock starts once they are settled.

We work through roles your administrator grants, with the least access the job needs, and read-only access for assessments. We do not ask for shared passwords or long-lived access keys. When the work is done, you remove our access in one place.

After the first call, we set up a shared Slack channel with your team for the length of the project. We work business hours, and every change also shows up as a pull request in your repository.

A senior cloud engineer leads every engagement, and the person you talk to on the first call is the person who builds it. We take on a small number of engagements at a time so we can hold our dates. We share our background on the call.

Yes. Our public sample library on IaC Hub has more than 1,000 free Terraform templates you can browse and use. The engagements themselves draw on our private library of more than 1,300 templates, and we are happy to walk you through how we structure a foundation on the call.

No. We build the cloud settings your auditor looks at and show them clearly. Your auditor issues the certificate, and your policies and training stay with you.

Your compliance tool tells you what is failing. We fix the cloud so it passes, and we leave every fix as code so it stays fixed.

You can, and we often build on them. The hard part is deciding the structure, wiring login, logging, and encryption together, and handing it over in a form your team can actually change. That is the part we do.

Yes. We build the same foundation on Azure and Google Cloud, from the same starting price, as long as you have already chosen that cloud. We lead with AWS because that is where most teams start.

We handle that as a separate, scoped engagement. We assess what you have, fix the findings, and tighten your security posture, whether an audit is coming or you simply want less risk. It starts at $15,000.

You own everything. Your team can run it from the README and the pipeline, or our managed cloud operations can keep making changes as code from $4,500 a month, with your team approving each one.