What RankCockpit can connect to
A selection of common systems from the SEO and marketing world. Some deliver data today, others can be attached through the adapter layer - the line is not drawn by a price list but by what you actually need.
Google Search Console
Google Analytics 4
DragonMetrics
Rankscale
DataForSEO
Google Docs & Drive
Supabase
OpenRouter
Firecrawl
Ahrefs
Semrush
Sistrix
SE Ranking
Moz
Screaming Frog
Majestic
Google Ads
Looker Studio
WordPress
Slack
Perplexity
Apify
Zapier
Microsoft 365All brands and logos named here are the property of their respective owners. Naming them describes technical connectability, not a partnership or an endorsement.
An adapter layer instead of hard wiring
Every data source sits behind a uniform provider interface. The system itself does not know where a ranking position comes from - it asks for rankings, and the adapter answers. Whether DragonMetrics, DataForSEO or something else entirely sits behind it is a question of one file, not of a rebuild.
That is why switching sources here is not a migration. Signals, thresholds, agent analyses and reports stay untouched, because they never talk to a vendor directly.
What delivers data in live operation
These sources are connected in the system and deliver every day: Google Search Console (clicks, impressions, positions), Google Analytics 4 (revenue relevance per page), DragonMetrics (rank tracking across several search engines), Rankscale (visibility in AI answers), DataForSEO (search volume, SERP fetches, keyword data), KeywordGraph (topical coverage) and Google Docs and Drive, where briefings and reports are written.
On top of that comes the foundation, which also runs in your own accounts: Supabase as the database and OpenRouter as access to practically every available language model. Which model does the work is your decision - globally or per client.
Swapping a connector means describing what you want
If you use other tools, you swap the adapter with Claude Code. You describe which source should deliver the data from now on, and your Claude writes the adapter against the existing interface. The system stays the same, only the data source changes.
That is exactly why the license does not grant a right of use but hands over the complete source code. A connector you are not allowed to change would not be a connector but a shackle.
The principle
Any system Claude Code can reach through an MCP server or an API can be attached to RankCockpit.
This is not a roadmap statement but a property of the architecture. Your CRM, your ticket system, your Slack, your shop, a backlink tool that does not even exist yet: if it has an interface, connecting it is a matter of hours, not quarters - and nobody has to prioritize it for you.
Your keys, your invoices
All access runs through your own accounts. You create the API keys, you see every invoice, you cancel what you do not need. There is no middleman looking at your data and no margin added on top of your usage.
To be honest, that also means this: rank tracking and AI visibility come from services you subscribe to yourself. RankCockpit does not replace those subscriptions, it makes their data usable.
What this means for you
- No lock-in to a single data source - the adapter is replaceable, the system stays.
- Your existing stack may stay. Ahrefs, Semrush and Sistrix still measure well.
- New sources need no approval from us - you attach them yourself.
- All costs run directly through your accounts, with no markup.
Open is not a claim, it is a licensing question
With the handover you receive the source code including every adapter. What you change about it is up to you.