Skip to content

[Decision] One name for the self-managed edition: "ObjectOS Enterprise" (positioning, 8 pages) vs "ObjectOS Self-Managed" with Business single-node and Enterprise under it (License & Pricing, Deploy) #295

Open

Description

@objectstack-fleet

Found by the seat's site-wide audit on 2026-10-06. This needs a maintainer ruling. It changes product naming on both docs.objectos.ai and www.objectos.ai.

The conflict, measured on main @ b754364

Positioning (ruling Q1 on #171, 2026-10-05)

  • apps/docs/lib/positioning.ts OBJECTOS_EDITIONS reads: "ObjectOS runs hosted in the browser with nothing to install (ObjectOS Cloud) or self-managed on your own infrastructure (ObjectOS Enterprise)…"
  • index, why, architecture, quickstart, faq, glossary and security follow it, and so does www's src/lib/positioning.ts.

License & Pricing

  • content/docs/resources/license.mdx:8-10 and :38-44 define:
    • ObjectOS Cloud: Free / Team / Business;
    • ObjectOS Self-Managed: Business Self-Managed (single node, 10–25 AI seats, $540 / AI seat / yr) and Enterprise.
  • The Editions table gives Enterprise as "cloud or private deployment".
  • deploy/index.mdx:3-6 and deploy/docker.mdx use "Self-Managed".
  • README.md:38 lists Enterprise only under Self-Managed.

The result: a reader cannot tell whether Business Self-Managed counts as "Enterprise", or whether Enterprise is offered on Cloud. The legal pages in #294 had to choose, and they follow E1.

Options

  • A. Keep E1 as the product vocabulary. Self-managed is called ObjectOS Enterprise. license.mdx, deploy/** and README are re-worded to match, with Business Self-Managed described as an Enterprise single-node option and the "cloud or private deployment" cell revisited. This changes how pricing is described.
  • B. Keep license.mdx as the product vocabulary. The editions are ObjectOS Cloud and ObjectOS Self-Managed (Business single-node, Enterprise). The E1 sentence changes on both sites, along with the positioning constant, the gate and about 8 pages per site.
  • C. Name the deployment modes, not the editions, in positioning (recommended). E1 becomes "…hosted in the browser with nothing to install (ObjectOS Cloud) or self-managed on your own infrastructure, and either way you can export your ontology…". The "(ObjectOS Enterprise)" parenthetical goes, so the positioning makes no claim about which plan is self-managed. license.mdx stays the single source for plan names. This is the smallest change that makes every page true under today's price list.

Recommendation: C. It touches one sentence on each site plus the pages that repeat it, and it leaves pricing to the pricing page.

Ruled: 6124045928 · letter A · Enterprise is self-managed only · the single-node SKU keeps the name Business Self-Managed · 2026-10-12T12:14Z

After the ruling

The seat records it here (Ruled: line in the body). Execution goes to the docs on-ramp card filed with this one, and to the www copy sweep card.


Generated by Claude Code

Activity

  1. objectstack-fleet commented on Oct 12, 2026

    @objectstack-fleet
    ContributorAuthor

    Ruling: letter A, with two sub-questions settled in the same pass · maintainer, this session's chat · 2026-10-12T12:13Z

    repo:objectos PM seat (objectstack-ai/objectstack#9831), R1, session session_01H1D12NQAtnCRwY1YzR43Vd. The seat put this card to the maintainer in its chat, after re-measuring the conflict on main 10beb8b. The maintainer answered three questions; each answer is quoted verbatim below.

    1. The edition vocabulary. Asked: 「objectos#295:自托管版本叫什么?」 Answer: 「A 自托管统称 Enterprise」.
      Self-managed ObjectOS is called ObjectOS Enterprise. positioning.ts (E1) stays as written.
    2. The Enterprise column's "cloud or private deployment" cell. Asked: 「Enterprise 还卖「我们托管的专属云」吗?」 Answer: 「只自托管 (Recommended)」.
      Enterprise is self-managed only. The cell becomes self-managed (private deployment), and Cloud tops out at Business.
    3. The single-node SKU. Asked: 「单节点那档($540/AI seat/年,10–25 席)现名「Business Self-Managed」……名字怎么处理?」 Answer: 「保留原名,归入 Ent (Recommended)」.
      The SKU keeps the name Business Self-Managed and its price. The copy describes it as the single-node entry option of ObjectOS Enterprise.

    Governing text: apps/docs/lib/positioning.ts OBJECTOS_EDITIONS and its gate .github/scripts/check-positioning.mjs (ruling Q1 on #171). This ruling keeps both unchanged and brings the pricing and deploy pages into line with them.

    Execution shape, measured on main 10beb8b

    This card leaves the decision inbox for pm:queue and becomes the execution card, as #171 did. Every place that uses "Self-Managed" as an edition name is re-worded. Lower-case "self-managed" as a description of a deployment stays.

    The dev re-derives this list from the tree at dispatch. The list above is the seat's reading, not a specification.

    Serialisation. This session has one objectos push branch, and #141 is in flight on it. This card is claimed after #141 lands.

    Downstream.


    Generated by Claude Code

  2. objectstack-fleet commented on Oct 13, 2026

    @objectstack-fleet
    ContributorAuthor

    Claim: PM loop, repo:objectos seat, R1
    Session: session_01H1D12NQAtnCRwY1YzR43Vd
    Account: os-support-ai (the seat's linked user as GET /user answers it; always the card's assignee)
    Branch: claude/youthful-cannon-b4o03w. This is the session's one designated objectos push branch. Its previous head e52161d (PR #326) is an ancestor of main 76988da, so the branch restarts from origin/main as a fast-forward. The dev builds it from a local branch issue-295-enterprise-vocab.
    Worktree: objectos-issue-295-enterprise-vocab
    Domain: n/a (single-lane repo)
    Seat: repo:objectos (objectstack-ai/objectstack#9831)
    File surface:

    • content/docs/resources/license.mdx, plus its siblings license.zh-Hans.mdx and license.zh-Hant.mdx (deletion only, under criterion A)
    • content/docs/deploy/index.mdx · content/docs/deploy/docker.mdx · content/docs/operate/upgrade.mdx · content/docs/configure/ai.mdx · content/docs/index.mdx · README.md

    Stop on breach; explain in the report.
    Container & model: M, mode:subagent, model: opus (default tier; dispatch-gates.mjs --tier --repo objectstack-ai/objectos over this surface at objectstack 3071d3e98 answers "no path-derived mandate")
    Clause-②: no
    Responsibility: n/a — not a defect card (ruling execution)
    Ruling-ref: 6124045928
    Governing text: apps/docs/lib/positioning.ts OBJECTOS_EDITIONS and .github/scripts/check-positioning.mjs (ruling Q1 on #171), both unchanged by this card
    Thread-read: 6124045928
    Serial constraints cleared:

    Review face. Docs prose and README.md are not contract faces. The seat checks the diff sentence by sentence against the ruling in its ACCEPT.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 13, 2026

    @objectstack-fleet
    ContributorAuthor

    Release: session session_01H1D12NQAtnCRwY1YzR43Vd · reason: shift closing on the maintainer's instruction before any dev was dispatched · destination: pm:queue, unassigned, for the next session on this seat

    Provenance of the instruction:

    • Who: the maintainer.
    • Verbatim: 「当前任务处理完就下班」.
    • Where: this session's chat, 2026-10-13T14:11Z, while this claim (6147517221) was being written.

    What was done: nothing beyond the claim. No dev was dispatched, no worktree was created, and nothing was pushed to claude/youthful-cannon-b4o03w for this card. The branch head is still e52161d, which is merged.

    What the next claimant inherits unchanged:

    • the ruling 6124045928 (Ruling-ref:);
    • the surface measured on main 76988da, as listed in the claim above;
    • one more surface fact: apps/docs/app/[lang]/privacy/page.tsx already says "self-managed ObjectOS deployment (ObjectOS Enterprise)", which agrees with the ruling, so it needs no change.

    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions