The Launch workspace puts your app online and separates test changes from the Production app your customers use.
Three environments have different jobs
An environment is a separate copy of your app with its own address and state. Orbit's Launch overview names three environments:
- Sandbox is the place to try changes.
- Review is the place to check a change before customers see it.
- Production is the live app your customers use.
A change in a test environment does not reach Production until you deploy it there. A successful test and a live update are different results.
For example, a repair business can test a new request form in Review while customers use the current form in Production. The repair business and form are examples, not a built-in app template.
A deployment includes more than the pages
Orbit deploys your pages, workflows, and database together. Each app has its own Postgres database, and existing data stays when you deploy again.
Orbit gives the app an address on orbitapps.ai with HTTPS. You can also connect your own domain. App settings shows each environment's address, server size, and last deployment.
A deployment does not decide who should read private customer records. You still need to define and test access rules. Authentication explains the difference between sign-in and record access.
A test address is not the customer address
For the repair business, the new form must work at the Review address before the business moves the change to Production. Test records let the business check the form without real customer details.
The form's appearance is only one check. The business also needs to confirm that a submitted request stays saved and that another customer cannot read it.
Review an app before launch covers those checks. Repeat the main customer task at the Production address after deployment. A result at the Review address does not prove what customers receive.
A deployment takes time
Orbit bundles the app, applies safe database changes, and waits for the new version to become healthy before that version takes over. The current live app stays available during that process.
A deployment health check does not replace a test of your app's main task. For the repair business, the final result is a customer who can submit a request and return to the saved request.
For more on what persists between deployments, read Isolated Postgres database.