We Ran OpenSEO: An Open Source SEO Suite, Plus the Fine Print
The video uses a digital avatar of Erick Grau, CEO of Chibitek.
SEO tools are one of those line items every marketing team pays for and nobody in IT thinks about. So when an open source project promises the same kind of keyword research, rank tracking and site audits, on a server you control, people notice. OpenSEO has been climbing GitHub fast. Before anyone on your team spins one up on a company account, here is what we saw.
What Did We Actually Do?
On Tuesday, Nov. 17, 2026, just after midnight ET, we installed OpenSEO in a locked down sandbox at commit 2df84ff (version 0.1.27). We ran the project's install with network access, then cut the network and ran its unit tests: all 2,033 passed, across 289 test files. During the install, the only network destination our logs recorded was the npm package registry. During the offline tests, our logs recorded no outbound calls at all.
We did not run Docker, deploy to Cloudflare, sign up for the hosted service, or connect a DataForSEO account. We used no real accounts or keys. So we are not claiming we stood up a live install. Everything below comes from our own run logs, the public repo, or the project's own website docs.
What Is OpenSEO?
In plain words, OpenSEO is an open source SEO suite. The GitHub description and the project website both call it an "Open source alternative to Semrush and Ahrefs."
You can run it three ways, according to the README and the website: self-host it with Docker, self-host it on your own Cloudflare account, or use the hosted version. The README says "a hosted subscription is $10/month," and the pricing page lists the same starting price.
Repo facts, dated:
Stars: 27,983 when we checked on Nov. 17, 2026, at 12:29 AM ET. On Nov. 20, 2026, at 4:08 PM ET, the GitHub API showed 28,455.
License: MIT, per the GitHub API and the repo's license file.
Commit we tested: 2df84ff, committed Nov. 13, 2026, at 3:10 AM ET.
Since then: the main branch has moved to commit af3f995 (Nov. 20, 2026, 12:03 AM ET), and the latest release is v0.1.31. We rechecked every fine print item below on main, and the docs still say the same thing.
What Was the Good News?
Credit where it is due:
Open source under MIT. The license is confirmed by GitHub and the project website.
A public security policy. SECURITY.md gives a private email address for reporting problems and asks people not to open public issues for security bugs. GitHub shows the policy on the repo page.
Cloudflare Access is documented. The Cloudflare self-host guide has a section titled "Cloudflare Access: the most secure option," and the website version says the same.
No install hook of its own. The root package.json has no install or postinstall script. In our run, the install only reached the npm registry.
The tests ran clean offline. 2,033 of 2,033 passed with the network cut.
We found nothing that looks like malware in what we scanned and ran. That is not a guarantee, but it deserves credit.
What Is the Fine Print?
These come from the project's own docs, not our guesses. Each one is in the repo docs, and each is backed by either the project's website or its code.

1. A Cloudflare self-host sends usage heartbeats until you opt out. The operations doc says OpenSEO "collects anonymized telemetry for core usage events: heartbeats with aggregate counts (installs, users, projects, feature usage) tied to a random install ID." It also says no URLs, keywords, prompts or emails are collected. The code sends those heartbeats to PostHog. To turn it off, the doc says to "set OPENSEO_TELEMETRY_DISABLED=1" and redeploy. This is documented, not hidden, but it is easy to miss.

2. The first visitor becomes the administrator. The Cloudflare guide is blunt about it: "registration closes once the first account exists, and until then anyone who finds the URL could claim the installation." The Docker guide gives the same advice: create the administrator account "before you put the installation on the internet." Both are repeated on the website.

3. Sign-in is email and password by default, and one mode has no login at all. Both self-host guides say you sign in with email and password accounts, and the Cloudflare guide calls Cloudflare Access the most secure option. There is also a Docker mode called AUTH_MODE=local_noauth that runs "without sign-in, as one admin user." The Docker guide says to use it "only where the network already controls who can reach the app," and SECURITY.md says plainly that it "has no login by design. Run it behind your own auth."
4. SEO data comes from your own DataForSEO key. The search data itself comes from DataForSEO. If you self-host, you bring your own key and pay DataForSEO directly, according to the docs and the website. The README adds that the hosted service makes money "by charging 28% extra for every request we make to DataForSEO." Either way, that key is a paid production secret.
What Should You Do If You Try It?
Put Cloudflare Access, or your own SSO and MFA, in front of any install that is not only on localhost.
Create the admin account yourself, immediately, before the URL goes to anyone.
Decide on telemetry before you deploy. If you self-host on Cloudflare and do not want usage heartbeats, set the opt-out and redeploy.
Keep the DataForSEO key out of git, name an owner, and add the app to your software inventory.
These four rules are Chibitek guidance, based on our sandbox run and the project's own docs. A self-hosted SEO suite is still an app with accounts, a paid API key and data about your marketing. It belongs on the same list as everything else you manage.
Key Points of OpenSEO
OpenSEO is an MIT licensed SEO suite you can self-host on Docker or Cloudflare, or use hosted from $10 a month.
Chibitek installed it in a sandbox at commit 2df84ff on Nov. 17, 2026, and all 2,033 unit tests passed offline. We did not run a live install. Verdict: PASS WITH NITS.
A Cloudflare self-host sends anonymized usage heartbeats until you opt out and redeploy.
After a fresh deploy, the first visitor becomes the administrator, so claim it right away.
Default sign-in is email and password; Cloudflare Access is the documented more secure option; local_noauth has no login by design.
Frequently Asked Questions
Did you run a live install? No. We installed the project and ran its unit tests offline. We did not run Docker, deploy to Cloudflare, or use the hosted service.
Is OpenSEO open source? Yes, under the MIT license.
What does it cost? The software is free to self-host. You pay for your own hosting and for DataForSEO usage. The hosted version starts at $10 a month, according to the README and the pricing page.
Does it send my keywords anywhere? The operations doc says the self-host heartbeats do not include URLs, keywords, prompts or emails. Your searches do go to DataForSEO, because that is where the data comes from.
Is the first-admin issue a bug? No. It is how the setup works, and the docs warn about it clearly. It only becomes a problem if someone shares the URL before the admin account exists.
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. If your marketing team wants to self-host an SEO suite, contact us at hello@chibitek.com and we can talk through where it should run and who should own it.
Claim the admin account before you share the URL.
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 (2df84ff91461cc55b6c8bb98f3ce0f195d2e463d, committed Nov. 13, 2026, 3:10 AM ET), fetched from GitHub on Nov. 20, 2026, then against the current main branch (af3f995, Nov. 20, 2026), the OpenSEO website docs, and Chibitek's own sandbox run logs from Nov. 17, 2026.
README at the tested commit (description, hosted price, 28% DataForSEO markup)
SECURITY.md at the tested commit (private reporting, local_noauth has no login by design)
Cloudflare self-host guide at the tested commit (email and password sign-in, first visitor admin, Cloudflare Access)
Cloudflare self-host operations guide at the tested commit (telemetry and opt-out)
Self-host telemetry code at the tested commit (PostHog heartbeats, opt-out variables)
Docker self-host guide at the tested commit (first admin, local_noauth)
Root package.json at the tested commit (version 0.1.27, no install or postinstall script)
OpenSEO website: Open source SEO (MIT, self-host options, DataForSEO costs, 28% fee)
OpenSEO website: Pricing (hosted plan from $10 a month)
OpenSEO website: Cloudflare self-hosting and Docker self-hosting
Star count: 27,983 on Nov. 17, 2026, 12:29 AM ET, and 28,455 on Nov. 20, 2026, 4:08 PM ET, from the GitHub repository API








Comments