GitHub v1.3.1
The Philosophy

The framework that doesn't rename the platform.

We built Coralite because modern meta-frameworks have introduced a "Vocabulary Tax"—forcing you to learn proprietary abstractions for things the browser already does perfectly.

The web platform is incredibly powerful. But we've spent a decade wrapping it in heavier and heavier abstractions. We replaced native state with reactivity proxies, native forms with controlled inputs, and native DOM with virtual trees. Coralite takes a step back.

HTML, CSS, and JavaScript. Server-rendered, componentized, validated at build time.

The Non-Negotiables

Every helper in Coralite has a native Web API equivalent you could have written yourself. A helper earns its place when the native call breaks under component reuse. We never rename the platform.

Correctness has the same shape. Invalid templates, broken component contracts, and server imports cannot compile. Failures are deterministic, located, and explained before output ships. See the validation guide →

The Four Tracks

Track A: The Native Web

Server-rendered Web Components, Light DOM, and progressive enhancement.

Track B: Strictness

AST-level boundary enforcement, strict template tokens, and zero-runtime overhead.

Track C: Education

A learning path that starts with basic HTML and ends with a Netflix-shaped app in one paradigm.

Track D: AI Legibility

Machine-readable documentation and predictable APIs that LLMs can generate without hallucinations.

Structural Guarantees vs. Reputational Guarantees.

Next.js and Astro rely on build-time tree-shaking to keep server code secure. Coralite physically strips it via AST analysis. It cannot leak.

See the Benchmarks →