// DESIGN PHILOSOPHY

Let it crash. Restart with policy.

ShipStacks templates lead with OTP-inspired actor supervisors — crash-isolated write paths, a gateway that fails closed during restart, and the same production kit (auth, Stripe, S3, email, AI) already wired on mainstream backends.

// OPEN SOURCE

Inspect the Go and Rust supervisor cores.

The same mailbox + gateway + restart pattern — runnable demos with /api/debug/crash, unit tests on Go, and MIT licenses. Full SaaS kits stay on the marketplace; these repos are the wiring you can audit.

Four technical beats. One contract.

The buy reason is wiring you can see — not “AI wrote templates,” and not a stack-count pitch.

01

Mailbox + gateway

Supervised writes go through a gateway into a DataActor mailbox. HTTP handlers enqueue work — they never own the write lifecycle or hold the DB connection across the crash boundary.

  • Bounded mailboxes per actor type
  • Gateway send with timeout
  • Contact + document writes supervised
  • HTTP stays on the request path
02

Unregister → 503

When the actor is down or restarting, the registry unregisters the mailbox. The gateway fails closed with 503 instead of writing into a dead channel or blocking forever.

  • No silent write into a closed mailbox
  • Clients see a clear restart window
  • Other routes keep responding
  • Open-source Go + Rust demos show this live
03

Restart policy + backoff

OTP-inspired one-for-one restart: max retries, exponential backoff, then a failed state. Native BEAM OTP on Elixir uses the same let-it-crash idea with GenServers.

  • Max retries + exponential backoff
  • Isolated DataActor write path
  • POST /api/debug/crash for demos
  • Restart counters on admin / debug
04

Supervised vs direct DB

Not every query goes through an actor. Reads and simple paths stay direct. Writes that must survive process death — contact, documents — go through the supervised path. PHP ships the kit without an actor layer by design.

  • Supervised: contact + store document
  • Direct: reads, auth session lookups
  • BEAM: sessions under VaultServer
  • PHP: production kit, no actor layer
// THE S+S CONTRACT

Built in before you write a line.

Every stack ships the same production foundation — auth, payments, uploads, privacy, Docker, and your library. You only choose the language and framework.

Sign in OAuth, SSO, or email
Pick stack Language + SPA
Pay once Stripe checkout
Ship Library + updates
// SUPERVISED WRITE

Try /api/debug/crash.

On supervised stacks, crash the DataActor — the supervisor restarts it while other routes keep responding. That is the demo, not a marketing metaphor.

  • OTP-inspired supervisors

    Go · Rust · Node · Python · Rails · .NET (mainstream)

  • Native BEAM OTP

    Elixir — GenServer tree + supervised sessions

  • Production kit, no actor layer

    PHP (Laravel) — intentional

  • Also available

    Rails SPA + Livewire, Laravel SPA + Hotwire, Next.js, Blazor

supervised write · let it crash
// HTTP never owns the write lifecycle (Go)
err = supervision.Send(actor.TypeStoreDocument, actor.StoreDocumentPayload{
  ID: id, UserID: userID, Content: content,
  VectorLiteral: core.ToVectorLiteral(vec), CreatedAt: now,
})

# crash the write actor — supervisor restarts it
curl -X POST /api/debug/crash
[info] Unregister mailbox → gateway 503
[info] Restarting child actor (attempt 1)…
[info] HTTP still serving

Wiring you can see. Buy the zip.

Same supervisor story and production kit — pick the language you already use.