Every App: A Prompt That Replaces Your SaaS With Open Source

By Indie Kings | October 26, 2026

Updated October 26, 2026: Every App is a new MIT licensed project on GitHub with the blunt pitch of making every SaaS open source, shipping a stack of self hosted apps that run on a Cloudflare Workers plan that costs 5 dollars a month.

Image: data center server racks via Wikimedia Commons.

A SaaS alternative catalog that walks by prompt

The every-app/every-app repository on GitHub, currently 169 stars and 3 forks over 844 commits, carries the tagline make every SaaS open source, and it comes from the team behind OpenSEO, an open source SEO toolkit the project calls an alternative to Semrush and Ahrefs that has pulled in 25,000 stars. The idea scales that one success into a catalog: the flagship apps are OpenSEO, OpenCRM, OpenAnalytics and OpenMail, each a hosted, self owned replacement for a subscription product rather than a code drop you have to stand up yourself. There is an Every App MCP Gateway as well, which puts AI agents first on the guest list: where a consumer site sees forms, an agent can inspect and act on the same data through the Model Context Protocol.

The Gateway security model

The architecture leans entirely on Cloudflare's serverless stack: everything runs on Workers, with D1 as the database, R2 for object storage and KV for key value state, so there are no containers to babysit and no hosting bill outside the Workers plan. The project reports that its 5 dollar a month Workers Paid plan hosts hundreds of apps, which collapses the usual self hosting arithmetic of paying per container. Security is centralized in a Cloudflare Gateway: apps get no public address of their own, the Gateway holds the API keys and fronts traffic, and teams that want user level protection can layer Cloudflare Access on top for authentication. That inversion, one public entry point and a pile of private applications behind it, is the piece that makes a $5 plan viable without turning every app into a leak surface.

Install paths

Two onboarding routes. The classic one is npm: install the package with npm install -g everyapp, then run everyapp setup --domain against a Cloudflare zone, a path the project describes as taking roughly 15 minutes. The new one is to hand the agent the keys: paste a prompt into Claude Code, Codex or Cursor and the setup walks itself, which is why the MCP Gateway and the prompt path ship together. The project publishes an llms.txt at everyapp.com/llms.txt so models can read its own docs, and the README is clear that the project is in early development, worth watching rather than betting a revenue line on yet.

Repo card

Item	Detail
Project	Every App, every-app/every-app on GitHub
Pitch	Make every SaaS open source, hosted on your own Cloudflare account
License	MIT
Repo stats	169 stars, 3 forks, 844 commits
Team lineage	OpenSEO, 25,000 stars, positioned against Semrush and Ahrefs
Flagship apps	OpenSEO, OpenCRM, OpenAnalytics, OpenMail
Stack	Cloudflare Workers, D1, R2, KV, fully serverless
Cost	Workers Paid at 5 dollars a month reportedly hosts hundreds of apps
Security	Gateway holds API keys, apps have no public address, Cloudflare Access optional
Install	npm install -g everyapp, then everyapp setup --domain, about 15 minutes, or a prompt into Claude Code, Codex or Cursor
Agent support	Every App MCP Gateway, llms.txt for model readable docs
State	Early development

FAQ

What is Every App?
An MIT licensed open source project that ships ready to run alternatives to commercial SaaS products on your own Cloudflare account, built by the team behind OpenSEO.

How much does it cost to run?
The stack is fully serverless on Cloudflare Workers, and the project claims its 5 dollar a month Workers Paid plan is enough to host hundreds of apps.

Which apps does it include?
The flagship set is OpenSEO, OpenCRM, OpenAnalytics and OpenMail, with the catalog meant to expand beyond them.

How does it keep apps secure?
Each app has no public address; a Cloudflare Gateway fronts the traffic and holds the API keys, and Cloudflare Access can be added for user authentication.

How do you install it?
Install the npm package and run setup against your domain, which the project says takes about 15 minutes, or paste a prompt into an agent like Claude Code, Codex or Cursor.

Is it mature?
No, the README marks it as early development, so treat it as a promising watch list item rather than a drop in replacement today.

Bottom Line

Self hosting usually dies at the invoice, one container bill per application until the stack costs more than the subscriptions it replaced. Anchoring the whole catalog to one 5 dollar serverless plan, with keys quarantined in a Gateway that agents can also talk to, is an honest answer to that math, and coming from a team that already turned the OpenSEO experiment into 25,000 stars gives the claim more weight than most. It is early, but the shape is right.

Sources

GitHub every-app/every-app README (stack, Gateway model, install steps, licensing), accessed 26 October 2026
GitHub API repository metadata for every-app/every-app and the OpenSEO reference, accessed 26 October 2026