Technology
Built on Cloudflare, from the first event to the lake
The edge, the live profiles and the event lake all run on Cloudflare's network. A decision is made next to the user's profile, in the request, and the same events feed analytics without a second pipeline.
The pieces
What it is built on, and what that gets you
Your sites and apps call UserCurrent through its SDKs, wherever they are hosted. Behind the SDKs, every part runs on Cloudflare.
Your sites and apps
- Web SDK
- Server SDK
- Astro integration
Run wherever you host them
Cloudflare
- Edge Workers decide
- Durable Objects hold live profiles
- Lake Durable Objects write the event tables
- R2 stores the event lake
Close to every user, on one network
Open Iceberg tables
- Events
- Sessions
- Per-user daily rollups
Read them with any Iceberg reader
Workers
Decisions close to every user
Events and decisions are handled on Cloudflare's network, near the user, so a page can change in the same request.
Durable Objects
A live profile for every user
Each profile updates as events arrive, so the next decision already reflects what the user just did.
R2 and Apache Iceberg
Your events in open tables
Events are stored as Iceberg tables, not in a proprietary store, so a query engine or notebook you already use can read them.
R2 SQL
Analytics without a warehouse
Trends, funnels and retention read the same events that drive decisions. There is no second pipeline to keep in sync.
Workers AI
AI that never holds up a page
AI works on the profile after events, outside the render path. Anything it generates is labeled as AI.
One network
Fewer moving parts
The edge, the profiles, the lake and the AI run on one platform, so there is no separate database, queue or warehouse vendor to wire together.
Talk to us
Tell us what you run and what you want to change.
Why this button?
It is this page's own suggestion for now. As you read, this site keeps a small profile of who each page is for and what it is about, in your browser, and picks this button from it. Nothing is sent.