It's not a chat. It's a loop.
ONI doesn't wait for prompts. It studies your business, writes its own backlog, and ships something every cycle — all while you sleep. Read a real one below.
One paragraph in plain prose. What you're building, who it's for, what you're worried about. No forms, no toggles, no 47-question onboarding. ONI reads prose.
Arabic or English (or both). The brand voice ONI learns from this shapes every email and invoice it sends later.
A larger brain re-reads your brief, researches your market, decides which capabilities to turn on (inbox · proposals · invoices · analytics · …) and writes a prioritised backlog.
If something's ambiguous — pricing, rules, who the first invoice goes to — ONI stops and asks you in chat. Never plows ahead on a guess.
Every few minutes a cycle fires. ONI picks the highest-leverage task, ships the change (code · email · invoice · page), updates its memory, and moves on.
Morning email at 8am local time: one-line summary per cycle, link to the full log if you want to dig. Most days you skim it over coffee.
One cycle. Two minutes. Eight cents.
Below is a real cycle from one of our own projects. Every cycle — on your account too — produces a log exactly like this.
- Read memory.md + last 4 cycle summaries · found unfinished Stripe migration+00:00
- Picked top of backlog: “Add Stripe Checkout to /product/[slug]” · priority 10+00:04
- Wrote 3 files · +182 −9 · committed a4c9b12+01:18
- Build passed. Deployed to prod subdomain · SSL verified+02:03
- Noticed 2 inbound emails since last cycle · drafted replies · auto-sent 1 (template match) · flagged 1 for review+02:31
- Updated memory.md · cycle closed in 2m 47s · cost $0.08+02:47
You read logs like this in the morning, or you skip them entirely — it's your call. ONI ships either way.
Not a chat toy. An operator.
Reads every thread, classifies it, and replies from your brand voice. Threads ONI can't decide on surface as 'Needs you' — tell ONI what to do, it sends.
Drafts from templates + brand voice, mints a public sign link, tracks opens + responses, triggers the invoice draft on signature.
Auto-generates from accepted proposals · mints Stripe Checkout · chases overdue at day 3 / 7 / 14 · sends you the 'paid' ping.
Customer records auto-update from inbox + invoices. Team roster with roles. Pipeline stays current without you touching it.
Pageviews, top pages, referrer leaderboard. 8am local digest tells you what moved overnight.
Newsletter drafts · social posts in your voice · outreach campaigns. ONI writes, you approve, ONI sends.
Vision · facts · rules · decisions. Read before every reply, updated after every cycle. ONI never forgets what you told it last week.
What ONI tried, what happened, what it learned. Queryable before a retry — so the same mistake doesn't ship twice.
Per-project pgvector index + 5 auto-registered MCP servers so ONI can read your files, DB, analytics, and team in one call.
You steer. ONI runs the shop.
ONI ships 3 cycles: added Arabic meta tags, drafted next week's newsletter, chased overdue invoice #INV-007.
Email summary lands: what ONI did, what's next, one thread that needs your call on a contract edge case.
You open Home, type 'proposal for the Aqaba gig, 3-month retainer, emphasis on the analytics side' — ONI drafts + sends it before you finish coffee.
Stripe webhook fires: invoice #INV-014 paid. ONI logs it, posts to your private Slack, moves the CRM card to 'paid.'
ONI won't pack physical boxes, give regulated advice (tax, medical, legal), sign contracts on your behalf, or do anything that crosses a rule you set. If something's ambiguous, it pauses and asks. You're the CEO. It's the operator.
Every outbound communication can be set to “draft, ask, then send” until you're comfortable — then flip it to “auto” per capability. Trust ONI piece by piece, on your schedule.
Ready to let go of the ops?
Describe your business in a paragraph tonight. Read ONI's first morning digest tomorrow.