JavaScript at C-speed. Billed by the hour, not the request.
DataVec is 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. That’s also why it’s fast: no proxy hop to cross. By “edge” we mean exactly that — no proxy in front — not hundreds of global locations; we run in two US regions today (San Francisco and New York).
Drop-in compatible with standard Web Workers, Next.js, and static site APIs. 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
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.
Runs existing code from
Cloudflare Workers
Deno Deploy
Vercel Edge
Fastly Compute
Netlify Edge
Resident
No cold starts
Native C
Compiled execution
Static
Single self-contained binary
VM-time
Billed as infrastructure
Direct comparison & capabilities showcase
DataVec replaces virtualized serverless runtime layers with compiled execution. Explore our billing, API standard compliance, and supported frameworks below.
Billing & Cost Comparative Metrics
Comparing infrastructure-priced VMs vs utility-metered edge networks.
DataVec compiled C
Billing unit
VM-time, cost-plus
Starter bill
$17.00 / mo
Bandwidth fees
Included ($0)
Cold starts
None (resident)
Cloudflare Workers
Model
Metered requests
Starter bill
$5.00 / mo
Bandwidth fees
Free
Cold starts
V8 isolate warmup
Vercel Edge
Model
Metered CPU + Seats
Starter bill
$20.00 / user / mo
Bandwidth fees
$0.15 / GB metered
Cold starts
Subprocess boot delay
The Compiled Edge Deployment Pipeline
Explore the pipeline phases to inspect how standard JavaScript code is compiled, linked, and hosted on our native edge network.
Visualizing compiler & runtime efficiency
DataVec replaces the virtualization stack — VM, language engine, garbage collector — with an M:N virtual kernel: a userland kernel, written in C, that isolates and memory-protects each connection in-process, with no language VM and no WebAssembly. Hover over the symbol map and stack diagrams below to inspect the design.
Source-to-Native Translation Showcase
At deploy time, the DataVec Builder translates your standard JavaScript into idiomatic native C, mapping each construct onto hand-tuned native structures. Under the hood, this leverages our stackless coroutine framework to execute concurrent micro-threads in isolated, partitioned micro-heaps:
JavaScript Source
Compiled C Target
→ Hover over any JavaScript or C node above to inspect compiled symbols.
Virtualization Layer Comparison
Standard serverless stacks execution layers — a VM, a JIT engine, a garbage collector — each adding latency and cache pressure. DataVec compiles your service into a standalone virtual kernel daemon that aligns data layout with code layout, so it cache-misses far less and saturates cheaper hardware than a garbage-collected engine needs — and because it’s lockless and soft-real-time, there’s no GC pause and a flat latency tail.
DataVec compiled C
Single self-contained binary
No per-invocation cold starts
Virtualized Edge Isolate
Multi-layer runtime stack
Cold start on scale-up
Compiled to C. Caged by the kernel. Blind to your secrets.
The first question about compiling JavaScript to C is “how is that secure?” — but the thing protecting you was never the language. It’s the cage around it. On DataVec that cage is kernel-enforced and tighter than the V8 process you run today: your Worker can’t make a syscall it wasn’t granted, and your secrets never enter it at all. Compiling to C confines your code harder than the runtime you came from, not less.
Your Worker can’t make a syscall it wasn’t granted
Every Worker runs under Syscall User Dispatch with a narrow, kernel-enforced allow-list. Try to open a file, spawn a process, or dial a socket it wasn’t granted and the kernel traps it and reaps the process — there’s no library policy to bypass.
Least privilege at the OS
Each Worker is pledged to a minimal set of operations and unveiled to only the exact paths it needs. Its filesystem and capability surface is cut to near-zero before a line of your code runs — the OpenBSD security model (pledge and unveil), enforced on Linux.
Your secrets never enter your code
Database passwords, API keys, and per-upstream tokens live in the host. It attaches them to requests on your Worker’s behalf — your JavaScript never holds a secret it could log, exfiltrate, or redirect to another host. A compromised Worker can’t leak what it never sees.
Capabilities are off until granted
SQL, object storage, email, outbound fetch, and AI streaming are denied by default and enabled per service. Least privilege is the default, not an opt-in. Revoke a capability and the Worker’s await fail-closes instantly — no redeploy.
Per-connection isolation, no shared state
Your app stays loaded in resident processes (one per CPU core), and each connection — each end user — runs in its own memory-isolated virtual kernel process inside them: a hardware-walled region, not a new OS process, with no cross-connection heap and no shared globals. Within a connection the handler and its pooled database connection are reused across requests — no per-request startup. A crash or compromise is contained to that one connection’s virtual kernel process and reaped, never spreading across your traffic.
You never hand-write the C
The JS→C lowering is content-addressed, API-grounded, and behaviorally gated — a faithful, tested lowering of your JavaScript over bounded region allocation, not arbitrary C. You get C’s speed without ever touching C’s manual-memory footguns.
Pick a VM size and your level of management
Choose a VM size, then choose how hands-on you want to be — a single server, reserved replicas, or auto-managed scaling. Every option ships the full platform and bills the same way: by VM-time, cost-plus. Your management level is your call; it doesn't change how you're billed.
Deploy in San Francisco · New York — same price in every region, your choice of location.
To launch: sign up (a one-time $1 verification), connect a Git repository(required — that's the app we build and run), and pick a size + region + management level. Your app builds and goes live at <name>.apps.datavec.comwith automatic HTTPS, and you're billed monthly for the VM-time it uses.
Spec your machine
Set the vCPU and memory you need; we match the DigitalOcean VM that meets it and price it cost-plus. No named tiers — you pay for the machine.
vCPU cores
1
Memory (GB)
1 GB
Need something bigger, dedicated CPU, or single-tenant hardware? That's a custom build — see Enterprise below.
Your machine
$17
/month
A dedicated 1-vCPU VM with 1 GB RAM and 25GB SSD — your app stays resident. That's one VM for a full month; you're billed for the VM-time you actually run, cost-plus, and your management level doesn't change it.
- Dedicated VM — your app resident in memory, no cold starts
- Custom domain registration + automatic HTTPS
- Full WebSocket & HTTP/2 protocol support
- Postgres wire connections in isolated sandboxes
- R2-compatible S3 object store worker
- Billed by VM-time, cost-plus — no per-request or bandwidth metering
vCPU
1
Memory
1 GB
SSD
25 GB
💎 Enterprise
— Custom
Dedicated hardware isolation, sizing beyond the standard machines, dedicated-CPU or memory-optimized families, single-tenant routing, and a premium SLA.
Synthetic metering vs. VM-time, cost-plus
Configure your monthly footprint. We estimate the metered bill on your current serverless platform, then size the DataVec VM that serves the same peak load at our published per-core throughput — priced as VM-time, cost-plus, with no per-request or bandwidth metering. Add reserved replicas for redundancy if you want; they're billed the same way, by VM-time.
Peak load ~3,472 req/s
Provisioned ~8,000 req/s
Cloudflare Bill
$976/mo
Metered utility pricing
DataVec VM-time
$17/mo
1 × 1 vCPU / 1 GB · 1 vCPU
Saves $959/month · $11,513/year
Illustrative estimate using vendors' published list prices as of June 2026 (AWS includes API Gateway; Cloudflare has zero egress). The DataVec figure is the real catalog price of the VM capacity needed to serve your peak throughput — assuming a 12× peak-to-average burst — at our published single-core rates, with headroom, billed as VM-time (cost-plus). VM plans include generous egress — we don't meter bandwidth. Reserved replicas for redundancy are optional and billed the same way. At very high volume, metered platforms are often negotiated down with committed-use discounts, so compare against your actual invoice.
Every VM bills the same way — VM-time, cost-plus — from a Business VM at $80/mo down to a $17/mo Starter VM. No per-request or bandwidth metering, and your management level doesn't change the unit.