Full-Stack Reactive Apps
Without Browser Driven Runtimes.
Eronom combines fine-grained signal reactivity with a native Rust HMR engine, zero Virtual-DOM overhead, and zero-config process routes.
<script> import { useState, effect } from "eronom/signals"; // Fine-grained reactive signal (Zero VDOM) let count = useState(10); let double = useState(() => count * 2); effect(() => console.log('Signal value: ' + count)); </script> <div class="process-card"> <h3>Count: {count}</h3> <p>Double Signal: {double}</p> </div>
Engineered for Extreme Performance
Four core architectural breakthroughs powering high-scale web applications.
Fine-Grained Signal Reactivity
Unlike virtual DOM frameworks that re-render entire component trees, Eronom tracks reactive signal dependencies directly down to exact DOM nodes.
Sub-Millisecond HMR
Native Rust compilation server delivers updates in under 0.4ms over memory-mapped IPC without state loss.
Zero-Config Process API
Define type-safe server HTTP routes in server/api/routes.er with zero boilerplate.
Streaming Edge SSR & Hybrid Prerendering
Server-render dynamic pages at the edge with zero cold starts, or prerender static assets instantly for ultra-fast global CDN distribution.
How Eronom Works
From initial declaration to edge deployment in three streamlined steps.
Declare Signals
Create reactive signals using standard JavaScript syntax with automatic dependency tracking.
Write Server Handlers
Export zero-config Rust/JS API endpoints with end-to-end type safety.
Deploy Anywhere
Compile to lightweight static HTML assets or ultra-fast edge server binaries.
Speed Measurements
Cold-start response times compared to traditional SSR web frameworks.
Frequently Asked Questions
Everything you need to know about Eronom framework.
What makes Eronom different from React or Svelte?
Eronom uses fine-grained signal reactivity with zero Virtual DOM overhead, compiled by a native Rust backend for instant sub-millisecond hot-reloading.
How does zero-config server routing work?
Server endpoints defined in your project are automatically typed and mapped directly to frontend signal requests without requiring complex build configurations.