AI assistants and search decision

Bluesky Copilot

A small, single-developer replacement that offers basic drafting and posting via an LLM is realistic to build and maintain in-house; there is no evidence of durable moats on the supplied page.

Visit website

Built by Sousa, who ships 5 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off40 h to build

$20/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

  • Provide a lightweight web UI that fetches a user's feed, drafts suggestions with an LLM, lets the user edit, and posts back to the social account.

What it still won’t have

  • Brand trust and packaged onboarding
  • Any proprietary moderation or safety pipelines the vendor runs
  • Large-scale reliability, multi-user analytics, and cross-platform integrations
  • Ongoing product polish, UX research, and official support

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Bluesky Copilot 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal 'copilot' web app using React frontend, Flask (or Node/Express) backend, Postgres for storage, and a hosted LLM (OpenAI/GPT-compatible) for generation. Core features in scope: OAuth account connect, fetch and cache a user's recent feed, generate draft posts and summaries via the LLM, UI for editing and publishing drafts, persist published drafts and basic usage logs. Out of scope: enterprise analytics, multi-tenant billing, advanced moderation pipelines, and large-scale rate-limiting. Include error handling for failed API calls, retries, input validation, and unit/integration tests for auth, LLM calls, and posting flows.
How we checked1 sources · 2/3 runs agreed · evidence score 78

How the score was reached

  • Build verdict base78
  • Evidence score78

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.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded