Government
Government FAQ
Permanent answers to common questions about federation, environments, workload eligibility, evidence, classified claims, disconnected operation, economics, and pilot design.
Frequently asked questions
Start with the boundary.
Use the mission, environment, product, trust, pricing, and contact pages for the detailed decision path.
Capacitas Government is a proposed qualification and operating pathway for U.S. government workloads that require specific residency, personnel, facility, network, evidence, or authorization boundaries. Commercial capacity remains available only when the workload and customer policy permit it.
The relevant requirement sets can include FedRAMP High, StateRAMP High, DoD IL2/4/5/6, ICD 503/705, JSIG PL-3, ITAR, IRS 1075, CJIS, NIST SP 800-171, HIPAA, FIPS 140, and an agency ATO. The applicable scope depends on the customer and system boundary. Capacitas does not claim these are currently held unless the public authorization register identifies the evidence, owner, scope, and date.
Eligibility is determined by the government customer, applicable acquisition path, data and mission requirements, sponsoring authority, facility and personnel rules, and the approved system boundary. Government contractors and solution providers may participate only under the relevant agreement and validation process.
Only when the specific model, software, hardware, data path, facility, personnel, network connection, and complete system boundary are approved for that classification and mission. Product availability in one environment does not imply availability in another.
The acquisition path must be selected with the customer and an eligible prime or channel partner. Potential routes can include direct awards, schedules, task orders, OTAs, SBIR/STTR follow-ons, and mission-specific vehicles; availability is not asserted until a named vehicle and authorized seller are confirmed.
The architecture supports connected, disconnected, and DDIL planning. Each workload and node still needs an explicit profile for local functions, control-plane dependencies, approved synchronization, evidence retention, recovery, updates, and loss-of-link limits.
Submit the mission assessment form with the workload, data type, users, models, environment, performance, site, power, security, evidence, support, and contracting constraints. Capacitas will use that information to define the smallest appropriate evaluation path.
Residency, replication, administrative access, identity, citizenship or clearance requirements, and support access must be defined for the selected environment and contract. Capacitas records those limits as placement and operating rules rather than assuming a single answer across the federation.