RevenueOS
Install free
Self-hosted revenue automation

Connect once. Everything runs free.
Pay when you agree with the result.

RevenueOS reads your website, ads, leads and mailbox, lists what is costing you customers, fixes what you approve, and proves the change before you pay anything.

uvx revenueos demo https://yoursite.com

Last verified run: 2026-09-13 · two site fixes deployed by the executor and measured 0 → 1 · 210 tests passing · the record

Self-hosted. Your business context and results stay in your workspace; only the prompts for approved work go to the LLM you configure.
Recorded 2026-09-13: a fresh workspace connected to plausible.io, nothing else connected, model off. Every line is the product's own output; the run took 5 seconds.
What it connects to

Connect once. Act after your yes.

only after you approve what it measured ranks what comes next Reads your connected accounts Finds what costs you money Your yes one click, or nothing Does just what you approved Measures before → after your website · Stripe Google · Meta · mailbox site repo · WordPress site fix deployed campaign paused · call booked invoice sent · email drafted what it measured ranks what comes next Reads website · Stripe · ads · mailbox Finds what costs you money Your yes one click, or nothing Does site fix · pause · invoice · draft Measures before → after
Five steps, one gate. Everything left of Your yes is reading and thinking, and costs you nothing. Nothing to the right of it happens until you click, and every change that does happen is re-checked against the live account and written down as before → after.
Evidence

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.

revenueos today
TODAY — Plausible Analytics

  2 SEO opportunities found
  3 content opportunities
$0 pipeline generated
ApproveExecuteIgnore
revenueos results
RESULTS — Plausible Analytics
5 opportunities found · 1 executed · 1 measured
✓ [ 4] seo: seo-content-strategy   deliverable_written 0 → 1
RevenueOS today brief screen listing five opportunities found for Plausible Analytics — two SEO, three content, each with Approve, Execute and Ignore controls
The brief — every opportunity found, waiting on a decision.
RevenueOS results screen showing 5 opportunities found, 1 executed, 1 measured, with the seo-content-strategy action marked deliverable_written 0 to 1
The results ledger — what ran, and what it produced.

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.
How it works

Connect → Discover → Approve → Execute → Measure

One loop, running on your schedule. Every step writes to one place; nothing skips the approval step.

Connect Discover Approve Execute Measure
revenueos — a real run against plausible.io, 2026-09-13
SEO opportunity An SEO content plan: the searches to target and the pages to write
✓ deliverable_written 0 → 1

Fixes, not suggestions — and never without your yes. Everything runs free; you pay after the first measured result you agreed with.

See it, step by step

Six screens. That is the whole product.

RevenueOS: connect once by pasting your website
1 · Connect once. Paste your website; RevenueOS fills in your business profile and labels every guess.

Every screenshot is the real product running on the neutral example domain (example.com), captured 2026-09-13. Nothing here is mocked.

Agents at work

Eleven workers on a schedule. One list you decide from.

Reading your websiteweekly · Monday 06:00crawl, homepage signals, deployable fixes
Auditing your adsdaily 06:30 · every 6 h when connectedwaste, pacing, 414 controls
Finding prospectsdaily 07:00public data, gated: found · contactable · qualified
Drafting emailsweekdays 08:00one observed defect, one ask, linted before you read it
Reading the mailboxevery 10 minreplies, bounces, unsubscribes
Reading Stripedaily 06:15revenue, MRR, open invoices
Search Console / GA4daily 06:45queries losing clicks
Re-checking earlier actionsevery 5 minbefore → after on every executed action

Schedules are the shipped defaults (data/automations.json). Every run writes to TODAY; nothing sends, publishes or spends without your approval.

What happens after you connect

Day by day, not a feature list.

Day 0 — Connect

Give it your website. It reads the site, fills in your business profile and labels every guess. Add Stripe, your site's repo or WordPress, Google or Meta when you want more done.

Day 0 — Audit

Every page crawled, the homepage read for tappable phones, LocalBusiness schema, canonical, titles, descriptions, sitemap; ad exports or connected accounts run through the 414-control catalogue. Findings land on TODAY with Approve / Execute / Ignore.

Days 1–7 — First fixes ship

Each approved fix is deployed by RevenueOS itself where it can (git-hosted sites, WordPress) or handed to you as an exact change. Then it re-checks the live page and writes before → after next to the action.

Every week — Re-check and next action

Workers run on a schedule, prospects with live ad spend are found from public data, drafts wait for your read, wasting campaigns are queued to pause. revenueos next ranks what to do from what actually worked.

When you agree — Pay

Nothing is charged until RESULTS shows a measured change you approved. Then 14 more days free, then $99/month to keep it running continuously. One-shot runs and the panel never lock.

Pricing

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.

Community
$0
Install it. Connect your business. Run it by hand.
  • Manual runs of every worker
  • The daily brief, locally
  • The full skill catalogue
Also available as an MCP server and Claude Code plugin (RevenueOS SEO Auditor, Ads Auditor, Lead Discovery, Sales Follow-up, Marketing Intelligence, Revenue Monitor).
Install free
Pro
$99 / month
Turn it on and leave it running.
  • Continuous operation via the orchestrator
  • Advanced audits & automated monitoring
  • Historical reporting & persistent memory
Early access: we connect RevenueOS to your business, you see every finding on TODAY and approve each action, and you pay the first month only after the first measured result appears in RESULTS.
Get early access
Business
$299 / month
For teams running more than one brand.
  • Multi-brand workspaces & multiple users
  • CRM synchronization
  • Approval controls & centralized analytics
Not built yet. Today RevenueOS runs one business per install, and nothing in the software gates these. Tell us you want them and we will say where they are; do not pay for this tier expecting them now.
Request Business
Agency
$999 / month
Run it for your clients.
  • Multi-client account fleets
  • White-label reports & client workspaces
  • Full API access
Not built yet. One workspace per client already works (revenueos workspace new), but fleets, white-label reports and a documented API do not exist yet and nothing in the software gates them.
Request Agency
Compare every feature, tier by tier →
Install

Run it yourself, today

No account required for Community. Install it, connect your business.

# install
uvx revenueos demo https://yoursite.com   # nothing installed, one command
pip install revenueos   # or: uv tool install revenueos — to keep it

# 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>.

Honesty, by design

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.

Free audit

Point it at any site. Including a competitor’s.

RevenueOS reads a public web presence and nothing else — no account, no access, no credentials. Type a domain and it builds your command.

Install it free
$ revenueos demo plausible.io

Read-only. It crawls what is already public, reports what it cannot reach instead of guessing, and sends nothing to anyone.

Works with

It reads the stack you already pay for.

64 connectors ship in the box. These are the ones wired into a worker today — the rest are available to the skills.

Google AdsMeta Ads Google Analytics 4Search Console StripeShopify WordPressSMTP / IMAP PlausibleHacker News

Available to skills, not yet wired to a worker: Apollo Hunter Clearbit Semrush Ahrefs HubSpot Klaviyo + 47 more

Why this one

Four things you can check yourself.

01

Nothing acts without you

  • Workers only read and propose — they cannot send, publish or spend
  • Sending is additionally capped, suppression-listed and STOP-aware
02

It refuses to invent a number

  • An outcome is measured, no_effect, or unmeasurable with the reason
  • Our own proof page shows $0 pipeline because no lead was contacted
03

You own the install

  • MIT-licensed, self-hosted, SQLite state on your machine
  • Only the prompts for approved work reach the LLM you configure
04

Every part is attributed

  • Upstream repository, commit and licence recorded for each component
  • Copyleft code runs across a process boundary, never bundled in

Questions

The things people ask first.

Do I have to give you access to anything?

No. The audit reads your public web presence only — the same pages anyone can load. Connectors exist for Google, Meta, Stripe and others, but they are opt-in, stay read-only until you explicitly allow changes, and the install runs on your machine.

What stops it emailing my customers by mistake?

Workers are structurally incapable of sending. Only an action you approve can act, and sending is additionally bounded by a daily cap, a suppression list, a List-Unsubscribe header and reply-STOP handling.

Is there a free tier, or is it a trial?

Community is free permanently and is not a trial — every worker, the full skill catalogue, and the control panel. Paid tiers add continuous operation via the orchestrator; you always own the install either way.

How many customers do you have?

None yet. RevenueOS went public on 2026-09-12 and has zero paying customers, zero stars and $0 revenue. The proof page is a real run against a real company’s public site, not a case study, and there are no testimonials on this page because there is nobody to quote.

What does it not do?

Live ad-platform ingestion is CSV export only. Reddit monitoring is not built. Multi-brand and multi-user are single-workspace today. The authority-comparison endpoint returns HTTP 403 and is reported as unavailable rather than guessed.

Run it on your own site in a minute.

No account. No card. It reads what is public and tells you what it found.