Graphden documentation

Plans & tiers

Graphden’s cloud stratifies tenants into tiers. A tier is a slug on the org (:plan) that resolves to (a) the side effects its graph may use and (b) its quota ceilings — the source of truth is graphden.tenancy.plan (in the private graphden-tenancy repo).

Pricing is published at graphden.dev (or contact licensing@graphden.dev); this page documents what each tier includes, not what it costs.

  Anonymous (demo) Free (registered) Cloud Shared Cloud Dedicated
Effects allowed db state time random + network + network + network process
Outbound HTTP (network) ✗ ✓ (egress-guarded, rate + size capped) ✓ ✓
Connect to your OWN database ✗ ✓ (external :sql-query/:sql-exec) ✓ ✓
Outbound calls / min 0 120 6,000 ∞ (uncapped)
Max fns 200 500 5,000 5,000
Max list items 2,000 50,000 500,000 500,000
Persistence ephemeral (reaped) persistent while used (see note) persistent persistent
Always-on services ✗ ✗ ✗ ✓ (up to 20)
Resource isolation shared pod shared pod shared pod dedicated cgroup-limited shard
BYO executor (run your own — BYO_RUNBOOK.md) ✗ ✗ ✓ ✓
raw-sql (platform DB) ✗ ✗ ✗ ✗

Notes:

Starting an anonymous demo

A landing visitor gets an anonymous org through the unauthenticated endpoint:

POST /api/demo/start   →   {"token": "<bearer>", "org": "demo-xxxxxxxx"}

It mints a throwaway anonymous-tier org (locked, no network, small ceilings) plus a bearer token, and stamps an :expires-at so the demo-GC reaper purges the whole org after the TTL (GRAPHDEN_DEMO_TTL_MS, default 1 h). The visitor uses the returned token like any bearer.

This endpoint is OFF by default — a public, zero-friction row-creating endpoint is an abuse surface. A deploy opts in with :tenancy/user-ops {:demo-signup-enabled? true}. When off it returns 404; when on it is per-IP rate-limited (429 over the window), and the anonymous tier + TTL bound each demo’s blast radius.

Founding beta — paid tiers before billing exists

Until billing ships, paid tiers are granted by hand and never sold:

The billing seam — invoices today, a provider later

Whatever bills, the org row ends up carrying three fields, written only through the operator route (POST /api/orgs/plan, or Operate → Orgs):

Field Meaning
:plan the tier slug
:plan-until when the plan ends (a YYYY-MM-DD day, inclusive); nil = open-ended (a founding grant, a hand-set tier)
:plan-note operator free text — the invoice number, the founding-beta promise, later a provider subscription id

The reaper (:tenancy/demo-gc) is the clock: a paid org past :plan-until drops to free on the next sweep (nothing is deleted — the free ceilings apply from its next request), its people are emailed, and the note keeps the history (… · network ended 2026-12-31); a week before the end they get one warning. So an invoice paid through a freelance platform is plan=network, until=<period end>, note=<invoice> today, and a payment provider’s webhook tomorrow is a handler that calls the same route with the period end it was told — the provider never reaches the schema.

For invoices and the founding-orgs register, GET /api/orgs/usage.csv?days=30 answers every org’s runs / failures / summed duration over the window as CSV (operator context only; a tenant gets the header).

Funding

Where each kind of money goes, so the lanes never mix:

Source Goes to Pays for
Donations, GitHub Sponsors, grants the project’s Open Collective (fiscal host: Open Source Europe; public ledger) contributor work on the open-source repository, against invoices at the published rate; community expenses
Cloud subscriptions, implementation work, paid support, commercial licences the maintainer’s own business servers, the hosted service, the maintainer’s time

Rules that follow: the collective never pays for the servers that run the hosted service (they are shared with the free tier); a donation never buys a cloud tier; cloud revenue never flows through the collective. Support and implementation are described in SUPPORT.md, the commercial licence in COMMERCIAL.md.

Suspending an org (abuse kill-switch)

suspended is a special tier — not something a tenant buys, but an operator’s throttle-to-zero for a misbehaving org. It grants no effects at all and sets every row ceiling to 0, so a suspended org can neither run any graph (execution is blocked at the effect gate) nor create any entity (the row-cap rejects even the first write). Deletion stays allowed, so the tenant can still clean up its own data.

An operator sets any org’s tier — to suspend, to restore, or to upgrade / downgrade — through the platform-only route:

POST /api/orgs/plan     (form-encoded: name=<org-slug>&plan=<tier>)

plan is one of free / network / dedicated / suspended; an unrecognised slug is rejected (:plan/unknown) so a typo can’t silently drop an org to the free default. The change takes effect on the org’s next request (the resolver is not memoised). This route is platform-only — the :org entity is tenant- forbidden, so a tenant cannot change its own or another org’s tier.