Access & attestation
U.S. facilities
A defined hardware boundary
Single-tenant servers separate your workloads from other customers at the physical hardware level.
ServLogi / Dedicated cloud infrastructure
Dedicated cloud
for government.
Single-tenant cloud infrastructure for federal agencies and government contractors. Configure compute, storage, and networking in U.S. facilities, with engineering support for deployment and operations.
Federal and contractor intake is open. View capacity information
ServLogi / InfrastructureArchitecture overview
Customer boundary
ApplicationsData workloadsPublic services
Dedicated physical hardwareSingle tenant
Access & attestation U.S. facilities
01 / The platform
Infrastructure for federal workloads.
Configure dedicated infrastructure to meet application, data-handling, and operational requirements. Establish the system boundary and support responsibilities as part of deployment planning.
Secure Compute
Dedicated servers for sensitive applications, analytics, and AI workloads. Hardware isolation keeps capacity reserved for your organization.
Explore computeAgency Web Portals
Hosting for public services and internal applications, with infrastructure and operational support aligned to your agency’s requirements.
Explore web portalsDeployable Data Centers
Compute beyond a fixed facility. Explore rack, transit-case, and container configurations for sites with limited connectivity.
Explore deployable systems02 / Security & control
Infrastructure control.
Documented responsibility.
Evaluate platform controls, assessment documentation, and the responsibilities assigned to each team. Review the applicable service boundary with your security and assessment personnel.
Review compliance coverageVerification at the processor
Review signed AMD SEV-SNP attestation reports and the configuration requirements for confidential workloads.
Read the attestation guide ↗Clear control responsibilities
Review the applicable authorization boundary and shared responsibilities with your assessor before committing a workload.
Visit the Trust Center ↗03 / From plan to production
Migration planning and deployment support.
Coordinate application dependencies, security requirements, validation, and cutover activities with the deployment engineering team.
- 01 / Assess
Define the requirements
Map application dependencies, data classification, capacity, and program dates.
- 02 / Prepare
Build the deployment plan
Agree on architecture, control responsibilities, testing, and the migration sequence.
- 03 / Transition
Validate before cutover
Test the environment, verify server integrity, and document the operational handoff.
Technical evaluation
Technical evaluation and procurement.
Use the documentation to prepare a focused review with your engineering, security, and procurement teams.
Evaluate the platform.
Define the deployment.
Define the deployment scope before making architecture or procurement commitments.
Open the Trust CenterBrowse documentationWhat is dedicated to our organization?
The physical host is reserved for a single customer. Review the compute, storage, and networking configuration, including any shared service dependencies.
Infrastructure specificationsWhich controls remain our responsibility?
Identify the platform controls that apply to the engagement, then map application security, identities, data handling, and operational ownership with your assessor.
Plan your security reviewHow do we plan a migration?
Start with dependencies, a representative test workload, and the target dates. Define validation, cutover, and rollback criteria before scheduling the move.
Migration & onboardingCapacity & procurement
Plan your infrastructure deployment.
Engage ServLogi to review workload requirements, available capacity, procurement considerations, and the delivery schedule for your program.
Technical resources