PRODSovereign European BaaS platformOpen Dashboard →
ACCUEIL/PRODUITS/REALTIME
REALTIME · NATIVE SYNC

Sync, presence,
broadcast.

Auto-negotiated WebSocket, SSE, and NATS. Presence, replay, guaranteed ordering, explicit backpressure. 1M connections per POP, sub-15ms p99 fanout.

14ms
P99 FANOUT
1M
CNX/POP
3
TRANSPORTS
app/dashboard/live.tsxTYPESCRIPT
const channel = aura.channel('sensors:live')
channel
  .on('postgres_changes', {
    event: 'INSERT',
    schema: 'public',
    table: 'sensors',
    filter: 'tenant_id=eq.${tid}',
  }, ({ new: row }) => render(row))
  .subscribe()
// Auto-negotiates WebSocket → SSE → NATS based on network
#
Feature set

From primitive synchronization to real-time multiplayer

3 auto-negotiated transports

WebSocket first, then SSE, then server-side NATS. The client selects the optimal protocol based on network conditions.

WS · SSE · NATS

Presence API

Who is currently in the room, custom state, join/leave events. Consistent hashing for cross-region state reconciliation.

< 20ms SYNC

Multiplex N channels

Open 1,000 channels over a single TCP connection. Atomic subscribe/unsubscribe with zero extra connection overhead.

N CHANNELS · 1 TCP

Backpressure & ordering

Guaranteed ordering per channel, configurable client buffer, explicit drop policy. No silent duplications.

EXACTLY-ONCE PER-KEY

Event replay

Replays the last N events upon reconnection. Configured per channel, default retention of 100 messages or 60 seconds.

REPLAY WINDOW · 60s

Collab cursors

Native collaborative cursor primitives for multi-user apps. Server-side adaptive throttling, client-side interpolation.

60 FPS · THROTTLED
#
Live feed

Real-time production stream inspect

Preview of an anonymized production stream. Every event is deduplicated and ordered per channel, fanning out in sub-15ms to all active subscribers.

STREAM · eu-west-3 · channel_id = LIVE_SAMPLE
LIVEFANOUT · 9msCLIENTS · 12,418
14:32:08.412INSERTsensors:live·{ device_id: "dvc_9f2a", temp: 24.7 }
14:32:08.510PRESENCEdoc:42·user_j8k joined · cursor@(340, 120)
14:32:09.001UPDATEorders:live·{ id: "ord_77c", status: "shipped" }
14:32:09.188BROADCASTchat:general·{ event: "typing", user: "ci_42" }
14:32:09.440INSERTsensors:live·{ device_id: "dvc_4a1", temp: 23.9 }
14:32:09.702PRESENCEdoc:42·user_n3e left
14:32:10.020DELETEsessions:live·{ session_id: "sess_0x4" }
14:32:10.155BROADCASTgame:room-8·{ event: "move", coords: [12, 44] }
#
Performance

Verified benchmarks, no marketing fluff

14ms
P99 FANOUT
Median 6ms — 1M concurrent clients, 12 active regions
1M
CONNECTIONS / POP
Per point of presence, standard edition
256KB
MAX MSG
Per message — automatic chunking beyond
#
Comparison

Aurabase · Supabase · Ably

FeatureAurabaseSupabaseAbly
TransportsWS · SSE · NATSWS onlyWS · Binary
Native presenceIncludedIncludedIncluded
Postgres CDCIncludedIncludedNo
Event replayConfigurableNoYes (Ably)
MultiplexingUnlimited100 channels200 channels
BillingConnection × minConnection × hrMessage × event
Open sourceApache 2.0MITProprietary
#
FAQ

Frequently asked questions

What is the difference between WebSocket, SSE, and NATS?+
WebSocket is bi-directional and our default transport. SSE is uni-directional server-to-client (useful behind restrictive corporate proxies). NATS is the inter-service transport inside our infrastructure — on an Aurabase VPC, you can hook your worker directly to NATS for sub-millisecond process-to-process latency.
Are messages guaranteed exactly-once?+
Exactly-once per key within a channel (ordering and deduplication via server-side message_id). Cross-channel is at-least-once — the SDK exposes seen_ids to deduplicate on the client side if needed.
How do you scale beyond 1M concurrent connections?+
Add POPs. Each POP accepts 1M connections. Presence state is partitioned using consistent hashing and replicated across 3 copies.
Can we filter Postgres CDC changes server-side?+
Yes. filter: 'tenant_id=eq.$1' is evaluated server-side against the WAL, so clients only receive changes that concern them. Postgres RLS policies apply to realtime events as well.
What about offline mode?+
The SDK maintains a local buffer (IndexedDB/AsyncStorage) and replays intents upon reconnection. Conflicts are resolved via optional vector clocks or configurable last-write-wins per channel.
What is the real pricing model?+
Free plan: 100 concurrent connections × 1h/day. Pro plan: 100k connections × total connection hours in the month at €0.015 per 1k connection hours. No per-message billing in the Pro tier.
REALTIME ENABLED BY DEFAULT

Open a channel and listen to production live.

Zero configuration required. One channel, three lines of code, a living dashboard.

No credit card required · 500 MB free · 50,000 MAU