A taxi meter for money on Lightning.
Flux streams sats continuously to a receiver — one keysend payment per tick — for as long as a session runs. Stop it at any instant and billing halts within one tick, guaranteed.
Real streaming payments
One Lightning keysend payment per tick interval, for as long as you let it run.
Stop is instant
Server-side state re-checked before every payment — nothing sent after stop.
Fully documented API
REST + WebSocket, API keys, webhooks, idempotency. See the reference.
Zero setup to try
Runs on a simulated Lightning backend by default — no node required.
This page is a reference client of the Flux API — it calls a server-side proxy so the API key never reaches your browser. Sign in to save your sessions to a real history.
Try the meter
Runs on Flux's simulated Lightning backend — no real sats, capped at 5 minutes / 5,000 sats for this demo.
How it works
Everything you see here runs against the real Flux API — the same one you'd integrate into your own product.
Sign in with email
No wallet, no setup. Your account is how Flux knows which sessions are yours.
Start a streaming session
Pick a rate and tick interval. Flux begins sending one keysend payment per tick immediately.
Watch it, stop it, review it
Stop instantly whenever you like. Every session and payment stays in your history afterward.
Common questions
Is this real money?
By default, no — Flux runs on a simulated Lightning backend with no real node required. The operator can connect a real LND node, in which case sessions send real keysend payments; check the account/settings page for which mode is active.
What happens to my sessions if I don't sign in?
You can still try the live demo on the homepage without an account. It's tagged as a public demo session and won't appear in any personal history, since there's no account to attach it to.
Can I really stop a session at any moment?
Yes — the server re-checks session state immediately before every single payment. Once a stop is acknowledged, no further payment is ever sent, even if one was about to fire.
Can I build my own product on top of Flux?
That's the point. The full REST + WebSocket API is documented and open — see the API Reference link above.