Unreal Ops Platform
Unreal Ops Analytics
Product analytics for the apps and sites you already monitor.
Crash data tells you what broke. Analytics is meant to tell you what was happening before that, and what happens on the days when nothing breaks at all: which screens people reach, where they stop, and whether the people who came back this month are the same ones who came back last month.
Scoped, not yet written. There is no code, no beta, no waiting list that turns into a login, and nobody using it. It is the next product after Monitor. This page exists so you can tell us what you would need from Analytics while changing it is still free.
What it is meant to do
Most small products do not need a data warehouse. They need five numbers, correct, on one screen, without a quarter of engineering time spent assembling them. That is the target.
Because Analytics shares a project with Monitor, a drop in completion on a funnel step and a spike in errors on the same release are the same investigation rather than two tools you line up by hand and by eye.
What Analytics is intended to do
None of this is built yet. It is written down here so the scope is public and you can argue with it.
Events
A typed event call from the same SDK surface the rest of the platform uses, so you are not wiring a second vendor into your app to answer one question.
Funnels
An ordered set of steps with the drop between each one, over whatever date range and release you choose.
Retention
Cohorts by first seen week, so growth and churn stay separable numbers instead of one line that only ever goes up.
Dashboards
The handful of numbers the business actually runs on, pinned to one screen, without building an internal reporting tool first.
Privacy controls
Events you define rather than blanket auto capture, no third party advertising identifiers, and deletion by user id when somebody asks.
The same project as Monitor
One project can receive from an app and from the website that sells it, reported together rather than side by side.
Who it is for
- Teams already using Monitor who want product data under the same account.
- Developers who want events without a heavyweight analytics install.
- Operators who need five reliable numbers, not a hundred unreliable ones.
One account, one project, one SDK surface
Analytics is not a separate product with a separate login. It reads the same project as Monitor: same app, same releases, same environments, same teammates.
That is the entire reason to build it here rather than bolt on somebody else's. Two tools that already agree on what a release is beat two tools you reconcile by hand every time something looks wrong.
The rest of the platform
Analytics shares its account and its project structure with everything else on this list. Tools that already know about each other, rather than a vendor and a bill for each one. This is the build order, and only the first of them runs today.
- Monitor
Running, nothing to buy
Crashes and errors, uptime with certificate and domain expiry, cron and heartbeat checks, and status pages. Available for Flutter and Next.js. The free plan is open; nothing is purchasable.
- Analytics
Next, no code yet
Events, funnels, retention and dashboards on the same project Monitor already reads.
- Forms
Planned, no code yet
Form handling for the sites we build and the ones we maintain for other people. It exists on this list because we pay somebody else for it today, and a form endpoint is a small enough thing to own.
- CMS
Planned, no code yet
A client edits their own copy without being able to break the layout. One install, many client sites.
- Feature Flags and Remote Config
Planned, no code yet
Turn something on for some people, and change a value in a shipped app without shipping a new build.
Register interest
Shape what Analytics becomes.
Nothing is written yet, which is precisely why this is the useful moment to speak up. Requirements are cheap to absorb before the schema exists and expensive afterwards.
We are collecting requirements, not signups. Say what you measure today and what you gave up trying to measure, and it will shape what gets built.
Every product on this page is being built by Unreal Ops. Monitor runs and takes real crashes; its free plan is open, nothing here can be bought, and nothing here has a customer. When that changes, this page changes with it.
Monitor, in its own words: what it stores and what it drops, how long it keeps it, what it cannot be relied on for, and who answers.