QSCSCoreV2

QSCSCoreV2 is now production-ready and is actively powering this website. Every page you load, every navigation event, and every state transition is handled through the deterministic QSCS substrate rather than a traditional web server stack.

This is the first public deployment of the V2 architecture, and it demonstrates the full end-to-end model: browser-side WASM state machine, delta-driven updates, encrypted peer transport, and multi-domain routing — all operating as a single coherent system.

WASM Client State Machine (Browser Runtime)

QSCSCoreV2 ships with a fully integrated WASM client state machine for browsers.
You are running it right now.

The browser no longer performs direct HTTP fetches. Instead, it participates in the QSCS substrate, sending state requests to QSCSCore and receiving optimised deltas in return. This eliminates full-payload transfers and enables the real-time bandwidth-saved bar visible under the Spook Systems Ltd header.

Multi-Domain Node Support

QSCSCoreV2 supports multiple node domains, enabling load-balanced and distributed web applications to run entirely inside the substrate.

Routing, state resolution, and upstream fetches are all handled deterministically by QSCSCore without the need for application-layer coordination.

Full instructions for configuring multi-domain deployments will be included in the upcoming documentation site.

Documentation & Installation (Coming Soon)

A dedicated documentation site is currently being prepared. It will include:

Once published, you will be able to install QSCSCoreV2 with a single command and begin running your own services inside the substrate.

Consultation & Integration Support

If you are interested in deploying QSCSCoreV2, integrating it with existing systems, or exploring distributed application design within the substrate, please contact us via the enquiries email below.

We provide architectural guidance, deployment assistance, and integration support.

Enterprise Support & SLAs

Enterprise-grade support packages and formal SLAs will be published alongside the documentation site and the full V2 release. These will include: