Why VOLENT
One current, not a stack you babysit.
Sub-50ms reads from the nearest edge
Every client reads locally, so the browser is fast, not just the backend.
Shared state that stays consistent
Two users editing the same record converge on one result, with no last-write-wins surprises.
Streams, presence, storage, one API
Drop in a single typed SDK instead of stitching four services together.
Prototype to millions of connections
The same current scales without a broker to capacity-plan or a pool to babysit.
How it works
Connect, publish, and let the current fan it out.
Most realtime stacks bolt together a broker, a cache, a database, and glue code, and every hop adds latency. VOLENT replaces that with one current: a single low-latency channel that moves state from your servers to every client and back. You write state once, and VOLENT decides where it lives, which edges need a copy, and how to keep them in sync. There is no polling loop to tune and no broker to capacity-plan.
- Connect. Open a current with one SDK. No brokers to provision, no connection pool to babysit.
- Publish state. Write to a key and VOLENT replicates it to the edges that need it, in the order it happened.
- Subscribe. Every client receives the update at its nearest edge in under 50 milliseconds, presence and history included.
Global edge
One current. Every edge.
Write state once. VOLENT replicates it to the edges that need it and serves every client from the closest one, so the same update lands everywhere at the same moment.
Built for realtime
Everything that moves state, end to end.
Live streams
Typed channels for events, presence, and cursors. Backpressure and reconnection are handled for you, so a dropped network never means lost state.
State sync
Conflict-free shared state that converges automatically across every connected client.
Edge compute
Run functions next to the data. Validate, transform, and authorize in microseconds.
Observability
Every message, latency percentile, and connection is traceable in real time, so you can see exactly where a slow frame came from before a user does.
FAQ
Questions, answered.
How much does VOLENT cost?
VOLENT starts free for hobby projects and small teams, with usage-based pricing as your connections and message volume grow. You only pay for the throughput you actually use.
Does VOLENT integrate with my stack?
Yes. VOLENT ships SDKs for JavaScript, TypeScript, Swift, and Kotlin and works alongside your existing database and auth. You keep your stack and add one current for anything realtime.
How is VOLENT different from a message queue?
A queue moves messages between services. VOLENT moves state to clients at the edge, keeps it consistent, and serves reads locally, so the browser is fast, not just the backend.
What latency can VOLENT guarantee?
VOLENT targets sub-50ms reads from the nearest edge in every major region. Writes replicate in the order they happened, so clients stay consistent even under heavy load.