Automation and integrations decision
Anonymous Bot for Slack
A single developer can reproduce the core anonymous-posting functionality in ~20 hours; the product has no documented proprietary moat on the retrieved page and reasonable open-source analogues exist.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off20 h to build
$10/mo3 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Receive message from a Slack user (slash command or DM) and re-post it into a target channel as an anonymous bot
What it still won’t have
- Hosted UIs, uptime SLAs and customer support
- Scaling, analytics/dashboarding and moderation tooling
- Any proprietary integrations or convenience features not implemented
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Anonymous Bot for Slack does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build an Anonymous Slack bot using Node.js + Express (or Slack Bolt) and a small PostgreSQL or SQLite database. Core features: Slack App OAuth and verification, slash command or DM handler to accept message input, server-side sanitization and content-length checks, repost messages into configured channel(s) as a generic bot identity, simple persistence for banned users and audit logs, HTTPS deployment (DigitalOcean or Railway), structured logging and tests for request signature validation and forwarding. Out of scope: advanced moderation UI, multi-tenant billing, analytics dashboard. Include error handling, unit tests for signature validation and forwarding logic, and a README with deployment steps.
How we checked
How the score was reached
- Build verdict base78
- 3/3 assessment runs agreed+4
- Evidence score82
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productAnonymous Bot for Slack | Send Anonymous Messages
Integrity checks
What held up, and what did not.
