It's a self-hosted revenue department. One command, `revenueos demo https://yoursite`, reads a website and lists what's costing it customers: tappable phone numbers, LocalBusiness schema, canonical tags, titles and descriptions, sitemap. It says which fixes it would deploy itself, but it does not deploy anything without approval.
That's the core rule: every action waits for a human to approve it. The executors that change things, deploying a site fix, pausing an ad campaign, booking a call, sending an invoice, all refuse to run unless you've explicitly switched on "allow changes" for that connection.
The honesty rules are enforced in code, not just policy. No metric gets synthesized. A lead without a contact email can never be marked "qualified," full stop. Outreach drafts get linted and refused if they contain placeholders or leftover prompt scaffolding. Deliverables are stripped of anyone's payment links or identity before they go out.
Measured result, on our own site: it found two defects, we approved the fix, it pushed two commits itself, and the live page carried both tags within 20 seconds. canonical_present went 0 to 1, local_schema_present went 0 to 1.
We also ran lead discovery from public OpenStreetMap data with no credentials, in Adelaide: 525 businesses with a website, 432 reachable, 70 with live ad tags, 42 of those with a business email. We report all three numbers separately, found, contactable, qualified, because collapsing them into one number is exactly the kind of thing that gets lied about in this space.
What it can't do yet: live Google Ads or Meta connections need your own OAuth client. Hosting is self-hosted or run-for-you. Revenue so far is $0, customers 0. This is a Show HN.
It's MIT-licensed, `pip install revenueos`, v0.2.4. You run it free; you only pay after a measured result you agreed with.
unempyd•4h ago
That's the core rule: every action waits for a human to approve it. The executors that change things, deploying a site fix, pausing an ad campaign, booking a call, sending an invoice, all refuse to run unless you've explicitly switched on "allow changes" for that connection.
The honesty rules are enforced in code, not just policy. No metric gets synthesized. A lead without a contact email can never be marked "qualified," full stop. Outreach drafts get linted and refused if they contain placeholders or leftover prompt scaffolding. Deliverables are stripped of anyone's payment links or identity before they go out.
Measured result, on our own site: it found two defects, we approved the fix, it pushed two commits itself, and the live page carried both tags within 20 seconds. canonical_present went 0 to 1, local_schema_present went 0 to 1.
We also ran lead discovery from public OpenStreetMap data with no credentials, in Adelaide: 525 businesses with a website, 432 reachable, 70 with live ad tags, 42 of those with a business email. We report all three numbers separately, found, contactable, qualified, because collapsing them into one number is exactly the kind of thing that gets lied about in this space.
What it can't do yet: live Google Ads or Meta connections need your own OAuth client. Hosting is self-hosted or run-for-you. Revenue so far is $0, customers 0. This is a Show HN.
It's MIT-licensed, `pip install revenueos`, v0.2.4. You run it free; you only pay after a measured result you agreed with.
Repo: https://github.com/unempyd/revenueos
electric_mayhem•30m ago