JavaScript at C-speed. Billed by the hour, not the request.
The first JavaScript runtime that isolates every end user. Every other runtime — V8 isolates, Node, Deno, Bun — multiplexes many users through one shared heap per core. DataVec gives each connection its own memory-isolated virtual kernel process: a smaller blast radius than any runtime you can buy, on software efficient enough to serve more traffic from the same machine.
A full platform for high-volume JavaScript backends. Write JavaScript, deploy normally, and we compile it to optimized C, keep it resident in memory, and scale it for you — then bill you for the actual infrastructure it uses: VM-time, cost-plus. No per-request, per-duration, or bandwidth metering. A managed platform, priced like the servers underneath it.
Edge functions with cloud-function semantics.Your code terminates the request on the machine — no proxy tier in front, running at the network edge — but with the full runtime a cloud function gives you, not the stripped-down edge subset. And it’s fast on every axis at once: no proxy hop, native compiled C, resident with no cold start, lockless execution, and no GC pauses. By “edge” we mean exactly that — no proxy in front, not hundreds of global locations. We run multi-region, and we’re adding more.
You write the standard Web Worker API — fetch(request, env), Request/Response, Web Crypto — plus a static site. Built on native coroutine scheduling for massive vertical scaling.
Next.js Static Routing
Processes a complex nested endpoint router with custom JSON payload returns.
Compiled & resident
Compiling JavaScript into native C stateful coroutines yields direct machine execution speed.
No cold start · no interpreter · no GC pauses
The best AI spend is the kind you never see.
Most AI spend shows up as a new line item — a cost you track, justify, and hope pays off. That is the wrong shape. The entire point of investing in AI is to turn expensive, expert, repetitive work into something cheap and automatic. When it actually works, the spend does not appear next to your costs. It disappears into them.
DataVec applies that to the cost of running your software. We use AI to compile your JavaScript and TypeScript into native C — the systems-level work that used to take a compiler team and a rewrite. There is no “AI” line on your bill to defend. There is a smaller infrastructure bill: the same code you already write, running at machine speed, isolated per end user, billed as plain VM-time, with the serverless premium gone.
You never see the AI spend. It cuts operational cost so far that it shows up as one thing only — a lower operational cost. That is what AI spend should really look like.
That is what we are building.
A new execution model for JavaScript infrastructure.
Under the familiar developer experience is a genuinely different engine — an M:N virtual kernel written in C. Your compiled app runs as memory-isolated virtual kernel processes (protected in-process, with no language VM and no WebAssembly) inside a small pool of always-resident OS processes — terminating the connection, isolating each end user, and reusing pooled Postgres and S3 object storage with no per-request startup.
Compile at deploy time
The DataVec Builder converts JavaScript/TS Web Workers and WebSocket endpoints into optimized C before production traffic hits your VMs.
Resident, isolated per connection
The DataVec Runtime keeps your compiled app loaded — no spin-up. Each connection runs in its own memory-isolated virtual kernel process (in-process protection, not a new OS process), and its pooled Postgres session is reused across requests: isolation per end user, no per-request cold start.
Billed by VM-time
You pay for the actual infrastructure your app uses — VM-time, cost-plus — never per-request, per-duration, or bandwidth. Choose how much management you want: a single server, reserved replicas, or auto-managed scaling — with no effect on how you're billed.
Same Worker API you write for
Cloudflare Workers
Deno Deploy
Vercel Edge
Fastly Compute
Netlify Edge
Per-user
Isolated per connection, not per core
Resident
No cold starts
Native C
Compiled execution
VM-time
Billed as infrastructure, cost-plus
The full picture, one page at a time
The home page carries the argument. Each page below carries the proof for one part of it.
How it works
Compile at deploy, resident at runtime
→
The pipeline that turns your JavaScript into native C, and the M:N virtual kernel that runs it with no cold starts.
Isolation & security
A boundary no other runtime draws
→
Every end user gets a memory-isolated virtual kernel process. Your code is caged by the kernel; your secrets never enter it.
Comparison & migration
Against Workers and Edge, and how to move
→
Billing, isolation, and cold starts side by side — and what porting from Cloudflare Workers or Vercel Edge takes.
Pricing
Billed by VM-time, cost-plus
→
Pick a VM size and your level of management. Estimate your bill against per-request platforms with the calculator.
Benchmarks
The numbers behind C-speed
→
Throughput, latency, and cost measured against the runtimes you would otherwise reach for.