ObjectOS
Editions
Diese Seite ist noch nicht übersetzt; angezeigt wird die englische Fassung.

Compare Editions

What each ObjectOS edition and plan includes, row by row — Community, Cloud Free, Cloud Team and Enterprise — and where each difference is enforced.

ObjectOS is one product in three editions. ObjectOS Community is the open-source runtime you run yourself. ObjectOS Cloud is the same product hosted for you, on the Free and Team plans. ObjectOS Enterprise is the licensed product on your own infrastructure: one edition, always a private deployment, sold by contract and priced per AI user. ObjectOS Cloud has no Business plan and no Enterprise plan. Prices and contracts are on License & Pricing; this page is what each one does differently. Beside them, anyone can open a free, non-production Developer Edition organization on ObjectOS Cloud to learn, build and demonstrate.

Every page in these docs carries a row of edition badges under its title, naming the editions it applies to. The sidebar marks the pages and groups that are not for every edition with the same icons.

The matrix

CommunityCloud FreeCloud TeamEnterprise
DeliverySelf-managedHostedHostedSelf-managed
PriceFree (Apache-2.0)Free$24 / AI seat / month, or $20 / AI seat / month billed annuallyBy contract, per AI user, 25 minimum: contact sales
File storageYour own (Storage)1 GB per environment20 GB per environmentYour own (Storage)
EnvironmentsAs many as you deployOne per organizationOne per organizationAs many as you deploy
MCP requestsSet by your deployment20 / minute, 1,000 / day120 / minute, no daily capSet by your deployment
Custom domainYour own host——Your own host
Record- and field-level security✓✓✓✓
Approval workflows✓—✓✓
Scheduled and time-relative flows✓—✓✓
In-UI AI (AI Builder, "ask your data")MCP only — bring your own modelTaste✓✓
AI governance (action audit, guardrails, permission scoping)———✓
Single sign-on with your identity provider✓ (Authentication)——✓
SCIM 2.0 provisioningOpen, off by default (OS_SCIM_ENABLED)——On by default
Several organizations on one deploymentOpen source in the framework, not in the Community image (Multi-organization)——✓
High availability (several replicas)———In development, not offered yet
Air-gapped operation———✓
SupportCommunityCommunityStandardStandard; priority and SLA support by contract

There is no Enterprise edition on ObjectOS Cloud: Enterprise is always a private deployment on infrastructure you operate. An Enterprise license includes every Enterprise feature, whatever the size of the deployment. Single sign-on with your identity provider and several organizations on one deployment are open source, free on a self-managed deployment; an Enterprise license adds our support for them. A deployment runs on one node today, with backup and restore; high availability across several replicas is in development and is not offered until it ships. On a self-managed deployment, Community and Enterprise run the same runtime: everything in the Community column is in the Enterprise column too.

Developer Edition

The Developer Edition is a free, non-production organization type on ObjectOS Cloud, for learning ObjectOS, building on it and demonstrating it. It is not a customer edition and not a plan you buy, so it has no column in the matrix above. The editions you run a business on are still Community, Cloud Free, Cloud Team and Enterprise.

  • Who can open one. Anyone with an ObjectOS Cloud account. The type is chosen when the organization is created: nothing turns a Free or Team organization into a developer organization, or a developer organization into another type.
  • Non-production. A developer organization is for learning, building and demonstrating, never for running a business. It has no upgrade, promotion or conversion to production. What you build there reaches production the way any app does: as a package you publish and install in a Free or Team organization or an Enterprise deployment, or as source.
  • At most five members, of every class. Every membership counts: the owner, every role, and every member class alike, whether AI seat, standard user or viewer. An AI service account registered for an agent in the organization's environment is a member too, and takes one of the five; an agent that signs in with a person's own API key is that person and takes no extra place. A pending, unexpired invitation holds a place as well, so an invitation is refused once members and pending invitations make five. The sixth membership, invitation or AI service account is refused with 403 DEVELOPER_ORGANIZATION_MEMBER_LIMIT_REACHED; remove a member or retire an AI service account to make room. No payment raises the limit.
  • Free, with no payment path. A developer organization costs nothing, and nothing in it can be bought: no paid plan, no AI seats, no credit packs. A checkout for one is refused with 409 DEVELOPER_ORGANIZATION_NOT_PURCHASABLE.
  • Cloud Free's limits. Like every organization, it has one environment, with 1 GB of file storage. Its in-product AI runs on the Free plan's model and weekly allowance (AI Credits and Limits), its MCP endpoint accepts Free's 20 requests a minute and 1,000 a day, and it has no custom domain. Approval workflows and scheduled and time-relative flows, which need Team on a customer organization, are available.

A developer organization runs with these Enterprise capabilities:

CapabilityWhat it does
Hierarchy securityRecord visibility relative to the business-unit tree: the unit, unit_and_below and own_and_reports read scopes. See Hierarchy Visibility.
AI governanceAn audit trail of every tool call the product's built-in AI makes (who asked the AI what, and what it touched), permission checks on each answer so the AI cannot become a way around record permissions, masking of sensitive fields in the data the AI's tools fetch, and visible quota refusals.

That is the whole list today. A developer organization gets an Enterprise capability only once it has shipped for developer organizations; until then it is not listed here and not offered there. No other Enterprise capability is part of a developer organization.

Where each difference is enforced

The matrix lists only differences the product enforces. These are the ones these docs already describe in detail:

  • The license decides what a self-managed deployment is. Without one, a single-organization deployment runs with Community behaviour — the open MCP server, bring your own AI. With one, the AI Builder and "ask your data" are unlocked on your own infrastructure. See AI Service.
  • On the Enterprise image, several organizations need the license. A multi-organization posture without one is refused at startup, and the runtime does not serve traffic. The multi-organization runtime itself is open source; the Community image does not ship it. See Multi-organization, Runtime Configuration and Troubleshooting.
  • Air-gapped operation is a license mode. An ordinary license is validated online against a control plane; an air-gap license is verified locally, and the deployment must also declare no control plane. The combinations that cannot work are refused at startup. See Air-gapped Deployment.
  • On ObjectOS Cloud, the plan is enforced per environment. An organization has one environment on every plan; a full environment refuses attachment uploads and bulk imports, never single-record writes, reads or exports (403 STORAGE_LIMIT_REACHED, with a warning from 80%); and the MCP endpoint answers 429 past the plan's request limit. See Environments and Storage and Limits.
  • An ended subscription falls back to Community. The Enterprise features switch off, and the system and its data keep working. Keeping a version after the end, a version lock, comes only with a perpetual license bought outright by contract. Three configurations that need a license refuse to start instead. See Licensing.

Which edition is this page for?

BadgeMeans
CommunityTrue when you run ObjectOS Community yourself
CloudTrue on ObjectOS Cloud, on the Free and Team plans
EnterpriseTrue on a licensed, self-managed ObjectOS Enterprise deployment

Deploy and Operate are for the two self-managed editions, Community and Enterprise: on ObjectOS Cloud we run the deployment for you.

Next

  • Start — the three ways in: Cloud, Community or Enterprise.
  • License & Pricing — prices, contracts and the open-source license.
  • Public Preview — what ObjectOS Cloud's current stage means for your data and integrations.

Auf dieser Seite