The platform
Tools that already know about each other.
Unreal Ops is building a small platform for the software we ship and for the people who ship their own: monitoring for crashes, uptime and the jobs that were supposed to run, then product analytics, form handling, a content system a client can use without emailing anyone, and feature flags. They share one account and one project structure, which is the whole point. Tools that agree with each other beat a vendor and a bill for each one.
Where this actually stands
- MonitorRunning, nothing to buy
- AnalyticsIn active development
- CMSIn active development
Monitor runs and takes real crashes from Flutter and Next.js apps, and it watches uptime, certificates, domains and scheduled jobs besides. Its free plan is open. Nothing on this page can be bought, and nothing has a customer. Analytics and the CMS are scoped and have no code yet. We would rather be early on this page than wrong on it, so it says what is true today and gets updated when that stops being true.
The products with a page so far
Unreal Ops Monitor
Crashes, uptime, and the job that was supposed to run.
Catches the crash your user never reported, groups it with every other instance of the same fault, and tells you which release it started in. It also notices when the site stops answering, when a certificate is about to lapse, and when the nightly job did not fire. Flutter and Next.js are the platforms available today.
Unreal Ops Analytics
Product analytics for the apps and sites you already monitor.
Events, funnels, retention, and dashboards for the same project Monitor already knows about, with privacy controls that are on by default.
Unreal Ops CMS
Let clients edit their own site copy.
A headless content system where the client changes the phone number themselves, and still cannot break the layout doing it.
The order they get built in
Monitor first, because it is the one that already runs. Then Analytics, then Forms, then the CMS, then feature flags and remote config. Two of these have no page of their own yet, and they are listed anyway so the order is public rather than implied.
- 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.
One foundation underneath
The reason to build several tools instead of one is that they are genuinely different jobs. The reason to build them together is that the seams between separate vendors are where small teams lose their afternoons: two logins, two ideas of what a release is, two bills, and no way to ask whether the drop in signups and the spike in errors are the same event.
One account
One login, one set of teammates, one bill. Adding the second tool is not a second procurement conversation.
One project
A project means the same thing to every product on the list: the same app, the same releases, the same environments. Nothing to reconcile by hand.
One SDK surface
The same package your app already imports for errors is the one that sends events. Not two vendors competing for the same lifecycle hooks.
Standing on open source
Some of these rest on open source that is already good, and we say so rather than pretending otherwise. Monitor uses the open source Sentry SDKs, unmodified, pointed at ingestion we run ourselves, so an app on a platform Monitor supports switches by changing one DSN string. The platforms it supports are named one by one on the Monitor page, and a platform is never on that list merely because an SDK exists for it.
The CMS is built on the MIT licensed Payload core, with the multi tenant layer that lets one install serve many client sites added on top. Building on well maintained foundations is not a shortcut we are hiding. It is the reason a very small team can ship these at all, and the reason you would not be trapped in a private format later.
Get involved early
Tell us what you would need from this.
The scope is public because it is still moving. If you ship apps, or you maintain sites for other people, the things you would need are the things worth building first.
Goes to Travis directly. Reply within a day, and an honest answer about how far off any of this is.
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.