Federal & contractor intake Discuss your deployment timeline. Capacity & availability ↗
FAQ

Frequently asked questions.

Information on infrastructure, security evaluation, capacity, commercial terms, and onboarding. Contact federal operations for requirements specific to your program.

Accreditation & compliance

Accreditation and compliance

Compliance coverage

FedRAMP High, DoD SRG IL5/IL6, NIST SP 800-53 Rev. 5, FIPS 140-3, HIPAA/HITECH, SEC Rule 17a-4, SOC 2 Type II, ITAR/EAR, CJIS Security Policy, IRAP PROTECTED, CMMC 2.0 Level 3, IRS Publication 1075, and StateRAMP. A complete overview is available on our compliance page.

The security controls that apply to our hosting platform, including boundary protection, account management, system monitoring, backup, and media handling, have already been assessed. Your assessment therefore covers only your application and the controls that remain your responsibility, not the underlying infrastructure. The division of responsibilities is documented in a shared responsibility matrix during onboarding.

Yes. Inheriting our baseline significantly reduces the scope of your authorization package, but your system still requires its own authorization. The difference is that you document your application rather than the platform. Our compliance engineers answer assessor questions about the hosting platform directly.

Evidence is delivered continuously through the Client Portal, rather than assembled once for an audit. Audit reports, control descriptions, and verification records are available to authorized users on your account. See our Trust Center for what is published and what requires portal access.

No. All hosting, processing, and support operations take place within the United States across our twelve U.S. facilities. All support personnel on federal engagements are U.S. persons.

Capacity & availability

Capacity and availability

Capacity update

Yes, for federal agencies, government clients, and cleared federal contractors. As 2026 capacity is fully committed, new engagements are scheduled for 2027 through 2029. Planning and control mapping typically begin well in advance of the capacity year. See our capacity update.

Most of our 2026 capacity is held under multi-year government agreements that run through 2029. Because every server is dedicated to a single customer, capacity cannot be oversold. Once capacity is allocated, it remains reserved for that customer for the full term.

Our consumer cloud service represents 5% of revenue and is closed to new accounts. Existing consumer customers continue to be supported under their current terms. Government cloud represents 89% of revenue and remains open to federal agencies and cleared contractors.

We commit to 99.99% monthly availability, backed by a defined schedule of service credits. The measurement method and credit schedule are set out in our master services agreement. See our service terms.

Yes. Multi-year agreements are standard for government programs, and our current commitments extend through 2029. A written allocation confirms your capacity and commercial terms for the full period.

Platform & security

Platform and security

Infrastructure specs

Every server is dedicated physical hardware, reserved for a single customer in a biometrically secured facility, rather than a virtual share of common hardware. Your performance is never affected by other customers, and no other customer's workload runs on the same machine.

Isolation is enforced by the processor itself. AMD SEV-SNP encrypts workload memory using keys the virtualization software never holds, so no operator with access to the server can read your data. Because protection is built into the hardware, it does not depend on configuration that must be maintained. See our engineering note on hardware attestation.

Yes, and we encourage it. Every secure server produces a signed report each time it starts, which your team can verify independently. The verification procedure is published, so the check does not depend on trusting our assertion.

Yes. Dedicated servers support demanding AI and data workloads without competing for resources with other customers, providing consistent performance for training and inference schedules.

Our security operations center monitors the platform around the clock. Notification and escalation procedures between your team and ours are agreed before launch rather than during an incident. See our incident response reference and our disclosure policy.

Please use the coordinated disclosure process described on our security page, which sets out scope, expected response times, and how findings are handled.

Commercial & contracting

Commercial and contracting

Pricing

Pricing is provided for each engagement during a briefing rather than from a standard rate card. Dedicated hardware, cleared support, transition engineering, and the inherited FedRAMP High baseline are priced together. You can build a sample configuration on our pricing page to see an indicative range.

Dedicated infrastructure does not lend itself to uniform pricing. Facility location, network requirements, storage, and support model all affect the cost, and most engagements span several years. A briefing produces pricing that reflects your actual configuration rather than an average.

Federal agencies, government clients, cleared federal contractors, and regulated enterprises in healthcare, financial services, and critical infrastructure. Our consumer service is closed to new accounts.

Yes. Integrators and managed service providers in our partner program can carry the contract and the implementation, which is often the simpler route where a program already has a prime relationship in place.

Customer references are available under a non-disclosure agreement during a briefing. Publicly, we identify customers by role and sector only, as most agency and cleared contractor engagements restrict attribution, and we do not name customers without written authorization. See our case studies.

Onboarding & support

Onboarding and support

Transition Program

The Transition Program pairs your engineers with ServLogi platform and compliance specialists across four phases, from scoping to handover. The work is scoped into the engagement rather than quoted as a separate services line.

Most transitions take 8 to 16 weeks from planning to handover. The deciding factor is rarely the infrastructure. It is how quickly control responsibilities can be agreed and how much the application must change. We commit to a date at the end of the planning phase.

A working session to review your workload, its data classifications, the controls you would inherit, and the capacity years available to you. The agenda and preparation guidance are available in what to expect in an onboarding briefing.

You receive a dedicated support team, agreed escalation procedures, and continuous evidence delivery through the Client Portal. Escalation arrangements established during the transition remain in effect after handover. See our support and escalation reference.

Yes. Our deployment guides, control mappings, and provisioning API reference are publicly available. Begin with our documentation index.

Next steps

Still have a question?

Our federal operations team will respond directly, and a briefing is the most effective way to receive guidance specific to your workload.

Request a briefing

A working session with our federal operations and compliance teams to review your workload, the controls you would inherit, and the capacity years available to you.

Contact federal operations

Check the Trust Center

Audit reports, control coverage, and live platform status, available for immediate review.

Visit the Trust Center