CoCreateJS Blog

Architecture, engineering, and open infrastructure.

Explore why the runtime exists, how its pieces work together, and what we are learning while building it.

Runtime

Why CoCreateJS Is a Runtime, Not a Framework

The distinction between rendering applications and providing the distributed capabilities beneath them.

Architecture

Every Node Is a Complete Participant

Why complete peer nodes simplify deployment, replacement, routing, and multi-cloud operation.

Routing

Application-Aware Routing with Native HTTP

Keep routing policy in JavaScript and redirect clients without permanently proxying traffic.

API and AST

Provider-Native APIs Without Provider SDKs

Use documented provider payloads while the runtime manages credentials, authorization, and transport.

Operations

Self-Healing Workers Without an External Orchestrator

Observe, cordon, redistribute, recover, and scale through integrated runtime coordination.

Data

Application Definitions as Structured Data

How shared definitions let stateless nodes change behavior without rebuilding or redeploying.

Technical articles are being prepared. Follow the project on GitLab for current source and development updates.