Environments
Every ObjectOS Cloud organization has exactly one environment, on every plan — its address, the environment page, and what suspend, archive, restore and delete each do to its data.
An environment is one running copy of ObjectOS with its own database, files, apps and address. Your organization's apps live in it, and your team signs in to it to use them.
Every organization has exactly one environment, on every plan. It is the production environment: the first one you create when you set up the organization (Start on ObjectOS Cloud), and the only one. One organization, one environment, many apps: you install and build as many apps as you need inside it.
| The environment | |
|---|---|
| How many | Exactly one per organization, on every plan |
| Address | Your organization's slug on the platform domain, or any other platform subdomain you choose, free on every plan |
| Idle | Never archived for inactivity |
| What it is for | The apps your team uses |
A second environment cannot be created. Plans differ in what the environment holds and allows (its storage, its AI allowance), not in how many environments there are.
Developing a complex app
If an app needs more than the AI Builder and the console give you, develop it
at source level instead of in a second environment: build it locally with
os dev and keep it in Git, then publish it as a package and install
it into your environment. See
Apps for the whole flow.
Create the environment
On Environments, choose Create Environment and give it a name; the platform assigns the address. The address can be changed later with Change Hostname (Domains). A new environment starts in Provisioning and turns Active when its database is ready.
To enter the environment, choose Open. It opens the environment's own console in a new tab, signed in as you.
The environment page
Each environment has a page with two tabs.
- Overview — its address, status, plan and type, the apps installed in it, and its access settings. A collapsed line, Features that need a higher plan, counts what the current plan does not include and lists them when opened.
- Settings — every action, in five sections: Apps, Plan and billing, Name and domain, Access and sign-in (including AI agent access) and Lifecycle and danger zone.
Actions that change an environment are offered to the organization's owners and admins.
Lifecycle
| State | What it means | Your data |
|---|---|---|
| Active | Serving requests | — |
| Suspended | All runtime traffic is blocked until you resume it | Kept |
| Archived | Removed from active views; it no longer starts on a visit | Kept until someone deletes it |
| Failed | Provisioning did not complete | None was created |
Suspend and Resume. Suspending blocks every request to the environment, from people and from integrations alike. Nothing is deleted, and Resume brings it back as it was.
Archive and Restore. Archiving takes an environment out of use. Restore brings it back, with its data; it starts again on its next visit.
Delete. Deleting is a two-step act, so one click can never destroy data:
- An environment that is not archived yet is archived, even if you asked for permanent deletion.
- Deleting an archived environment with Delete permanently if already archived checked destroys its database and all its files at once, with no recovery.
Deleting the production environment also asks you to check Force-delete the production environment. An environment whose provisioning failed holds no data and is deleted at once.
How long an archived environment is kept
An archived environment is kept, with its database, files and domains, until someone deletes it. Nothing expires on a timer, on any plan: archiving is always your choice, and so is deleting. Only the explicit, permanent Delete above destroys the data.
Next
- Plans and AI Seats — what the paid plans add.
- Storage and Limits — the per-environment storage allowance.
- Apps — install, update and publish apps in an environment.
Organization and Members
Your ObjectOS Cloud organization — its slug, the cloud console, adding employees in the environment and inviting organization-level people, the membership roles, and why sign-in lives in the cloud rather than in an environment.
Plans and AI Seats
The ObjectOS Cloud plans — Free and Team — the AI seat as the only paid seat, how to upgrade, cancel or change seats, who bills you, and where the console shows what your plan leaves out.