Start free
$0Free
100Kreliable publishes / month
1Mdeliveries / month
200peak connections
100publishes / second
1 daymaximum replay
2 projects3 team members64 KB payloads
Start building
Simple foundations. Flexible capacity.
Start free.
Scale without a rewrite.
Every plan includes reliable events, state, signals, presence, authorization, recovery, and observability. Plans change capacity and retention—not correctness.
Free is $0Paid checkout opens after live cost verification
Orastack plans and prices
Monthly plan
Coming soonLaunch
500Kreliable publishes / month
5Mdeliveries / month
2Kpeak connections
500publishes / second
7 daysmaximum replay
5 projects10 team members64 KB payloads
Talk to usMonthly plan
Coming soonPro
2Mreliable publishes / month
25Mdeliveries / month
10Kpeak connections
2Kpublishes / second
1 monthmaximum replay
20 projects30 team members64 KB payloads
Talk to usMonthly plan
Coming soonScale
8Mreliable publishes / month
100Mdeliveries / month
50Kpeak connections
10Kpublishes / second
3 monthsmaximum replay
100 projects100 team members64 KB payloads
Talk to usMonthly plan
Coming soonBusiness
32Mreliable publishes / month
500Mdeliveries / month
250Kpeak connections
50Kpublishes / second
6 monthsmaximum replay
500 projects500 team members64 KB payloads
Talk to usCustom agreement
Coming soonEnterprise
Customreliable publishes / month
Customdeliveries / month
Custompeak connections
100Kpublishes / second
1 yearmaximum replay
Custom projectsCustom team members64 KB payloads
Talk to usIncluded everywhere
Correctness is not
a premium feature.
A capacity limit can change with a plan. The meaning of an accepted event cannot. Core security and recovery behavior stays consistent from Free through Enterprise.
✓Reliable eventsDurable acceptance and replay
✓Scoped authorizationShort-lived client grants
✓Reconnect recoveryCursor-based gap replay
✓State + signalsVersioned truth and fresh motion
✓PresenceScope-based and eventually consistent
✓Environment isolationCredentials, data, and usage separated
Usage without surprises
Measured clearly.
Accounted for exactly.
Physical deliveries
A connection matching multiple target scopes is billed once for a deduplicated network delivery.
Separate replay
Replay reads and retained storage are tracked independently so retention can evolve without changing event semantics.
Auditable ledger
Billing-grade usage is idempotent, reconcilable, and separate from sampled dashboard analytics.
Questions
Before you choose a plan.
What happens when replay retention expires?
The client receives an explicit resync_required condition. Query adapters can invalidate and refetch authoritative application state; Orastack never silently skips the gap.
Does client acknowledgement mean my handler finished?
No. It means the Orastack SDK accepted the event into its local dispatch path. Business-level processing should still be idempotent where required.
Are signals and presence reliable events?
No. Signals optimize for freshness and may be dropped or coalesced. Presence is eventually consistent. Durable application truth belongs in state, events, or your database.
What happens at a plan limit?
Orastack rejects new cost-bearing operations with a stable rate_limited error before performing expensive work. Existing durable events remain recoverable for their configured retention window.
Free means production behavior