We Ran Every App: A Gateway for Internal Apps, Plus the Fine Print
The video uses a digital avatar of Erick Grau, CEO of Chibitek.
Your team can build an internal tool faster than ever. Hosting it, putting sign-in in front of it, and keeping its keys under control is still the hard part. A project that promises to handle all of that is going to get attention from MSPs and IT leaders. Before anyone on your team points one at a client's Cloudflare account, here is what we saw.
What Did We Actually Do?
On Tuesday, Nov. 17, 2026, just after midnight ET, we installed Every App in a locked down sandbox at commit 48667b2, with CLI version 0.4.1. We ran the project's install with network access, then cut the network and ran the command line tool's unit tests: 1,108 passed and 16 were skipped, including the live tests that need a real account. We built the everyapp CLI and printed its help and version.
We did not log in to Cloudflare. We did not run setup, install a real app, configure Cloudflare Access, or try the Mac desktop app. We used no real accounts, domains, or keys. So we are not claiming we stood up a live gateway. Everything below comes from our own run logs or from the public repo.

What Is Every App?
In plain words, Every App is a gateway that deploys and runs internal apps on your own Cloudflare account. The README puts it this way: "one command sets up a Gateway in your Cloudflare account, and your team signs in once to use every app."
It is open source under the MIT license. It had 874 GitHub stars when we checked it on Nov. 17, 2026, at 12:29 AM ET. When we checked again on Nov. 20, 2026, the GitHub API showed 1,049. The project has kept moving since our run: the main branch is now at commit 0b948c3 (Nov. 18, 2026) with CLI version 0.4.2. The fine print below is still in the README and security doc on main.
The README is also upfront about its stage: "EveryApp is in early development, so expect some rough edges."
What Was the Good News?
Credit where it is due:
Open source under MIT. The license file and the GitHub API both say MIT.
A long, public security document. It opens with what the project calls its one rule: "a person's credential stops at the Gateway." It also lists its own known gaps, ranked by severity.
A leak-check workflow. The repo runs gitleaks on pull requests and pushes to main, so a committed secret gets caught before it goes public.
A private way to report holes. The security doc points you to a private vulnerability report on the repository.
Access and SSO built into the CLI. One command puts "Cloudflare Access in front of the Gateway and its apps," and another lets people sign in with "Google, Microsoft, GitHub, Apple, Cloudflare or your SSO, beside passwords."
A quiet install. The project's own install hook is a local build of its SDK. In our run, the install only reached the npm registry, and the offline tests only talked to local test servers on the same machine.
We found no hidden malware in what we scanned and ran. That deserves credit.
What Is the Fine Print?
Here is the part I respect: the project lists its gaps in the open. These are the project's words, not our guesses.

1. Browser app installs can spend an account-wide token. The security doc rates this one high. A setting called browser app installs is off by default. If you turn it on, an owner or admin signed in within 10 minutes installs a release with the Cloudflare deploy token, "which can rewrite every Worker and database in the account."

2. First-party app hosts share a session cookie. The doc rates this medium: "First-party app hosts share the control plane's session cookie." It also says "Access mitigates." In other words, turn on Cloudflare Access.
3. The spend cap does not cover every vendor. Also rated high. Caps count only the cost a provider reports, and the doc names OpenAI, Anthropic, Workers AI, Groq and remote MCP servers as never moving the cap, "so a default cap doesn't bound them." Its advice is to "use a provider-side limit where offered."
4. Setup is not free-tier only. The README says "You need a Cloudflare account on Workers Paid ($5/month) and a domain on Cloudflare." Cloudflare's own pricing page lists the Workers Paid plan at a minimum charge of $5 USD per month for an account, plus usage beyond what is included. We did not run setup, so we can't tell you what a live gateway costs to run.
5. It is alpha. The security doc says "Every App is alpha and open source" and "There is no bounty." That is honest. It also means you should not treat it as finished production software.
What Should You Do If You Try It?
Treat it as early software. Read the security document before you put client data in it.
Turn on Cloudflare Access, and leave browser app installs off until you understand the deploy token.
Set provider-side spend limits, because the built-in cap does not cover every vendor.
Name an owner, keep secrets out of git, and add the gateway and its apps to your inventory.
These four rules are Chibitek guidance, based on our sandbox run and the project's own docs. A gateway like this hosts apps. It doesn't replace your PSA, your inventory, or the person who owns each app.
Key Points of Every App
Every App is an MIT licensed gateway that deploys and runs internal apps on your own Cloudflare account.
Chibitek installed it in a sandbox at commit 48667b2 on Nov. 17, 2026, ran 1,108 CLI unit tests, and built the CLI. We did not run setup or log in to Cloudflare. Verdict: PASS WITH NITS.
The project publishes its own ranked list of known gaps, including an account-wide deploy token when browser app installs are on, a shared session cookie on first-party hosts, and a spend cap that does not bound every vendor.
Setup needs Cloudflare Workers Paid and a domain on Cloudflare.
The README calls it early development, and the security doc calls it alpha.
Frequently Asked Questions
Did you run a live gateway? No. We installed the project, ran the CLI's unit tests offline, and built the CLI. We did not log in to Cloudflare or run setup.
Is Every App open source? Yes, under the MIT license.
What does it cost? The README says setup needs Cloudflare Workers Paid, which Cloudflare lists at a minimum of $5 USD per month for an account, plus a domain on Cloudflare. Usage beyond the included amounts is billed by Cloudflare.
Is the deploy token a problem by default? The setting that lets browser installs spend it is off by default. The project rates the risk high if you turn it on.
Let's Review Before You Install
At Chibitek, we look closely at tools like this before they get anywhere near a client account, with no geek-speak. A gateway that can deploy into a Cloudflare account deserves the same review as any other admin tool. Contact us at hello@chibitek.com to talk through how you test tools like this, and where they should run.
Early software. Read the security doc first.
We make IT effortless so you can create, disrupt, and grow!
Follow Chibitek on YouTube at @chibitekmsp, and follow Chibitek on LinkedIn.
Sources
Every repo claim was checked against the file at the tested commit (48667b23a1b7ccbe470409220955b6f40a0de1e6, committed Nov. 16, 2026, 5:18 PM ET), fetched from GitHub on Nov. 20, 2026, then against the current main branch (0b948c3, Nov. 18, 2026) and Chibitek's own sandbox run logs from Nov. 17, 2026.
README at the tested commit (what it is, early development, Workers Paid and a domain)
docs/security.md at the tested commit (the one rule, known gaps top 12, alpha, private reporting, no bounty)
Cloudflare Workers pricing (Workers Paid, minimum charge of $5 USD per month for an account)
Star count: 874 on Nov. 17, 2026, 12:29 AM ET, and 1,049 on Nov. 20, 2026, about 12:40 PM ET, from the GitHub repository API








Comments