RankMySEO SaaS vs the open-source toolkit (and the competitor matrix)

# RankMySEO SaaS vs the open-source toolkit (and the competitor matrix)

People keep asking me which RankMySEO they should use. Fair question. There are two products with one family name, and I will not pretend they are the same thing.

I’m Aris Setiawan. Senior full-stack, first Cursor Ambassador in Indonesia. I ship Next.js and AI-adjacent work for clients, and I maintain both the public toolkit and the private hosted SaaS because different teams need different ownership models.

Two products, one problem

The problem is simple: ranks without history are gossip. You need a loop that stores where you stood yesterday, not only a live peek that disappears when the tab closes.

How you run that loop is the fork.

The open-source toolkit

The public repo is https://github.com/madebyaris/rankmyseo. That is the OSS path: packages you install, adapters you wire, audits and agent tools you keep behind approval gates.

Choose OSS when:

• You want the loop inside your monorepo
• Your team can run and extend the stack
• You need framework adapters and custom agent surfaces
• You care about reading and changing the code in the open

Status stays honest: milestones are shipped, offline paths are verified, live connectors need your own setup. Docs live in the wiki on that same public repo.

If RankMySEO for you means “ship packages into our product,” start there.

The private SaaS

The hosted product source is https://github.com/madebyaris/rankmyseo-saas. That repo is private. I list it so the split is clear. You should not expect to browse SaaS source the way you browse the OSS tree.

RankMySEO SaaS is a clickable hosted MVP: persistent project history, background rank checks, daily SERP for project keywords. Overview, Keywords, Competitors, and Insights work. Proven on the diurusin.id demo. Not a chargeable public product yet. Stripe is not MVP.

Choose SaaS when:

• You want managed tracking without operating the tracking stack
• You need daily SERP history stored for you
• Marketing or SEO leads need a board, not a package install
• You are fine with a private hosted product next to the public toolkit

The Competitors tab and the keyword matrix

Competitors is where the SaaS earns its keep for comparison work. You are not only watching your own keywords. You are looking at how your project sits next to others on the same queries.

The keyword matrix is the practical view: your keywords across competitor domains, so gaps and overlaps are visible without exporting five CSVs into a spreadsheet ritual.

This is not a claim that you will beat every rival next week. It is a claim that the matrix is real UI on a working MVP, backed by stored snapshots, not a mockup slide.

Optional context from Overview helps when you jump back to project health after a competitor pass:

I keep the same product rule as the rest of RankMySEO SaaS: the UI shows history we store for your project. Rank checks run in the background. You read the board; you do not babysit the crawl path.

Ownership, not plumbing

OSS is the opposite ownership story: you host and extend the pieces you choose.

SaaS is the managed board: projects, keywords, competitors, and history you can reopen without operating the tracking stack yourself.

When to use which

Use the open-source toolkit if you are building SEO or agent loops into a product, you want Apache-2.0 code in the open, and your engineers will own deploy and extension.

Use RankMySEO SaaS if you want a hosted board for projects, keywords, competitors, and insights, with daily SERP history you do not operate yourself.

Use both if your eng team embeds the toolkit while growth watches the SaaS matrix. That is a normal split, not a contradiction.

Do not use either as a substitute for content quality. A matrix that shows you losing on a query still needs a better page. Tools measure. You ship the fix.

What I will not claim

I will not invent ranks, traffic charts, or a public launch URL beyond what is real. I will not say the SaaS source is publicly browsable. I will not say Stripe billing is ready. I will not invent a beta signup form URL.

What is real: clickable MVP, project history, background rank checks, daily SERP for project keywords, Overview / Keywords / Competitors / Insights working on the diurusin.id demo path, open beta next week.

Open beta next week

Open beta next week. Week of 2026-08-31, early September 2026.

Watch the site. For early access, reach out via https://madebyaris.com/services. Mentoring if you want a human in the loop. Build path if you need a Next.js product around this stack: https://madebyaris.com/services/nextjs-development.

If you only want the toolkit today, skip the wait and use the public GitHub: https://github.com/madebyaris/rankmyseo.

Closing

RankMySEO is a family name for two honest paths. OSS for self-hosted teams who live in the repo. SaaS for managed tracking and a competitor keyword matrix you can actually click.

Pick the ownership model that matches your team. Open beta next week for the hosted side. The public toolkit is already there for the code side.

Own the history. Then decide who you are competing with, and what you will ship next.