Browser runtime
The client receives the QSCS WASM module during bootstrap.
Integrate QSCS Without
Rebuilding Your Application.
QSCS sits in front of your existing application and database, adding edge caching, browser-side delta reconstruction, and encrypted peer synchronisation.
DEPLOYMENT ARCHITECTURE
Your application stays.
QSCS takes the front path.
The browser loads the QSCS WASM runtime, then traffic moves through the QSCS ingress mesh to your application. Your webapp and database can remain on private, controlled connections behind the edge.
Browser
QSCS WASM
Ingress Mesh
Webapp
Database
Substrate mesh
Ingress nodes serve requests and synchronise eligible state.
Internal origin
The existing webapp and database stay behind the substrate.
REQUEST LIFECYCLE
Bootstrap once. Then QSCS
takes over.
The first request reaches the HTTPS edge and returns the page with the QSCS WASM runtime. Subsequent requests can use state and delta delivery over HTTPS, while the mesh synchronises eligible responses between nodes.
Bootstrap
once
Browser
HTTPS Edge
QSCS WASM
loaded
The initial HTTPS request delivers the application page and QSCS runtime through your load balancer or reverse proxy. The browser can then establish the baseline needed for state-aware responses.
QSCS
takes over
Client + WASM
QSCS Mesh
Webapp
Database
QSCS can return cached state, a delta, or a no-change response when the client has a matching baseline. Protected requests use Ed25519 signatures when the identity-gate integration is configured; existing cookie-based authentication remains a separate application flow.
REQUEST SERVING
Reach the origin only when needed.
QSCS chooses a response source according to cache policy, identity, and availability, then uses the client’s matching baseline to reduce transferred bytes where possible.
Incoming GET requestAuthentication and cache eligibility checked
Eligible cached response?
Freshness and persistence policy apply
Hit
Served from cache, without a foreground origin body fetch
Matching client baseline?
Compared with the current available state
No change / Incremental
A compact no-change response or the changed bytes
Cold anonymous miss?
Peer pull enabled and usable peer state available
Peer pull
A configured peer supplies a valid cached response
Fetch from origin
When suitable state is not available
Full
Fetch the response, then cache and replicate if eligible
These are serving options, not a fixed decision order: a cache or peer hit can also deliver a delta. A client baseline alone does not prove freshness or remove the need for origin validation. A missing or mismatched baseline falls back to a full response.
Integration Remains Low-Touch.
No backend SDK to embed and no new application protocol to implement. The browser-side WASM runtime and QSCS mesh handle state delivery while your existing application interface stays in place.
Configure edge routing, private origin access, and the authentication model appropriate to your application.
THE RESULT
Build On A State-First
Foundation.
Explore Spook Systems and see how deterministic shared state can simplify coordination, recovery, and communication across the systems you already run.
QSCS
ALIGNED