Redoubt Managed Account.

Redoubt provisions an AWS account dedicated to a single customer, lays down a complete secure baseline, and keeps that baseline running. The baseline covers account structure, VPC and networking, IAM, and logging, so every customer workload that lands in the account starts from hardened ground. The account is single-tenant. Your workloads are the only workloads inside it.

Redoubt operates the account lifecycle end to end: initial provisioning, baseline maintenance as AWS service primitives evolve, routine patching, incident response, and SLA-backed support. Console access for customer personnel is defined in the engagement agreement and may be full, scoped, or read-only, depending on the compliance posture the customer is targeting. Workloads above the baseline remain customer territory.

Managed Account is right for organizations that want the entire secure substrate handled so their own teams can focus on applications rather than account hardening. It is a Team, Business, or Enterprise offering; Developer and Guardian tiers do not include Managed Account eligibility. Teams typically come to this service after running out of appetite for operating their own secure baseline, after a compliance readiness push, or ahead of a regulated workload that needs a clean starting point.

A 10% utilization fee applies to the deployed AWS resource cost inside the managed account. Team, Business, and Enterprise subscribers only. The platform subscription fee and the utilization fee are billed separately: the subscription goes through the usual channel, and utilization is metered through AWS Marketplace so your invoice draws down any existing AWS EDP commitment. There is no per-account minimum and no markup beyond the 10%.

Redoubt is pursuing its own FedRAMP authorization. Inheriting that authorization through a Managed Account engagement is a future capability tracked on the Redoubt Roadmap. Today, Managed Account delivers the hardened baseline and operational coverage described above; no inherited authorization is promised. Customers planning for a regulated workload should treat inheritance as forthcoming rather than available, and size the engagement against the baseline that ships now.