Try a free sandbox space
A sandbox is a free space that you can use to see if cloud.gov might suit your team’s needs. From the setup process through deploying an app, it works similarly to other spaces that are included in paid access packages, with some limitations.
Get a sandbox
Anyone with a U.S. federal government email address (ending in
.fed.us) can sign up for a free sandbox space. No paperwork is required from us. (It’s up to you to determine whether you may need permission from your agency.) If you have other questions or comments, see Contact.
If you’re interested in purchasing full access (whether for Prototyping or for production systems at the FISMA Low or FISMA Moderate levels), email email@example.com and we’ll help you get started.
Keep in mind before you try your sandbox
- If your agency has not already integrated its single-sign on authentication provider with cloud.gov (only GSA, EPA, and FDIC have done this so far), you will access your sandbox through a cloud.gov account. This account requires multi-factor authentication using a mobile app such as Google Authenticator or Authy. If you cannot install or use these apps, such as if your workplace prohibits mobile phones or mobile phone cameras, you might not be able to set up access. (Paid access packages support integration with your agency single sign-on authentication provider.)
- If your agency prohibits installing the cloud.gov command line interface on your computer, you won’t be able to deploy applications in your sandbox. (For paid access packages, we can coordinate with your agency to help them approve this tool.)
- If your agency blocks many network ports, you might receive errors when you try
cf ssh. (For paid access packages, we can coordinate with your agency to ask for unblocking those ports.)
A few things you can try in your sandbox
As part of that, you can:
- Try the web interface (dashboard) and the command line options.
- Deploy a demo app or two! You can use one of these sample apps or your own code. You can also try an app from the Cloud Foundry community (we don’t maintain or vouch for these).
- Create a free service instance, such as a PostgreSQL or MySQL database instance, and bind it to your application.
- Look at your application logs.
- Give a teammate permission to deploy by assigning them the “space developer” role.
Sandboxes are limited because cloud.gov is a cost-recoverable service. They’re a free trial to help you evaluate whether to purchase cloud.gov.
Sandboxes are for testing; they’re suitable for information and applications that require no confidentiality, integrity, or availability. (Don’t put production applications or production data in sandboxes; that’s not what they’re for.)
- Resource usage is capped at 1 GB of memory total, for all the applications in your space combined.
- You’re capped at using a maximum of 10 service instances, 10 service keys, and 10 application routes, for all the applications in your space combined.
- You can only create free managed service instances. (See each service documentation page for details about which service instances are available in sandboxes.) You cannot create managed service instances that will require payment in the future.
- You can only use the default
*.app.cloud.govdomain, not custom domains.
- Sandboxes do not have an “org manager” role available. (You can control access and permissions for your own sandbox space.) If you want to manage an org of prototyping spaces for people at your agency, consider purchasing a prototyping package.
- We periodically delete sandbox contents to ensure that users don’t run production applications in sandboxes. Specifically, we clear all sandbox contents 90 days after the first application or service is created. We’ll warn you via email five days before clearing out your sandbox.