Who can use it?
cloud.gov is suitable for a wide range of applications, including websites and non-website applications for internal and public uses.
Good fit for cloud.gov
- You have a technical team (employees and/or contractors) that can push applications to cloud.gov. (See technical requirements below.)
- Your application is for a United States federal government organization.
- You understand that cloud.gov is a product under active development and will see changes in the future.
- Your application is FISMA Moderate or lower.
- You can pay for cloud.gov through the federal Interagency Agreement (IAA/MOU) process (see how to purchase).
- Your team can install the cloud.gov command line interface (compatible with Windows, Mac, and Linux).
- Your application can read configuration from the environment.
- Your application uses one stateless process at a time (that can be horizontally scaled).
- Your application listens to a single port.
Your application’s dependencies are explicitly declared (such as
Optional but recommended
Your organization can integrate your identity system with cloud.gov over SAML.
Your application doesn’t rely on the filesystem for storing its state.
- An experimental service supports filesystem-dependent applications.
Your application can follow the 12-Factor App guidelines.
Not a good fit
- Your application requires proprietary databases not listed in our database service documentation.
- Your team is unable to use the federal Interagency Agreement process for payment. For example, this may apply for teams working for U.S. local, state, tribal, or territory government organizations. If this applies to your team, sign up for updates so that we can notify you if we add other options.
Cannot use cloud.gov
- The applications you’re building are not on behalf of a U.S. government organization.