Operations
Running Spillway in production: security, sign-in, the fleet.
Hosting plans and their cost model
The four hosting plans Spillway sells on Accorbis, what each one runs on Fly.io, and what that costs at Fly's published rates. The commercial decisions are recorded in open-decisions.md (hosting plans, decided 2026-11-05). The plans live as data in packages/fleet/src/plans.ts, the rates (Fly's,…
Caching and CDN purge
How a published page gets from the renderer to a visitor, what Spillway caches on the way, which tags it files pages under, how a CDN in front is kept in step, and what to set where. The admin side is Site settings → Cache (getting-started.md); the endpoints are in api.md, Site; the internals in…
Fleet: provisioning and managing many Spillway sites
@spillway-cms/fleet (packages/fleet) creates and operates Spillway sites on a host from one command or one HTTP call. It is what a hosting provider such as Accorbis runs to turn "new customer" into "running site"; anyone can use the same CLI for their own sites.
Enterprise sign-in (SSO)
Spillway signs staff in through your identity provider with OpenID Connect or SAML 2.0. Providers are configured in the admin under Site settings → Sign-in (needs the users.manage permission, i.e. the admin role); each enabled provider becomes a Continue with … button above the password form on…
Security
How Spillway is built to be run on the open internet, what each role can do, and what to set in production. Vulnerability reports go to the address in SECURITY.md; the findings this page grew out of are in dev/security-review-2026-11-05.md.