Connect your business.
RevenueOS finds opportunities, executes approved revenue work, and measures what happened.
One real run, on a real business
Not a mock-up. This is what revenueos today and
revenueos results showed after a live run against a real company's
public web presence.
TODAY — Plausible Analytics 6 content opportunities $0 pipeline generated
RESULTS — Plausible Analytics 6 opportunities found · 1 executed · 1 measured ✓ [ 1] seo: seo-content-brief deliverable_written 0 → 1
- ✓Date 2026-09-12.
- ✓Business Plausible Analytics (plausible.io) — a real company's public web presence, used read-only. No email was sent to anyone.
- ✓Found a real crawl of plausible.io, a Hacker News search through the relevance gate, and the content registry matched against the business's channels together produced 6 content opportunities across seo, blog and twitter.
- ✓Executed 1 — Claude ran the vendored
seo-content-briefskill and wrote a 14 KB deliverable in 1 m 23 s. - ✓Measured
deliverable_written 0 → 1— what RevenueOS can observe for a content action without Search Console connected.
What's honest about these numbers
- ✓The crawl found no defects on plausible.io — every page already had a title, description and body text — so no SEO fix opportunity was fabricated to fill the brief.
- ✓The free authority-comparison endpoint returned HTTP 403 during this run and was reported as unavailable, not guessed.
- ✓The Claude relevance gate rejected all 3 Hacker News candidates it considered — nothing was surfaced just to look busy.
- ✓$0 pipeline generated is true: no lead was contacted on this run. The pipeline number only moves when the outreach loop runs with a real mailbox connected.
Read the full command transcript → · docs/proof.md on GitHub
Connect → Discover → Approve → Execute → Measure
One loop, running on your schedule. Every step writes to one place; nothing skips the approval step.
Answer the questionnaire — in the CLI or the panel's onboarding form. RevenueOS reads your business, competitors, channels and offer.
Workers analyse your site, ad exports, lead lists, mailbox and Hacker News — deterministically, or with an LLM where judgment is needed.
Every finding becomes one action, and every action waits. Nothing sends, publishes or spends without your decision.
Approved actions run: the approved email sends, or the approved skill runs and writes its deliverable.
RevenueOS checks what actually happened: a re-crawl, a reply, the next export's delta, a deliverable written.
Community runs this loop by hand, one command at a time. Pro and above turn it on and leave it running.
Free to run. Simple to grow.
RevenueOS is self-hosted software — you always own the install. Paid tiers unlock capability via a signed licence key issued after checkout.
- Manual runs of every worker
- The daily brief, locally
- The full skill catalogue
- Continuous operation via the orchestrator
- Advanced audits & automated monitoring
- Historical reporting & persistent memory
- Multi-brand workspaces & multiple users
- CRM synchronization
- Approval controls & centralized analytics
- Multi-client account fleets
- White-label reports & client workspaces
- Full API access
Run it yourself, today
No account required for Community. Install it, connect your business.
# install pip install "git+https://github.com/unempyd/revenueos" # or: uv tool install git+https://github.com/unempyd/revenueos # connect your business and turn it on revenueos init # the questionnaire → company-context/ + revenueos.yaml revenueos run all # run every worker once revenueos today # the brief revenueos serve # the control panel: http://127.0.0.1:8791
From source: git clone https://github.com/unempyd/revenueos && cd revenueos && uv sync
&& (cd orchestrator && npm install), then run the same
commands with uv run in front. Optional: ANTHROPIC_API_KEY
(or ant auth login) turns on the LLM paths — relevance gating,
personalised openers, running skills — without it every worker still runs
deterministically. SMTP_PASSWORD + smtp.host in
revenueos.yaml enables real sending; REVENUEOS_DRY_RUN=1 writes
emails to data/outputs/ instead. Already have a licence key? Run
revenueos license install <key>.
Built in the open
RevenueOS is MIT-licensed. It includes permissively-licensed
open-source components, with full attribution for every one of them — upstream
repository, commit and licence — recorded in NOTICE.md. RevenueOS
never bundles copyleft code into the licensed product; where a copyleft component is
used at all, it runs as an external service across a process boundary, not inside
the product itself.
This isn't a from-scratch rewrite dressed up as one — it's glue code, business context, approval and measurement logic built new, over components whose licences allow exactly this kind of reuse.