The platform
Tools that already know about each other.
Six developer tools on one foundation: monitoring, product analytics, form handling, a content system a client can use without emailing anyone, feature flags, and the data platform underneath them. 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
- AnalyticsCollecting, nothing to buy
- CMSRunning, nothing to buy
Monitor, Analytics, Forms, the CMS and Flags all run today. The data platform answers over its API and its console is still being finished. Nothing on this site can be bought, because billing is the piece that is not built, and nothing here has a customer. This page says what is true today and gets updated when that stops being true.
The three with a page of their own
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 watches uptime, certificates, domains and scheduled jobs too. Flutter and Next.js today.
Unreal Ops Analytics
Traffic and events on the project Monitor already watches.
Page views, custom events, visitors and sessions for the same project as your crashes, broken down by path, referrer, platform, country, device, release and environment.
Unreal Ops CMS
Let the client change the copy, not the layout.
Content types you define in a dashboard, edited by the people who own the words, delivered over an API to whatever the site is already built with.
The order they get built in
Every one has a site of its own, and each of those says what it does and what it does not in its first screen.
- Monitor
Running, nothing to buy
Crashes and errors, uptime with certificate and domain expiry, cron and heartbeat checks, and status pages, for Flutter and Next.js. The free plan is open.
monitor.unrealops.ai - Analytics
Collecting, nothing to buy
Page views, custom events, visitors and sessions on the same project Monitor reads, with breakdowns by path, referrer, platform, country, device, release and environment. Funnels and retention are not built.
analytics.unrealops.ai - Forms
Taking submissions, nothing to buy
A plain HTML form posts to an endpoint, the submission is stored, and it is forwarded to an email address or a signed webhook with every delivery attempt visible. File uploads are not built.
forms.unrealops.ai - CMS
Running, nothing to buy
Content types defined in the dashboard, atomic publishing, immutable revisions with rollback, scheduled publishing and live preview. No client site is live on it yet.
cms.unrealops.ai - Flags
Evaluating flags, nothing to buy
Flags per environment with percentage rollouts, evaluated in the client so a check is never a network call, and an audit that records what a flag was as well as what it became. Targeting by attribute or cohort is not built.
flags.unrealops.ai - Data Platform
Service running, placeholder name
Define tables and JSONB collections through an API and get real Postgres with real constraints and indexes, read with a project key instead of a database account per app. The console is still being finished, and the name is not settled.
data.unrealops.ai
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
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.
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 here is built by Unreal Ops. Nothing on this site can be bought yet, and nothing has a customer. When that changes, these pages change with it.
Monitor, in its own words: what it stores and what it drops, how long it keeps it, and who answers.