Gov Shared Cloud Services

The platform PMO onboards at portfolio scale, intake forms, an account, a wiki. The program-specific work, your identity federation, your network path, your control inheritance documented for your assessor, is exactly what the intake queue doesn't provide.

The platform's authorization covers the platform. Your system still needs its own, and every control you claim to inherit must be documented or your assessor treats it as unmet. That documentation is the deliverable.

They work for the platform office, scoped to enterprise services, and your program would be competing for attention inside a very large book of business, with an OCI question attached when the platform's operator starts advising individual tenants. Avalon works only for you.

Both are accurate today, and the engagement is priced accordingly: this is a component-sized, fixed-fee, short-duration engagement, the lowest-risk way to evaluate a new vendor. Key-personnel certifications and a written methodology stand in for corporate CPARS at this size.

You can, and programs that do usually meet Avalon later through an IG finding or a FinOps review. Bespoke accounts outside the enterprise environment mean paying twice and defending the duplication.

No. This service ends at a tenant-ready state against a written acceptance checklist. Moving and modernizing the workloads themselves is Cloud Migration & Development, scoped and priced separately.

A standalone Shared Cloud Fit Assessment & Onboarding Sprint runs three to six weeks. Duration scales with impact level and enclave count far more than with agency size, an IL5 enclave with SCCA connectivity work runs weeks longer than a civilian FedRAMP Moderate tenant.