every-app/open-seo / Chapter 1

Programming /

The_Day_The_SEO_Bill_Arrived

# The Day the SEO SaaS Bill Arrived > A $7,200-a-year habit died in 2026. The open-source SEO tools that replaced it are not cheaper Semrush — they are a different product, designed around an AI agent instead of a human dashboard. ## Key Takeaways - The "expensive" SaaS SEO stack (Semrush + Ahrefs + a couple of long-tail add-ons) typically runs a small agency $400–$700 a month per seat, or roughly **$7,200 a year per analyst**. - A new generation of open-source tools — OpenSEO, SerpBear, SEONaut, LibreCrawl, SEOMachine — replaces most of those seats at **$50 minimum top-up + pay-as-you-go data**, often under $30 a month for a single user. - The interesting part is not the bill. The interesting part is the architecture: Cloudflare Workers, D1, R2, an MCP server, and pre-built agent skills. The bill is a side effect of a different product decision. - This series is a teardown of `every-app/open-seo`, the most ambitious of the new tools — the one that ships a hosted product *and* self-host, *and* an MCP server, *and* seven agent skills — and what its decisions mean for the rest of the category. --- I watched the GitHub star counter on `every-app/open-seo` cross 2,000 in May 2026, and I thought about the first time I paid for Semrush. It was 2017. I was a freelance technical writer with a vague SEO side hustle, and the price felt reasonable: $99 a month, all the data I could want, a UI that taught me what a SERP was. I renewed for eight years. By the time I cancelled in 2025 I was paying $449 a month for a "Guru" seat, and I had not logged into the site in eleven months — Claude was doing the SERP lookups for me, the way I once did them by hand. That gap is the story. The bill kept climbing. The product kept receding into the background. The dashboard stopped being where the work happened. I went looking for a replacement and ended up reading the source of a tool I had never heard of, with a README that opens with the words "Open source alternative to Semrush and Ahrefs." Twenty-eight stars turned into 2,000 in a year. The Discord is busy. The maintainer replies to issues in hours. The DataForSEO cost table in the README is printed in plain numbers, not in "contact sales." What I want to do in this series is treat OpenSEO as a case study in what a real, working, open-source SEO tool looks like in 2026 — not because it is the only one, but because it is the most opinionated. The opinion is: stop trying to be Semrush. Be the workflow an AI agent already wants to do. Ship the dashboard as an inspector for what the agent did, not as the place where the work happens. A quick map of what I am going to argue across the next four chapters. **Chapter 1** is the cost economics. The headline is misleading: "open source" sounds like "free," but open-source SEO tools still pay for data, and the cheapest path is not always the one you expect. Iceland — a country DataForSEO Labs does not cover — costs 96 credits per keyword research call, three times the standard 32. I will walk through the act

Chapter 1 of 5 6m Article Learning path

The Day the SEO SaaS Bill Arrived

A $7,200-a-year habit died in 2026. The open-source SEO tools that replaced it are not cheaper Semrush — they are a different product, designed around an AI agent instead of a human dashboard.

Key Takeaways

  • The "expensive" SaaS SEO stack (Semrush + Ahrefs + a couple of long-tail add-ons) typically runs a small agency $400–$700 a month per seat, or roughly $7,200 a year per analyst.
  • A new generation of open-source tools — OpenSEO, SerpBear, SEONaut, LibreCrawl, SEOMachine — replaces most of those seats at $50 minimum top-up + pay-as-you-go data, often under $30 a month for a single user.
  • The interesting part is not the bill. The interesting part is the architecture: Cloudflare Workers, D1, R2, an MCP server, and pre-built agent skills. The bill is a side effect of a different product decision.
  • This series is a teardown of every-app/open-seo, the most ambitious of the new tools — the one that ships a hosted product *and* self-host, *and* an MCP server, *and* seven agent skills — and what its decisions mean for the rest of the category.

---

I watched the GitHub star counter on every-app/open-seo cross 2,000 in May 2026, and I thought about the first time I paid for Semrush. It was 2017. I was a freelance technical writer with a vague SEO side hustle, and the price felt reasonable: $99 a month, all the data I could want, a UI that taught me what a SERP was. I renewed for eight years. By the time I cancelled in 2025 I was paying $449 a month for a "Guru" seat, and I had not logged into the site in eleven months — Claude was doing the SERP lookups for me, the way I once did them by hand.

That gap is the story. The bill kept climbing. The product kept receding into the background. The dashboard stopped being where the work happened.

I went looking for a replacement and ended up reading the source of a tool I had never heard of, with a README that opens with the words "Open source alternative to Semrush and Ahrefs." Twenty-eight stars turned into 2,000 in a year. The Discord is busy. The maintainer replies to issues in hours. The DataForSEO cost table in the README is printed in plain numbers, not in "contact sales."

What I want to do in this series is treat OpenSEO as a case study in what a real, working, open-source SEO tool looks like in 2026 — not because it is the only one, but because it is the most opinionated. The opinion is: stop trying to be Semrush. Be the workflow an AI agent already wants to do. Ship the dashboard as an inspector for what the agent did, not as the place where the work happens.

A quick map of what I am going to argue across the next four chapters.

Chapter 1 is the cost economics. The headline is misleading: "open source" sounds like "free," but open-source SEO tools still pay for data, and the cheapest path is not always the one you expect. Iceland — a country DataForSEO Labs does not cover — costs 96 credits per keyword research call, three times the standard 32. I will walk through the actual DataForSEO price sheet the project publishes in its README, line by line, and show what an indie founder versus a five-person agency actually pays in 2026.

Chapter 2 is the architecture. The wrangler.jsonc file at the root of the repo is 73 lines long and contains most of the story: a single D1 database, an R2 bucket, two KV namespaces, two Cloudflare Workflows, a Durable Object that runs the onboarding chat agent, and a fifteen-minute cron. The interesting decision is not the platform — it is that the hosted version and the self-hosted version are the same code, gated by a single boolean in the environment. The hosted version is metered through Autumn, the self-hosted version is not. The bill lives at the data-fetch boundary, not in a separate billing service.

Chapter 3 is the MCP server. This is the part of the product I underestimated. OpenSEO exposes a Model Context Protocol server at https://app.openseo.so/mcp, and it ships seven pre-built agent skills (seo-project-setup, seo-coach, keyword-research, keyword-clustering, competitive-landscape, competitor-analysis, link-prospecting) that you install in Claude Code, Cursor, or Codex. The combination — MCP for tools, skills for *what to do with the tools* — is the actual moat. The dashboard is a debugger for the agent.

Chapter 4 is the competitive landscape. OpenSEO is one of five serious open-source SEO projects. SerpBear is rank tracking only. SEONaut and LibreCrawl are technical-SEO crawlers. SEOMachine is a Claude Code workspace for content writing, not a data platform. They do not all do the same thing, and the most common mistake I see in "best open-source SEO tools" lists is conflating them. I will close with a four-row table that tells you which one to install on Monday morning.

I should say up front what I am *not* going to argue. I am not going to claim that open source is morally superior, that SaaS is bad, or that you should cancel your Semrush subscription today. The DataForSEO cost table the project publishes makes a clear case that open source is cheaper at low volume. It makes a less clear case — possibly a worse case — at high volume. I will show you the crossover point.

I am also not going to argue that the AI-agent surface is a gimmick. It is not. The interesting thing about pointing Claude at OpenSEO's MCP server, instead of pointing it at DataForSEO's MCP server directly, is that the agent can save its work back to a project the user actually owns, instead of leaving you to trust whatever it claims to have found. That changes the trust model in a way I want to dig into.

Two things to keep in mind as you read. First, OpenSEO is at version 0.0.22, which is to say it is young, moving fast, and changing its mind about some of the things I will describe. The maintainer has shipped twenty-one minor releases in roughly twelve months. Second, the project is candid about the fact that "open source" and "free" are not the same word. The code is free. The data costs money. The cheapest way to use OpenSEO is the $1 free credit DataForSEO gives new accounts, the most expensive way is whatever your SERP-API bill ends up being at scale.

I started this analysis thinking the headline would be the price tag. It is not. The price tag is a downstream consequence of three upstream decisions: the project does not own the data, the project does own the workflow, and the workflow is designed to be driven by an agent. The price tag is what falls out of those three choices when they are made honestly. The interesting questions are the upstream ones.

If you have ever opened a Semrush invoice and felt a small but persistent resentment, this series is for you. If you are a maintainer staring at a competitor's release notes, parts of it are for you too. If you are an agent builder wondering what a real MCP server looks like in production, Chapter 3 is the one you want.

The first question I want to answer is the obvious one. What does it actually cost?

---

References:

---

The cost of an SEO stack is not a number. It is a relationship between the data you can afford to look up and the decisions you can afford to make.