Architecture
Layered architecture. One coherent, swappable runtime.
Each layer has a clear responsibility, a stable typed contract, and an independent deployment lifecycle. Vendors are choices — not lock-in. Swap Stripe, Cloud Run, Claude, or Payload (headless) without touching the layers above or below.
Flexibility
Everything you see is configurable.
Swappable vendors
Payments, CMS, LLM, IdP, CDN, cloud — every named vendor sits behind a typed interface. Replace one without changing the rest.
Editable rules
Pricing, eligibility, bundling and entitlements live in a JSON-DSL. Operators ship changes from the admin UI — no deploy.
Open contracts
Every layer publishes REST + GraphQL + event schemas. Partners can integrate without a Screver release.
Layer details
Open any layer for responsibility, contract, metrics and cross-layer wiring.
Vendor names (Cloud Run, Stripe, Payload (headless), Claude, SwissID) are current production choices, shown as concrete examples. Each sits behind the layer's typed interface and can be swapped without changing the contracts above. Vendor doc links open in a new tab.
Console
Architecture console.
Pick any layer to see its responsibilities, latency, and live logs.
app.screver.ch/platform/architecture
PlatformArchitectureslug: architecture
⌘K
MK
Architecture console
all healthyReal example
Multi-provider booking in 1.2 seconds.
A guest books a combined ticket — a Glacier Express seat + a cable car ascent + a ski rental — from a hotel kiosk. The Channel Layer captures intent. The Commerce Layer assembles the cart and computes the fare. The Orchestration Layer reserves the seat with the rail operator, reserves a cable car slot via the gate system, reserves rental skis via the shop's inventory API. The AI Layer can pre-fill the cart from a chat. The Data Layer writes one booking with three audit entries. Total latency from intent to confirmed booking: under 1.2 seconds.
Keep reading