Skip to main content

Open source or Cloud plan

This plan is the spec for Open source or Cloud. The page is Conceptual. This docs site has no content-type frontmatter field, so the type is recorded here.

An AI assistant drafted the page and this plan. The draft names no model and no provider. The author is accountable for the claims. A reviewer should check them against the sources below.

Goal​

Explain how to choose infrastructure you run versus the invite-only hosted service, and send you to an existing guide.

Audience​

Developers deciding where a Shellui shell and its services will run. Contributors who need a local checkout are a second audience, in one section, so they do not follow the production path by mistake.

Outline​

  1. Define self-hosting and Cloud. Cloud means the hosted service on the waitlist.
  2. Say when self-hosting fits, including infrastructure cost.
  3. Say when the waitlist fits, and mark unpublished hosted operations as future and subject to availability.
  4. Separate contributor setup from a production deployment.
  5. Compare operating responsibility. Do not invent a feature split.
  6. Link the shared shell, authentication, administration, and storage pages.
  7. Link the next install, production, preview, playground, waitlist, and contributor guides.

Sources checked​

Open questions​

  • The waitlist does not say whether a future hosted service would run the shell only, or also identity-service, storage-service, hosting-service, and email-service.
  • No doc lists a hosted-only feature. The page assumes the MIT docs are the feature set. Confirm before adding a gate.
  • Regions, backups, monitoring, support, and any uptime commitment for the hosted service are unpublished. Leave those table cells as unpublished until a source exists.
  • shellui login documents a default backend.url of https://id.shellui.com. This page does not treat that host as Cloud. Confirm what that origin is before linking it here.
  • The website privacy policy names processors for waitlist email. That is form handling. It is not a residency claim for a hosted product, so the page omits it.
  • No production Compose file for every service showed up in the handbooks above. Issue 88 asks for one. The page does not invent that file.
  • The production sections name Postgres or a data volume. They do not document a backup job. Confirm before adding backup steps.