For solo developers, freelancers and studios
Every stackEvery accountEvery clientOne registry.
Ori keeps a live registry of what each project is made of — hosting, database, DNS, certificates, payments — across every account you manage.
| Resource | Lives in | Cost | Status |
|---|---|---|---|
Hosting2$60/mo | |||
| northwind-webCritical | Northwind account | $20/mo | Deployed 3h ago |
| northwind-apiCritical | Client's GCP | $40/mo | Deploy failed 2h ago |
Database2$40/mo | |||
| northwind-dbCritical | Northwind account | $25/mo | Healthy — 62% of plan |
| northwind-staging | Northwind account | $15/mo | Healthy — branch active |
Domains2$2.00/mo | |||
| NCnorthwind.comCritical | Client's Namecheap | $14/yr | Renews in 34 days |
| northwind.shop | Northwind account | $10/yr | Active — proxied |
6 of 16 resources shown — the rest cover DNS, certificates, storage, repos, payments, email, and monitoring.
Connect everything. Nothing falls through.
Real stacks are never fully reachable by API — there is always an inherited VPS, a registrar with no useful API, or a bucket in a client account you can barely see. Ori records those with the same standing as everything else: a registry that only holds half your stack isn’t a registry.
Added by hand
- A private hosting box
- A Raspberry Pi at home
- A client’s on-prem server
- That old VPS
- Anything else
A few seconds each, and they sit in the same list as everything else.
Syncs automatically
| Provider | Auth | Status |
|---|---|---|
| GitHub | OAuth | Connected |
| Supabase | Token | Connected |
| Railway | Token | Token expires in 12 days |
| Google Cloud | OAuth | Connected |
| AWSAWS | API key | Connected |
| Cloudflare | API key | Connected |
| Stripe | API key | Connected |
Connect the account once and the registry stays current on its own.
Alerts
Find out before your client does.
Not metrics and thresholds — control-plane events, like a certificate close to expiry or a webhook that stopped delivering. Set an alert once and Ori emails you the moment one fires, no dashboard required.
Every resource in a project rolls into one bar, sorted worst-first and color-coded end to end — the state of an entire stack reads in seconds.
Tap or hover a segment to see the resource behind it.
Set the alert
Certificate expiry, 7 days out — no thresholds to tune.
Something breaks
*.northwind.com quietly slips inside the window.
Ori emails you
Northwind Co · Certificate · expires in 6 days.
Straight to Cloudflare
Renew it from the account that issued it.
When it breaks
The story is already assembled.
A deploy goes out, errors climb, a service recycles, the edge starts timing out, payments queue up. Five vendors each hold one piece and none of them can see the chain. Ori joins them, so the question “what happened?” has one answer instead of five tabs.
Synthetic example — illustrative, not live production data.
- Railway
Deploy finished
[email protected] is live on production
- Sentry
Error rate rising
Timeouts on /checkout spike after the release
- Railway
Service restarted
Worker recycled after health check failures
- Cloudflare
Edge timeouts
Origin latency crosses the alert threshold
- Stripe
Webhook deliveries failing
Payment events queue while the API is unstable
- Ori
System recovers
One correlated story — not six browser tabs
Built for the one person doing five people’s job.
From a single side project to fifteen client stacks — plans that scale with what you’re actually running.
Solo
$9/month
Your own projects.
- Up to 3 projects
- Full registry — synced and manual
- Email alerts
- Cross-vendor timeline
Studio
For client work$39/month
The working freelancer or small studio.
- Up to 15 projects
- Separate credentials per client account
- Everything in Solo
- Priority on new integrations
Agency
$99/month
When client count stops being the constraint.
- Unlimited projects
- Everything in Studio
- Shared access for your team
Same list for every tier — pick Solo, Studio, or Agency when Ori opens.
Indicative pricing while Ori is pre-launch — the waitlist is how we find out whether these numbers are right. The first 100 people on it keep 50% off for as long as they stay subscribed.
Questions
Add it by hand. Providers sync automatically as integrations ship; everything else is a manual entry that sits alongside them. A stack Ori can only half-connect still deserves a complete record.
No. Ori is read-only — it observes and correlates, and links you into the vendor’s own dashboard for anything that needs changing.
Encrypted at rest, with read-only scopes wherever the provider offers them. Credentials belong to your organization and you choose which projects can use each one.
No. Ori shows you that Sentry is reporting new errors and links you there. It is the layer above your tools, not a replacement for any of them.
No date yet — that would be a made-up number. The waitlist decides the order people get in, and the first 100 keep a permanent discount.
Join the waitlist
Ori is in early access. Join the waitlist and you’ll get in ahead of general availability — the first 100 keep a permanent discount.