live · mainnetme · ochk · io
federation-custodied · self-custody-ready
§ integrate · sandbox

Try the model. Before you sign up.

Pick a preset that matches your shape (or customize), pick the traffic tier closest to your scale, and see what the four-way split — site paid · OC fee · user cashback · site rebate — looks like for one month. The simulator runs the same computeFees() that the production verifier runs; numbers below are exact, not approximate.

§ sandbox · live

pick a preset, pick a traffic tier, see the math.

Simulates one month of representative traffic against the chosen integrator config. Updates as you switch presets or scale traffic. Both denominations on every aggregate.

§ pick a preset
Breez breez.example
✓ config valid
account creation
2,100 sats70% to user
session opened
80 sats70% to user
payment authorized
0.50% of amount75% to user
payment method connected
420 sats70% to user
§ traffic tier
§ monthly aggregate · mid · 10,000 MAU
site pays · gross
30,860,000sats
$29,317
oc platform fee · 20%
6,172,000sats
$5,863
user cashback
+22,602,000sats
$21,472
site rebate balance
2,086,000sats
$1,982
120,000 sessions20,000 payments600 new accounts0 kyc upgrades
§ vs the legacy stack
legacy total
$2,145/mo
auth0 $240 · stripe $1750 · twilio $80 · kyc $75
me.ochk.io · site cost
$29,317/mo
30,860,000 sats gross
saved
$-27,172/mo
and you pay your users 22,602,000 sats

> simulation uses representative event volumes per traffic tier. real integration replaces these with your actual telemetry. legacy quotes drawn from auth0 b2c starter, stripe standard 2.9% + $0.30, twilio sms, averaged kyc vendor pricing.

§ ship this config

Like the math? Push this exact config to /developer/config (the in-memory v1 store) or copy the JSON into your oc.config.update() call. Production wires this through the federation index against your project_key.

open dashboard ↗

what the simulator is doing

For each traffic tier, the simulator generates a representative one-month event mix:

  • sessions — MAU × sessions-per-user. Class C billable atom; one envelope per session, free intra-session signins.
  • payment authorizations — MAU × payments-per-user. Class B percentage-of-amount events at the chosen rate.
  • account creations — proxied by the tier's monthly signup volume. Class A one-time events.
  • kyc upgrades — proxied by the tier's monthly KYC volume. Only counted when the integrator config has kyc_tier_upgrade enabled.

Each event runs through the canonical computeFees(cfg, payment_amount?) that /api/platform-fee-policy publishes and that production envelopes are signed against. The platform fee is fixed at 20% of gross. The user cashback comes from the integrator's configured user_share_pct. The site rebate is whatever's left.

Legacy-stack quotes for comparison are based on Auth0 B2C Starter, Stripe Standard (2.9% + $0.30 per payment), Twilio SMS at $0.008 each, and averaged KYC-vendor pricing. Real invoices vary; we'll model your exact stack against your actual statements at /contact.

next step

Like the math? Go to /integrate for the drop-in code samples and the live configurator. Want OC to model against your actual usage? Email /contact with your stack and we'll send back a paired comparison within a business day.