Enterprise setup

Sitebin is open-core: the community edition is complete on its own, and the enterprise edition adds accounts, tiers & quotas, OAuth login, SMTP, and Stripe/Paddle billing on top — all configured at container startup, like everything else.

Editions

• Community (default) — MIT licensed, built with go build / the default sitebin:latest image. Fully open, no accounts, no feature gates.
• Enterprise — the ee/ tree, governed by the Elastic License 2.0. Compiled in only with the ee build tag (go build -tags ee, image sitebin:latest-ee).

The ee/ source is published in the repository — source-available, so you can read and audit every line before you buy. Both editions build from the same repo, but the community sitebin:latest image contains none of the ee/ code: it is excluded at compile time, so the community binary stays pure MIT.

Account modes

SITEBIN_ACCOUNT_MODE selects how the instance handles users (default: open):

• open — no accounts; anonymous creation, exactly like the community edition.
• accounts — users log in to create sites.
• tiers — accounts plus tiered quotas (and optionally paid plans).

Enterprise environment variables

Tiers

Tiers are defined as JSON, either inline in SITEBIN_TIERS or in a file mounted at SITEBIN_TIERS_FILE:

[
  {
    "id": "free",
    "max_site_bytes": 104857600,
    "max_files": 1000,
    "max_sites": 5,
    "webdav": true,
    "custom_domains": 0,
    "max_expiry_days": 30,
    "price": null
  },
  {
    "id": "pro",
    "max_site_bytes": 1073741824,
    "max_files": 10000,
    "max_sites": 100,
    "webdav": true,
    "custom_domains": 5,
    "max_expiry_days": 0,
    "trusted": true,
    "price": { "stripe": "price_123", "paddle": "pri_456", "display": "€9/mo" }
  }
]

Two optional flags change behaviour rather than quotas. "trusted": true exempts the tier's sites from the strict content-security headers untrusted uploads get — grant it to plans whose holders you can hold accountable, and see Operations & security for what the two header levels contain. "admin": true marks a tier whose holders may reach the instance register at /account/admin: every site on the instance, with search, filters, delete and expiry control. Admin needs a second condition — the account's email must also be listed in SITEBIN_ADMIN_ACCOUNTS — so neither the tier source nor the container environment can grant instance-wide access on its own.

A tier's price maps it to provider price IDs — a tier with a price becomes a paid plan the dashboard sells via checkout. Point your provider's webhooks at POST /account/billing/stripe/webhook and POST /account/billing/paddle/webhook.

The account dashboard

The dashboard lives at /account on the main domain. Sites created while signed in are owned by the account and still work over the API with their edit password.

It also issues API tokens, optionally named. A token creates sites owned by the account without a browser session — which is what makes publishing from CI or an AI agent possible on an instance where sign-in goes through SSO — and stands in for the edit password on every site that account already owns. It is shown once and stored only as a hash, and it acts on sites, never on the account: the dashboard refuses it, so it cannot change a plan or delete the account. See the API page.