The edge database · single-digit ms, everywhere

Data that lives where your users are.

HELIX replicates to every edge region and resolves reads locally — so a query in Tokyo never crosses an ocean. This whole page is one GSAP ScrollTrigger timeline.

Scroll ↓
Three primitives
Built from
three moving parts.

Pinned section, horizontal scrub — the panels move on the scroll axis, not the page.

01

Replicas

Every write fans out to all edge regions in the background, versioned and conflict-free.

▚ multi-region · CRDT
02

Local reads

Reads resolve from the nearest replica. No round-trip to a primary, ever.

◱ < 5ms p99
03

Edge functions

Run logic beside the data. The function and its rows share a region.

⟠ colocated compute
A read, end to end
  • 01Request hits the edge
    Anycast routes it to the closest of 300+ locations.
  • 02Local replica answers
    The row is already here — no primary round-trip.
  • 03Function runs in-region
    Business logic executes beside the data it reads.
  • 04Response returns
    Total path stays on one continent. Single-digit ms.
By the numbers
Fast is a feature.
0ms
Median read latency
0
Edge regions
0.99%
Uptime SLA
0 cfg
Replication to set up
$ helix deploy
→ replicating to 312 regions
→ warming edge caches
✓ live in 1.9s
Zero-config

One command.
Every region.

No replica topology to design, no failover to wire. Push once; HELIX places the data and keeps it consistent.

Consistency

Strong where
it matters.

Per-query consistency: take the local read when speed wins, or a linearizable read when correctness does. Same API.

await helix.get(key,
  { consistency: 'local' })

await helix.get(key,
  { consistency: 'linearizable' })
HELIX
Deploy in a minute

Ship data to the edge.

Start free — no card, no replica config, no ocean-crossing reads.