Introducing RankMySEO SaaS: rank history you actually own

# Introducing RankMySEO SaaS: rank history you actually own

I already open-sourced RankMySEO as a toolkit you can drop into your own stack. That path is still the right one if you want packages, adapters, and full control in your repo.

But a lot of people asked a simpler question: can I just track ranks somewhere hosted, keep the history with the project, and not babysit crawlers on a Friday night?

That is why RankMySEO SaaS exists. It is a private hosted product next to the public OSS toolkit. Same family. Different job.

I’m Aris Setiawan. Senior full-stack, first Cursor Ambassador in Indonesia. I ship Next.js and AI-adjacent product work for clients, and I build RankMySEO because rank talk without history is just storytelling.

Why a hosted product next to the OSS toolkit

The open-source RankMySEO toolkit is for teams who want to install, adapt, and own the loop in code. Packages, adapters, audits, agent tools with approval gates. If that is your world, stay there.

RankMySEO SaaS is for the other case: you want a clickable product that stores SERP history for your projects, runs rank checks in the background, and shows Overview and Keywords without you operating the tracking stack. The SaaS source lives at https://github.com/madebyaris/rankmyseo-saas. That repo is private. I mention it so the split is honest: public toolkit vs private hosted product. Do not expect to browse the SaaS source on GitHub like the OSS tree.

Honest product state today: this is a clickable hosted MVP. Persistent project history. Background rank checks. Daily SERP for project keywords. Overview, Keywords, Competitors, and Insights are working. I have proven that path on the diurusin.id demo. It is not a chargeable public product yet. Stripe is not in the MVP.

What you see on Overview

Overview is the home screen for a project. You land, you see the project context, and you get a read on how keywords are doing without jumping into five tabs first.

The point is not a vanity dashboard. The point is history you own. When ranks move, the movement lives in our database, not in a screenshot folder on someone’s laptop.

Check ranks queues the work in the background. The board stays responsive. You come back to results in your project history, not a spinner that owns the page.

If you have used tools that freeze the page while a crawl runs, you already know why that matters. Overview is for reading the state. The queue is for doing the work.

Keywords: daily SERP and history you can trust

Keywords is where the focus keyword work lives day to day. You attach keywords to a project. The system runs daily SERP for those project keywords. Snapshots stay with the project so you can look back instead of guessing.

I care about this more than fancy charts. If your rank history evaporates when a tool changes pricing or an account dies, you do not own the loop. RankMySEO SaaS keeps that history with the project. The UI reads what we stored, not a one-off live peek.

You still need judgment. A keyword at position 8 that never converts is not a win because the chart went green. The SaaS gives you the time series. You decide what to ship next.

Built so history sticks

The product rule is simple: the board you open should show ranks you can trust tomorrow, not a live peek that vanishes when the tab closes.

When you check ranks, the work runs in the background. The UI stays fast. Results land in your project history, so Overview and Keywords stay useful the next day.

You do not operate crawl infrastructure. You open a project and read what changed.

If you want the self-hosted toolkit instead, the OSS path is still https://github.com/madebyaris/rankmyseo. Same family name. Different job.

What is in and what is not

In for the MVP you can click today:

• Project Overview that reflects real stored data
• Keywords with daily SERP and history
• Competitors and Insights (more on the matrix in a follow-up post)
• Background rank checks that do not freeze the UI
• Persistent project history you can reopen later

Not in the MVP:

• Public paid billing (Stripe is not MVP)
• Pretending this is a finished chargeable launch
• Invented traffic numbers or fake rank screenshots for marketing

I would rather ship an honest beta than a landing page that lies.

Open beta next week

Open beta next week. That is the week of 2026-08-31, early September 2026.

I am not inventing a beta signup URL here. Watch the site, and if you want early access, reach out through https://madebyaris.com/services. Mentoring fits if you want a human on the loop. If you need a Next.js product built around SEO tracking, the Build path is https://madebyaris.com/services/nextjs-development.

If you prefer to stay in code and self-host the toolkit, start with the public GitHub and skip the wait.

Who this is for

Use RankMySEO SaaS if you want managed tracking, daily SERP history you do not have to operate yourself, and a UI that already works for Overview and Keywords.

Use the OSS toolkit if you want packages in your monorepo, custom adapters, and full control of how agents and audits run.

Plenty of teams will use both: toolkit in the product codebase, SaaS for the marketing or SEO lead who just needs the board.

Closing

RankMySEO SaaS is the hosted answer to where do my ranks live over time. The OSS toolkit remains the answer to how do I wire this into my stack.

Overview and Keywords are real. Project history is real. Background rank checks are real. Open beta next week. Reach out via services if you want in early, or watch the site as we open the door.

I built this because I got tired of SEO conversations that never had yesterday’s position. Own the history. Then decide what to ship.