# LopeBase

> LopeBase is the ops console for people who run several small SaaS products. It reads the tools each product already uses (analytics, search, revenue, errors, uptime, email, bank) and shows growth, revenue, uptime, and SEO for every product on one screen. Every operator action is recorded in an audit log with the exact before and after.

## Key facts

- Console and signup: https://app.lopebase.com/signup
- Set up from a terminal: run `npx lopebase` in a project folder. It scans the stack, signs in or creates an account in the browser, and hands setup to a coding agent.
- MCP server for AI agents: https://app.lopebase.com/api/mcp. `list_sources` and `read_source` let an agent read search and analytics data for every connected site (Search Console, Bing, GA4, Plausible, PostHog, Cloudflare Web Analytics). Aggregates only, read-only. `get_health`, `query_metric`, and `get_digest` return the same numbers as the console.
- Pageviews: LopeBase can count a product's pageviews itself with one tag (`<script defer src="https://app.lopebase.com/lb.js" data-site="KEY">`): pages, sources, and visits, no cookies, no visitor ids. MCP tools `get_pageview_snippet` and `get_pageviews`; ask the human before adding the tag.
- Uptime: every product's address checked every 15 minutes. With the LopeBase Adapter, declare `services` (database, queue, workers, other hosts) and use `<app>/api/lopebase/health` as the uptime address to watch each one.
- Connectors are read-only unless a page says otherwise. LopeBase never connects to a product's database; a product's own records come through the LopeBase Adapter (`@lopebase/adapter`), a small handler the product mounts at /api/lopebase.
- Pricing (USD per month): Free $0 (1 product, 1 operator, 30 days of audit history), Studio $29 (3 products, 3 operators, 1 year), Portfolio $99 (10 products, 10 operators, full history), Agency $299 (no limit). Monthly AI credits: 50, 500, 2,000, 8,000. Bring your own AI key to use no credits.
- Yearly billing: two months free on every paid plan. Studio $290 a year, Portfolio $990, Agency $2,990, with the same limits as monthly.
- Made by Jackalope Digital. Contact: https://lopebase.com/contact
- Privacy: https://app.lopebase.com/legal/privacy
- Terms: https://app.lopebase.com/legal/terms

---

## LopeBase: one ops console for every SaaS product you run

URL: https://lopebase.com/

Growth, revenue, uptime, and SEO for every SaaS product you run, on one screen. LopeBase reads Stripe, PostHog, and Search Console. Free for one product.

Run every product from one console.
Growth, revenue, traffic, uptime, and SEO for all of your SaaS products in one place. LopeBase reads the tools you already use, so you stop opening ten tabs to see how things are going.
Start free, no card needed Take the tour 14 days of Portfolio, then free for one product. No card. Read-only keys, no database access.
What you can do with LopeBase
Automate blog posts in your voice
Get a weekly briefing on what changed
Track your Domain Rating week by week
See what competitors published this week
Find the revenue at risk this month
Find where Hacker News talks about you
Spot searches stuck on page two
Find the pages worth working on next
See which pages Google has indexed
See MRR for every product at once
Watch uptime on every site
Turn an outage into a status note
Run an SEO audit with one button
Turn each article into social posts
Get a weekly digest of every product
Let your coding agent set it all up
See every feature Start with a goal
What do you want to get done?
Pick the job that matters most right now. Each one works with the tools you already use, and every one is in the free plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 06 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Your tools in. Answers out.
Each product already sends its numbers somewhere: payments to Stripe, visits to PostHog, searches to Google. LopeBase reads them with read-only keys and turns them into four questions you can answer at a glance.
Stripe
PostHog
Search Console
Analytics
Bing
Sentry
LopeBase Are we growing?Visitors and signups, every product Is revenue healthy?MRR, recent charges, and past-due subscriptions$4,210 Are people finding us?Searches, rankings, and what to write+3 pos Is everything up?Uptime, errors, and page speed3 of 3 up Or start from your terminal.
Run one command in a product's folder. It reads what the code already uses, you sign in or create a free account in the browser, and your coding agent does the rest of the setup.
$ npx lopebase 01It reads your stack. Dependency and config file names only, after you say yes. Never your .env file or your code.
02You connect this computer. Sign in or create an account, check that the short code matches your terminal, and press Connect.
03Your agent sets it up. Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent connects the services it found and asks you when it needs a key.
Works on macOS, Linux, and Windows with Node 18 or later. More on agents and MCP
A morning with LopeBase
One tab, a few minutes, every product. Here is a normal Monday when growth, revenue, and SEO live in one place.
See the week across every product.
Overview puts revenue, visitors, signups, and search clicks for each product side by side, with anything that needs you on top. No logging in to six dashboards.
Overview $4,210MRR18,420Visitors90Signups Needs you Down for 4 minutes overnightProduct three, back up nowOpen 2 subscriptions past dueProduct two, Stripe
Find the next search win.
SEO lists the searches where a product sits on page two, and the pages people see but rarely click. Each one is a click away from a draft.
SEO On page two uptime monitoring for side projectsPosition 12.1, seen 3,400 timesWrite about this track mrr across stripe accountsPosition 14.8, seen 2,100 timesWrite about this
Get a draft that is checked, not guessed.
It is written in your voice, links to your own posts, and is checked before it can publish: every link opens, any video is real, and it actually answers the search.
Product one / articles Uptime monitoring for side projects Every link opensLinks to your own postsSounds like your siteAnswers the search Published. LopeBase checks until Google lists it.
Watch it land.
Indexing, rankings for the searches you track, and Domain Rating against your competitors, checked every week. You see what moved, not just what is.
Keywords uptime monitoring for side projects8.4Up 3.7 track mrr across stripe accounts12.0Up 2.8 search console for multiple sites6.1Steady
app.lopebase.comStep 1 of 4 Overview $4,210MRR18,420Visitors90Signups Needs you Down for 4 minutes overnightProduct three, back up nowOpen 2 subscriptions past dueProduct two, Stripe SEO On page two uptime monitoring for side projectsPosition 12.1, seen 3,400 timesWrite about this track mrr across stripe accountsPosition 14.8, seen 2,100 timesWrite about this Product one / articles Uptime monitoring for side projects Every link opensLinks to your own postsSounds like your siteAnswers the search Published. LopeBase checks until Google lists it. Keywords uptime monitoring for side projects8.4Up 3.7 track mrr across stripe accounts12.0Up 2.8 search console for multiple sites6.1Steady SEO that does the legwork.
The checks you mean to do every week, done every week, for every product. Most of it is free: it runs on Search Console, Bing, Google's speed data, and Ahrefs' Domain Rating.
Domain RatingYour site against the ones you compete with yourproduct.com34 competitor-a.com41 competitor-b.com22 Up 4 in 4 weeks · Domain Rating by Ahrefs
Tracked searchesPosition week by week, from Search Console uptime monitoring 8.4 mrr across stripe 12.0 multi-site search 6.1 Backfilled from 90 days of history the day you add one
Is Google listing your pages?Every new article checked until it is 32of 40 indexed The 8 that are not, and what to do about each
Page speed for real visitorsGoogle's Core Web Vitals, 25 weeks of trend Loading1.9 sGood Responsiveness140 msGood Visual stability0.18Needs work With Google's good and poor thresholds marked
Who links to youInbound links from Bing, new and lost each week Linking sites flowing into your pages
One-button auditA baseline in a couple of minutes Checked 10 pages, 2 things to fix
Found your blog, 38 posts
Added 3 competitors to track
Reviewed pages to rewrite
Shows its cost in credits before it runs
Tour the full SEO suite · How the content autopilot works
It reads. It does not reach in.
LopeBase is a window onto your tools, not a new place to manage your users. Here is exactly what it can see.
No database access
It never connects to your database. Want your own signup counts too? A small read-only endpoint you host reports them.
Read-only keys
Stripe, PostHog, Search Console, and the rest are read with scoped, read-only keys. Google connects with one click and read-only access.
Encrypted credentials
Each key you add is encrypted on its own. The console only ever shows its last four characters.
Every change on the record
Publishing an article or changing a setting is logged with who, when, and the before and after.
We built LopeBase to run our own products. It is the console we use.
Also in the console
UptimeEvery 15 minutes, a year of history, outages, and a free public status page
AnalyticsPostHog or Google Analytics, every product side by side
RevenueMRR, past due, and payments from Stripe or Polar
Content autopilotArticles in your voice, every link checked
Competitor watchWhat your competitors published this week
Weekly digestThe week across every product, by email
Agent setupLet your coding agent connect things over MCP
ThemesFive palettes, light and dark
See every feature Pay for products, not seats.
Every plan gets the whole console and monthly AI credits. New workspaces start with 14 days of Portfolio, then Free covers one product. Move up when you add more.
Compare plans Monthly Yearly 2 months free Free $0 One product, no time limit. 1 product
1 operator
50 AI credits a month
Start free Studio $29 /month$290 /year About $24 a month, billed yearly A few products and a small team. Up to 3 products
Up to 3 operators
500 AI credits a month
Choose Studio 14-day free trial, no card Portfolio $99 /month$990 /year About $83 a month, billed yearly A real portfolio, run day to day. Up to 10 products
Up to 10 operators
2,000 AI credits a month
Choose Portfolio Agency $299 /month$2,990 /year About $249 a month, billed yearly Client products, each kept separate. Unlimited products
Unlimited operators
8,000 AI credits a month
Choose Agency No card to start. Two months free when you pay yearly. Change plans any time from Billing.
Questions, answered
The short version of what people ask before they connect their first product.
Something else? Contact us.
01What is LopeBase?
An ops console for people running more than one small SaaS product. It reads the tools each product already uses and shows growth, revenue, traffic, uptime, and SEO for every product on one screen, with an SEO toolkit and a content autopilot on top.
02Does LopeBase need access to my database?
No. It reads from services like Stripe, PostHog, and Search Console with read-only keys. If you want your own product's user and signup counts too, a small read-only endpoint you host can report them. LopeBase never connects to your database.
03Which tools can I connect?
Stripe, Polar, PostHog, Google Analytics 4, Plausible, Cloudflare Web Analytics, Google Search Console, Bing Webmaster Tools, Sentry, GitHub, Cloudflare, Supabase, Resend, Sequenzy, Mercury, Brex, Rho, Wise, and the EmDash CMS, plus uptime checks for any address, your own AI provider, and your own app through the LopeBase Adapter. See every connector.
04How is it priced?
By how many products you connect and how many operators you add. Free covers one product and one operator. Studio is $29 a month for up to 3, Portfolio is $99 a month for up to 10, and Agency is $299 a month with no limit. Paying yearly gets two months free. Every plan includes monthly AI credits.
05Can my AI agent set up LopeBase?
Yes. LopeBase has an MCP server. Create an agent token in Settings and your agent can add products and connect their services. How it works.
06Is it a replacement for PostHog or Stripe?
No. Keep them. LopeBase reads from them. You still go to Stripe for Stripe things, just a lot less often.
See every product in one place.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Connect one product for free. Add the rest when you are ready.
Start free, no card needed Sign in

---

## LopeBase Adapter

URL: https://lopebase.com/adapter

A small signed handler in your app. It shares only the records and numbers you declare, runs admin actions with an audit trail, and reports service health.

Your own app, inside LopeBase.
The LopeBase Adapter is one small handler you mount at /api/lopebase. LopeBase signs every request to it, and it answers with only what you declare: your records, your dashboard numbers, your admin actions, and whether each service you depend on is up. Your database never leaves your app.
Start free Read the guide No dependencies. Runs on Cloudflare Workers, Node 18 and up, Vercel, Netlify, Deno, and Convex.
your app/api/lopebaseusersoverviewactionshealth signed, every request LopeBaseYour consoleOverviewAnalyticsUptimeAudit What it adds
The parts of your product no other tool can see.
Stripe knows payments and PostHog knows visits. Only your app knows its own users, plans, and queues. The adapter puts them next to everything else.
d••@acme.comPro, active, joined Sep 12 m••@north.ioTrial, 3 days left j••@kite.devFree, last seen today Your records, searchable
Users, subscriptions, reports, whatever you describe. Search, filter, and saved views work on all of them, and you pick whether emails and names go out in full, masked, or not at all.
Signups, 7 days48Counted in your database Exact dashboard numbers
Users, signups, active users, MRR, and paying customers, counted in your own database and shown on Overview and in the weekly email.
Extend trialUser and days, confirmed, then auditedRun Admin actions with an audit trail
Grant credits, extend a trial, resolve a report. Each action has typed fields, a confirm step, a role check, and a before and after on both sides.
DatabaseUp Job queueUp Every service, watched
List the database, queue, workers, or second API your app needs. LopeBase's uptime checks show each one on its own and alert you when one fails.
Needs attentionFrom your app 14 reports waiting for review
Export queue is behind by 20 minutes
All payouts sent
Warnings from your own app
Your app can report what needs a person, and it shows under Needs attention beside outages and past-due payments, with email or push alerts if you want them.
Service health
One address, every service
Declare what your app cannot work without. Each check uses your app's own credentials for the cheapest authenticated call, like select 1, Stripe balance.retrieve, GitHub GET /app, or your AI provider's GET /models, so it proves your integration works, not just that the vendor is up. Never point a check at a vendor's status page or home address. /api/lopebase/health runs every check in parallel, each with its own time limit. A failing critical service answers 503; mark a service critical: false and its failure shows as degraded instead. cachedCheck keeps a success for 60 seconds and a failure for 10, so polling does not use up your API limits while a recovery still shows up within seconds. Use that address as the product's uptime check. Only names and up or down leave your app.
import { cachedCheck, createAdminAdapter, httpCheck } from "@lopebase/adapter"; export const lopebase = createAdminAdapter({ // ...resources, overview, auth services: [ { id: "db", label: "Database", check: async () =  { await db.execute("select 1"); } }, cachedCheck({ id: "stripe", label: "Payments", check: async () =  { await stripe.balance.retrieve(); } }), cachedCheck({ id: "ai", label: "AI provider", critical: false, check: async () =  { await openai.models.list(); } }), // httpCheck is for hosts your app owns httpCheck("api", "https://api.example.com/health", { label: "Our API" }), ], }); More on how checks run and alert on the Uptime and incidents page.
Pageviews
Pair your signups with where they came from
LopeBase can count your pageviews itself with one tag: pages, sources, and visits, with no cookies and no visitor ids. Next to the signups your adapter reports, the Analytics page shows which pages and sources bring people in. It works with or without the adapter.
script defer src="https://app.lopebase.com/lb.js" data-site="your-site-key"  /script  Copy your tag from the product's Analytics page, or let your agent add it. See Growth analytics.
Set up by your coding agent
Run npx lopebase in the product's folder. It scans the stack, lists what is worth watching, and hands setup to Claude Code, Codex, or the agent you use. The agent asks you before it changes anything.
More on the Agents and MCP page.
What it never does
It lives in your code, so you can read every rule it follows.
Change anything by defaultIt lists and shows what you declare. Updates and actions exist only if you add them.
Send fields you did not declareEvery row is cut down to the fields you list. Anything else your query returns is dropped.
Let secrets slip outA field named like a password, token, API key, or card detail stops the adapter from starting, unless you allow that one field.
Accept unsigned requestsEach request is signed with a secret only your app and LopeBase know. The secret never crosses the wire, and a captured request is useless after five minutes.
Leak errorsErrors are logged in your app. LopeBase only ever sees "adapter error", never a stack trace or a connection string.
Answer without limitsAt most 100 rows per page, and 600 signed requests a minute per running instance by default.
The contract
Every path sits under /api/lopebase. A conformance suite in the package checks your adapter against it in your own tests.
GET /healthOpen, no data. Each declared service's id, label, and up or down. 503 when a critical one is down, 200 and degraded when only non-critical ones are.ok · status · services
GET /overviewSigned. Your dashboard numbers and anything that needs attention.stats · attentionItems
GET /resourcesSigned. The resources and fields you declared.resources · personalData
GET /resources/:nameSigned. A page of rows, with search, sort, filters, and a cursor.rows · nextCursor
POST /actions/:nameSigned. Only if you add actions. Typed params in, a summary and an audit row out.ok · summary · audit
GET /auditSigned. The adapter's own record of every change made through it.actor · action · before · after
Adapter questions
Something else? Contact us.
01Does LopeBase need my database credentials?
No. It only talks to the adapter, which decides what to expose. LopeBase never connects to your database.
02Do I need the adapter to use LopeBase?
No. Analytics, search, revenue, errors, and uptime all connect without touching your code. Add the adapter when you want your own users, numbers, actions, or service health next to them.
03What frameworks does it support?
It uses only Web Crypto and has no dependencies, so it runs on Cloudflare Workers, Node 18 and up, Vercel, Netlify, Deno, and Convex. The guide has Next.js, Hono, and Convex examples.
04Can secrets or personal data leak through it?
Only fields you declare leave your app. A field named like a password, token, or API key stops the adapter from starting unless you allow that one field, and you choose whether emails and names go out in full, masked, or not at all.
05Is the health endpoint public?
Yes, so the uptime check can read it without a secret. It shows only each service's name and whether it is up. Error messages stay in your logs.
06Does the adapter count pageviews?
No. Pageviews come from a separate one-line tag that LopeBase serves. The adapter reports signups from your database, and the two together show which pages bring signups.
What an admin audit trail should record The fields every admin action should record, and why the before and after matters most.vs Forest Admin An admin panel on your database, compared with a console that reads your tools.All connectors The tools LopeBase reads beside your own app, all with read-only keys. What do you want to get done?
The adapter feeds every one of these.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 06 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Put your own product next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free Read the guide

---

## Agents and MCP

URL: https://lopebase.com/agents

Run npx lopebase in your project and your coding agent sets up LopeBase over MCP: it adds products, connects sources, and wires up your app's adapter.

Let your coding agent set it up.
Run npx lopebase in a product's folder. It reads your stack, connects your agent to LopeBase's MCP server, and your agent adds the product, connects its sources, and wires up your app's admin adapter while you keep coding.
Start free Every change an agent makes is in the audit log, under the person who created its token.
Connect an agent
Using Claude? LopeBase is listed in Claude's connector directory.
Find LopeBase in the Claude directory
Otherwise, run the command below.
$ npx lopebase 01Run it in your product's folder. It reads dependency and config file names, after you say yes. Never your .env file or your code.
02Connect this computer. Sign in, or create a free account if you are new, check that the code matches your terminal, and press Connect.
03Pick your agent. It finds Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent, adds the LopeBase tools, and starts it with what the scan found.
Works on macOS, Linux, and Windows with Node 18 or later. Rather wire it up by hand? Add the MCP settings below.
The MCP settings
{ "mcpServers": { "lopebase": { "url": "https://app.lopebase.com/api/mcp", "headers": { "Authorization": "Bearer lb_agent_..." } } } } What an agent can do
list_products, get_productSee your products and what each one has connected.
add_productAdd a product by name and address.
connect_sourceConnect PostHog, Stripe, Sentry, Search Console, GA4, or Bing to a product, checked before it is saved.
connect_adapterConnect the LopeBase Adapter in your app once the agent has added it, including the services uptime should watch.
get_onboarding_statusWhat to set up next for a product, including which services are worth an uptime check, read from your code.
get_pageview_snippet, get_pageviewsTurn on LopeBase's own cookieless pageview counter, with your yes, and confirm hits are arriving.
get_content_profile, next_article_topic, submit_draftWrite articles for the content autopilot. Drafts go through the same checks and review.
get_health, get_digestWhat needs attention across every product, and this week against last.
list_metrics, query_metricHeadline numbers like pageviews and signups, the same ones the console shows.
list_sources, read_sourceRows from Search Console, Bing, GA4, Plausible, PostHog, and Cloudflare Web Analytics: queries, pages, channels, funnels, and more.
Read your search and analytics data
Once a source is connected, your agent can read it for every product. Ask where you are close to page one, which channel converts, or what caused a spike.
Search ConsoleQueries, pages, positions Google Analytics 4Channels and conversions Bing WebmasterQueries and inbound links PostHogRetention and funnels PlausibleGoals and entry pages Cloudflare Web AnalyticsVisits and referrers Working across all of them? See one MCP server for all your SEO data.
Limits
Scoped to one workspaceA token only works in the workspace that made it.
Aggregates, not peopleread_source returns search and analytics totals. Customer, billing, and email records are not offered to agents.
Write only for secretsKeys go in, never out.
Your plan's limits applyAn agent cannot add products past what your plan allows.
On the recordEach change is in the audit log, under the person who created the token.
Questions
Something else? Contact us.
01Do I need an account first?
No. When you run npx lopebase, the browser step lets you sign in or create a free account, then you confirm the code from your terminal.
02Which agents work with it?
npx lopebase finds Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent. By hand, any agent or editor that can use a remote MCP server over HTTP works.
03Can an agent see my secrets?
No. An agent can save a key you give it, but it can never read one back. Saved keys are encrypted, and the console only ever shows their last four characters.
04How do I stop an agent?
Revoke its token in Settings. It stops working on the next request.
05Is agent access included in every plan?
Yes. Agent tokens work on every plan, including Free.
Content autopilot A blog for every product, reviewed or on autopilot.LopeBase Adapter What the agent wires into your app. What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Hand the setup to your agent.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Bing Webmaster MCP

URL: https://lopebase.com/agents/bing-webmaster-mcp

Give your AI agent Bing Webmaster data over MCP: search queries, daily clicks, and inbound links for every site, next to your Google numbers.

Agents and MCP Bing search data, for your agent too.
Bing's index also feeds other search engines and assistants, and it is easy to forget to check. Connect Bing Webmaster Tools to LopeBase and your agent can read your Bing queries, daily traffic, and the pages that link to you.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
Sign in with Bing and approve read access. LopeBase never submits URLs or changes a setting.
Ask about the search engine nobody checks
Bing numbers use the same fields as Search Console, so your agent can put them side by side.
Inbound links, with anchor text
backlinks lists pages linking to your most linked pages, with the anchor each one uses.
Bing's own queries
top_queries shows what people search on Bing to find you, which often differs from Google.
Daily clicks and impressions
daily_traffic gives the trend, so you can see whether Bing is growing or fading.
What your agent can read
Four datasets per verified site, read live from Bing Webmaster Tools.
search_performanceClicks, impressions, and click-through rate over the last 30 days.clicks · impressions · ctr
top_queriesThe top 25 searches that bring people from Bing.query · clicks · impressions · position
daily_trafficClicks and impressions per day.day · clicks · impressions
backlinksPages linking to your 8 most linked pages, with anchor text and link counts.source · target · anchor · target_links
Workflows worth stealing
Bing is small enough to ignore and big enough to matter. These asks make it cheap to keep an eye on.
Find the Google and Bing gap
Which searches bring clicks on Google but not on Bing, and the other way round?
With Search Console connected too, your agent compares the two lists.
top_queriessearch_queriesAudit your links
List the sites linking to us and group them by the page they link to.
Shows which pages earn links and which need outreach.
backlinksCheck anchor text
Are most links to our homepage using our brand name, or something descriptive?
Anchor text tells search engines what a page is about.
backlinksWatch Bing week to week
Did Bing clicks drop this week? From which day?
A quiet drop on Bing is easy to miss without a check.
daily_trafficsearch_performance Set it up in a few minutes
01Connect Bing. Start free, click Connect Bing, and approve read access on Bing's own page. Each product is matched to its verified site.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Sites must be verified in Bing Webmaster Tools first. Bing can import them from Search Console.
Good to know
Bing's link index is smallerBing finds fewer links than some paid tools, and may show none for a new site.
Top 25 queriesBing returns its top searches for a site, not every search.
Read onlyLopeBase never submits URLs, changes settings, or touches your sitemaps.
One token, one workspaceAn agent's token reads only the workspace that issued it, and stops as soon as you revoke it.
Bing Webmaster MCP questions
Something else? Contact us.
01Why not just paste a Bing API key?
A Bing API key can also submit and change things. Signing in with Bing lets LopeBase ask for read access only.
02Does Bing data matter if most of my traffic is Google?
Bing results also power other search engines and assistants, and its queries often show different wording. It is cheap to check once your agent can read it.
03Can my agent see backlinks from Google?
Google does not offer a links API, so backlinks come from Bing. Search Console's own links report stays in Search Console.
04Which agents work with it?
Any agent that can use the LopeBase MCP server, through npx lopebase or a remote MCP connection with sign-in.
The Bing connector Connect Bing in one click and see its numbers in the console too.Search Console Queries, pages, and positions for your agent.Google Analytics 4 Channels, landing pages, and conversions.Cloudflare Web Analytics Cookieless pageviews, visits, and referrers. Stop ignoring Bing. Let your agent check it.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## Cloudflare Analytics MCP

URL: https://lopebase.com/agents/cloudflare-web-analytics-mcp

Connect Cloudflare Web Analytics to your AI agent over MCP. Read cookieless pageviews, visits, top pages, and referrers for every site you run.

Agents and MCP Cookieless traffic, readable by your agent.
Cloudflare Web Analytics is free and private, and its numbers usually stay in the dashboard. Connect it to LopeBase and your agent can read pageviews, visits, top pages, and referrers for each site, without a cookie banner anywhere.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
Connect Cloudflare in one click, read-only. A read-only API token works too.
Ask your free analytics real questions
Your agent reads the same numbers the Cloudflare dashboard shows, shaped into tables it can compare across sites.
No cookies, no banner
Cloudflare counts visits without cookies. LopeBase reads those counts; it adds no tracking of its own.
Referrers included
traffic_sources lists the sites that send visits over the last 28 days.
Every site, side by side
Each site is its own connection, so an agent can rank all your products by traffic in one ask.
What your agent can read
Four datasets per site. Cloudflare counts visits, not unique people, so these report visits.
web_analyticsPageviews and visits for the last 7 and 28 days.pageviews_7d · pageviews_28d · visits_7d · visits_28d
daily_pageviewsPageviews and visits per day.day · pageviews · visits
top_pathsThe most viewed pages.url · views · visits
traffic_sourcesVisits per referring site over 28 days.source · sessions
Workflows worth stealing
Small, useful checks that free analytics rarely gets.
Explain a spike
What caused the traffic spike this week, and which page did people land on?
The daily trend gives the date; referrers give the cause.
daily_pageviewstraffic_sourcesRank your sites
Rank all my sites by visits this week and last week.
One ask across every Cloudflare site you connected.
web_analyticsFind pages worth updating
Which pages get steady views but have not changed in a year?
Your agent checks the page's history in your repo.
top_pathsTell launch traffic from search
After launch day, how much traffic still comes from search?
Shows whether a launch turned into lasting visitors.
traffic_sourcesdaily_pageviews Set it up in a few minutes
01Connect Cloudflare. Start free, press Connect Cloudflare, and approve read access to your analytics. Each site is matched by domain.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Web Analytics must be turned on for the site in Cloudflare. It works whether or not the site is proxied through Cloudflare.
Good to know
Visits, not peopleCloudflare does not count unique visitors, so weekly active users are not offered for these sites.
No goals or funnelsCloudflare Web Analytics does not record events, so conversions are not available. Pair it with PostHog or GA4 if you need them.
Read onlyLopeBase never changes anything in your Cloudflare account.
One token, one workspaceAn agent's token only reads the workspace that issued it.
Cloudflare Web Analytics MCP questions
Something else? Contact us.
01Is this the same as Cloudflare's own MCP servers?
No. Cloudflare publishes its own MCP servers for working in your Cloudflare account. LopeBase puts Web Analytics next to your other products and sources, in one set of tools.
02Does it work for sites not proxied through Cloudflare?
Yes, as long as the Web Analytics beacon is on the site.
03Why are weekly active users missing?
Cloudflare counts visits, not people. LopeBase reports what Cloudflare measures and leaves out what it does not.
04Can my agent read Workers or D1 too?
The Cloudflare connector shows Workers, deploys, and D1 in the console. Agents read the analytics datasets.
The Web Analytics connector Connect Cloudflare and see visits and top pages in the console too.Search Console Queries, pages, and positions for your agent.Google Analytics 4 Channels, landing pages, and conversions.Bing Webmaster Bing queries, traffic, and inbound links. Make your free analytics answer questions.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## Google Analytics MCP

URL: https://lopebase.com/agents/google-analytics-mcp

Connect GA4 to Claude, Codex, or Cursor over MCP. Your agent reads channels, landing pages, devices, and conversions for every property you run.

Agents and MCP GA4 answers, without the GA4 maze.
Connect your Google Analytics 4 properties to LopeBase, and your agent can read traffic, channels, landing pages, devices, and goal conversions for each one. Ask which channel converts, which landing page leaks, and what changed this week, in plain words.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
Connect with Google in one click, read-only. Every property you run, from one sign-in.
Ask about outcomes, not reports
Your agent reads the same numbers the GA4 Data API returns, already shaped into small tables it can reason about.
Conversions by channel, page, and device
Pass any event as the goal and traffic_sources, landing_pages, and devices count who converted, not just who visited.
Find your goal events first
goal_events lists the events that could count as a conversion, with people in the last 28 days, the 28 before, and the last 7.
Every property in one place
Each GA4 property is its own connection, so an agent can compare products without switching accounts.
What your agent can read
Seven datasets per property. Breakdowns cover the last 28 days; the trend covers up to 90.
web_analyticsPageviews for 7 and 28 days, plus weekly and monthly active users.pageviews_7d · pageviews_28d · wau · mau
daily_pageviewsPageviews and visitors per day.day · pageviews · visitors
top_pathsThe most viewed pages over the last 7 days.url · views · visitors
goal_eventsEvents that may count as a conversion, with people now and before.event · people_28d · people_prev_28d · people_7d
traffic_sourcesVisitors and sessions per default channel group. Add { goal } to count conversions.source · visitors · sessions · converters
landing_pagesVisitors per landing page with bounce rate. Add { goal } for conversions.path · visitors · converters · bounce_rate
devicesVisitors per device category. Add { goal } for conversions.device · visitors · converters
Workflows worth stealing
Questions that take a dozen clicks in GA4 take one sentence here.
Find the leaky landing page
Which landing pages get over 500 visitors but bounce above 70%? Suggest one fix for each.
Your agent can open the page in your repo and look for the cause.
landing_pagesJudge a channel by signups
Rank channels by conversion rate to sign_up, not by visitors.
The goal filter turns a traffic report into an outcome report.
traffic_sourcesgoal_eventsCheck mobile before a launch
Do mobile visitors convert worse than desktop? By how much?
A gap here usually means a form or layout problem on small screens.
devicesWrite the weekly traffic note
Summarize this week's traffic for every product in five lines.
query_metric and get_digest give the headline numbers; read_source adds the why.
web_analyticsget_digestNotice a goal that stopped firing
Did any goal event drop by more than half compared with the 28 days before?
A sudden drop is often a broken tag, not a bad week.
goal_eventsPair search with sessions
For our top Search Console pages, how do those visitors behave once they land?
With Search Console connected too, your agent can join the two by page.
top_pageslanding_pages Set it up in a few minutes
01Connect GA4. Start free, press Connect with Google, and pick the GA4 property for each product.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Using PostHog or Plausible as well? Connect both; each shows up as its own connection.
Good to know
Fixed windowsBreakdowns cover the last 28 days, and top pages the last 7. Custom date ranges are not offered yet.
Goals use your event namesPass the event exactly as GA4 records it, like sign_up or purchase. goal_events lists what is there.
Read onlyLopeBase never changes GA4 settings, audiences, or tags.
No visitor level dataAgents get counts and rates, never individual visitors or their details.
Google Analytics MCP questions
Something else? Contact us.
01Do I need a Google Cloud project to use the GA4 Data API?
No. Connect with Google handles access. You pick the properties; LopeBase calls the Data API for you when your agent asks.
02Can I use Universal Analytics?
No. Google shut down Universal Analytics; LopeBase reads GA4 properties.
03Will the numbers match the GA4 interface?
They come from the same Data API. Small differences can come from GA4's own thresholds and sampling, the same as in Explorations.
04Can my agent compare several products?
Yes. Every GA4 property you connect is a separate connection. Ask about all of them at once.
05Does it work with Claude in the browser?
Yes, if your plan lets you add custom connectors. Add https://app.lopebase.com/api/mcp and sign in.
The GA4 connector Connect with Google and see each property in the console too.Search Console Queries, pages, and positions for your agent.Bing Webmaster Bing queries, traffic, and inbound links.Cloudflare Web Analytics Cookieless pageviews, visits, and referrers. Let your agent read GA4 for you.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## Plausible MCP

URL: https://lopebase.com/agents/plausible-mcp

Connect Plausible to Claude, Codex, or Cursor over MCP. Your agent reads goals, channels, entry pages, and devices for every site, self-hosted too.

Agents and MCP Plausible, with an agent on top.
You picked Plausible for simple, private numbers. Connect it to LopeBase and your agent can read them too: visitors, goals, channels, entry pages, and devices for each site, including self-hosted Plausible.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
A Plausible Stats API key, which can only read. Cloud and self-hosted both work.
Ask, then act in the same session
Your agent reads the numbers and can fix what it finds in your code before you switch windows.
Your goals, as conversions
Pass a goal name and the breakdowns count who converted, not just who came.
Channels and entry pages
traffic_sources and landing_pages cover the last 28 days, with bounce rate per page.
Privacy stays intact
Plausible collects no personal data, and agents only ever see counts.
What your agent can read
Seven datasets per site, from Plausible's Stats API.
web_analyticsPageviews for 7 and 28 days, plus weekly and monthly visitors.pageviews_7d · pageviews_28d · wau · mau
daily_pageviewsPageviews and visitors per day.day · pageviews · visitors
top_pathsThe most viewed pages.url · views · visitors
goal_eventsYour goals, with people in the last 28 days, the 28 before, and the last 7.event · people_28d · people_prev_28d · people_7d
traffic_sourcesVisitors per channel. Add { goal } for conversions.source · visitors · converters
landing_pagesVisitors per entry page with bounce rate. Add { goal } for conversions.path · visitors · converters · bounce_rate
devicesVisitors per device. Add { goal } for conversions.device · visitors · converters
Workflows worth stealing
Plausible keeps the dashboard simple. These asks go one step further.
Find posts that never convert
Which entry pages get over 1,000 visitors and under 1% goal conversion?
Good candidates for a clearer next step.
landing_pagesgoal_eventsCompare goals month over month
Which goals grew and which shrank compared with the previous 28 days?
goal_events carries both windows, so no second query.
goal_eventsWeigh your channels
Rank channels by conversions to Signup, not visitors.
A small channel that converts well is worth more than it looks.
traffic_sourcesCheck mobile
Do mobile visitors reach our goals as often as desktop?
A gap usually points at a layout or form problem.
devices Set it up in a few minutes
01Connect Plausible. In Plausible, create a Stats API key. Paste it into LopeBase and pick each product's site. Self-hosted? Add your Plausible address too.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Your agent can also connect Plausible for you if you give it the key: connect_source tests it before saving.
Good to know
Fixed windowsBreakdowns cover the last 28 days. Custom ranges are not offered yet.
Goals must exist in PlausibleConversions use goals you set up in Plausible. goal_events lists them.
Read onlyA Stats API key cannot change anything, and LopeBase does not ask for more.
One token, one workspaceAn agent's token only reads the workspace that issued it.
Plausible MCP questions
Something else? Contact us.
01Does it work with self-hosted Plausible?
Yes. Add your Plausible address when you connect, along with a Stats API key from that instance.
02Which API key do I need?
A Stats API key, from Account settings, API keys. It can only read stats.
03Can my agent see individual visitors?
No. Plausible does not record them, and LopeBase passes only counts and rates.
04Can I connect several Plausible sites?
Yes. Each site is its own connection, and your agent can ask about all of them at once.
The Plausible connector Add a Stats API key and see each site in the console too.Search Console Queries, pages, and positions for your agent.Google Analytics 4 Channels, landing pages, and conversions.Bing Webmaster Bing queries, traffic, and inbound links. Give your agent your Plausible numbers.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## PostHog MCP

URL: https://lopebase.com/agents/posthog-mcp

Read PostHog retention, funnels, goal events, and traffic from your AI agent over MCP, for every project, next to your Search Console data.

Agents and MCP PostHog for every project, next to your search data.
PostHog has its own MCP server for working inside one project. LopeBase answers a different question: how are all my products doing, and why. Connect each PostHog project once, and your agent can read retention, funnels, goal events, and traffic beside Search Console, GA4, and the rest.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
A personal API key with read access. Pick which projects LopeBase reads.
Ask across projects and tools
LopeBase runs one read-only query per dataset in PostHog and hands your agent a small table.
Funnels from event names
Pass 2 to 6 events in order and get how many people reached each step in the last 28 days.
Weekly retention
New people per week and how many came back in weeks 1, 2, and 4.
Many projects, one agent
Each PostHog project is its own connection, alongside your other tools.
What your agent can read
Nine datasets per project. Agents never get person profiles or raw events.
web_analyticsPageviews for 7 and 28 days, weekly and monthly active users.pageviews_7d · pageviews_28d · wau · mau
daily_pageviewsPageviews and visitors per day.day · pageviews · visitors
top_pathsThe most viewed pages.url · views · visitors
goal_eventsEvents that may count as a conversion, now and in the 28 days before.event · people_28d · people_prev_28d · people_7d · with_visit
traffic_sourcesVisitors per channel. Add { goal } for conversions.source · visitors · sessions · converters
landing_pagesVisitors per entry page with bounce rate. Add { goal } for conversions.path · visitors · converters · bounce_rate
devicesVisitors per device. Add { goal } for conversions.device · visitors · converters
retentionWeekly cohorts of new people and how many came back.cohort · new_people · week1 · week2 · week4
funnelPeople at each step of an ordered funnel. Pass { steps: [...] }.step · event · people
Workflows worth stealing
The cross-project and cross-tool questions are where this earns its place.
Find where the funnel breaks
Build the funnel pageview, signup_started, signup_completed, first_invoice and tell me the worst step.
The agent picks the step and can open the code behind it.
funnelgoal_eventsCompare retention across products
Which of my products keeps new people best at week 4?
One ask across every PostHog project you connected.
retentionTie search to activation
Do visitors from organic search activate as well as direct visitors?
Pass your activation event as the goal.
traffic_sourcesCatch a broken event
Did any goal event fall to near zero in the last 7 days?
Usually a renamed or removed capture call.
goal_events Set it up in a few minutes
01Connect PostHog. Create a personal API key in PostHog with read access, paste it into LopeBase, and choose which projects to read.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
US and EU cloud and your own PostHog host all work.
Good to know
Fixed windowsBreakdowns and funnels cover the last 28 days.
No raw events or peopleAgents get aggregates only. Session replays and person profiles stay in PostHog.
Use both if you likePostHog's own MCP server suits working inside one project, like editing flags. LopeBase is for reading across projects and tools.
One token, one workspaceAn agent's token only reads the workspace that issued it.
PostHog MCP questions
Something else? Contact us.
01Should I use this or PostHog's own MCP server?
Use PostHog's for deep work in one project, like feature flags. Use LopeBase when you want every project together with Search Console, GA4, Stripe, and uptime. They work side by side.
02What key does LopeBase need?
A personal API key with read access to the projects you choose.
03Can my agent run any HogQL query?
No. LopeBase runs its own fixed read-only queries and returns the results. Event names you pass are checked before they reach a query.
04Does it work with EU cloud or self-hosted PostHog?
Yes. Choose your host when you connect.
The PostHog connector Add a read key and see each project in the console too.Search Console Queries, pages, and positions for your agent.Google Analytics 4 Channels, landing pages, and conversions.Bing Webmaster Bing queries, traffic, and inbound links. Read every PostHog project from your agent.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## Search Console MCP

URL: https://lopebase.com/agents/search-console-mcp

Give Claude, Codex, or Cursor your Search Console data over MCP: every query, page, and position for each site, so your agent can find SEO wins.

Agents and MCP Search Console, inside your agent.
Connect Google Search Console to LopeBase once, and any agent that speaks MCP can read your queries, pages, clicks, and positions for every site you run. Ask in plain words where you are close to page one, which titles lose clicks, and what to write next.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
Connect with Google in one click. LopeBase only asks Google for read access, and agents only get read access from LopeBase.
Ask it like you would ask a person
Your agent picks the dataset, reads the rows, and works out the answer. No exports, no spreadsheets, no copying numbers between windows.
Every query, not just the top ten
search_queries returns up to a thousand queries from the last 28 days, with impressions, clicks, CTR, and average position for each.
Page and query together
page_queries shows which searches each page appears for, so an agent can tell when two pages compete for the same search.
Daily history for what you track
queries_daily gives 90 days of daily numbers for the searches you name, so a drop has a date.
What your agent can read
Seven datasets per site, read live from Search Console when the agent asks. Domain and URL prefix properties both work.
search_performanceThe site's last 7 days in one row: clicks, impressions, click-through rate, and average position.clicks · impressions · ctr · position
top_queriesThe top searches from the last 7 days, for a quick look at what is bringing people in right now.query · clicks · impressions · ctr · position
search_queriesEvery search over 28 days, up to 1,000 rows. The one to use for finding wins.query · clicks · impressions · ctr · position
top_pagesEach page's clicks and position over 28 days, up to 1,000 pages.page · clicks · impressions · ctr · position
page_queriesWhich searches each page shows up for over 28 days, up to 1,000 pairs.page · query · clicks · impressions · position
daily_searchOne row per day for the last 28 days, for the trend.day · clicks · impressions · position
queries_daily90 days of daily numbers for searches you name. Pass them as filters: { queries: [...] }.query · day · clicks · impressions · position
Workflows worth stealing
Each one is a single ask. Paste it into your agent as written, or change the numbers to suit your site.
Find striking distance searches
List searches where we average position 8 to 20 with at least 200 impressions, biggest first.
The searches where one better page pays off fastest.
search_queriesFix titles that lose the click
Which pages rank in the top 5 but get under 2% CTR? Draft a better title and description for each.
A page can rank well and still be skipped. Your agent reads the page in your repo and rewrites the snippet.
top_pagespage_queriesSpot pages competing with each other
Find searches where two or more of our pages both show up, and tell me which one to keep.
Two pages splitting one search often both rank worse than one page would.
page_queriesDate a drop
Clicks fell this month. Which searches lost the most, and on what day did it start?
Read the trend, then the daily history for the searches that moved.
daily_searchqueries_dailyPlan the next article
Pick the next article topic for acme and write it in our voice.
next_article_topic starts from Search Console quick wins and skips what you already wrote. submit_draft sends the article to your review queue.
next_article_topicsubmit_draftCheck every site at once
Compare this week's clicks for all my sites and flag any that dropped.
Each site is its own connection, so one ask covers them all.
search_performance Set it up in a few minutes
01Connect Search Console. Start free, press Connect with Google, and pick the property for each product.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
An agent can also connect Search Console for you: connect_source checks the connection before it saves it.
Good to know
Search Console lags about two daysGoogle publishes search data with a delay, so the last day or two are often missing. That is the same in Search Console itself.
Up to 1,000 rows per askLarge sites get the top 1,000 queries or pages by clicks. Ask for a narrower list with queries_daily when you need one search exactly.
Nothing gets changedLopeBase never submits sitemaps, requests indexing, or changes settings. Agents read; they cannot write to Search Console.
One token, one workspaceAn agent's token only reads the workspace that issued it. Revoke it in Settings and it stops on the next request.
Search Console MCP questions
Something else? Contact us.
01Do I need to set up a Google Cloud project or service account?
No. Connect with Google signs you in and asks for read access to Search Console. A service account still works if you prefer one.
02Which agents can use it?
Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent through npx lopebase, and any chat app or editor that can add a remote MCP server with sign-in, such as Claude.
03Can my agent see more than one site?
Yes. Each Search Console property you connect is its own connection, and list_sources shows them all, so one question can cover every site.
04Does the agent see my Google password or token?
No. Your Google connection stays encrypted in LopeBase. The agent gets rows of search data and never the key that fetched them.
05How is this different from exporting to a spreadsheet?
The agent reads current numbers when you ask, picks the right cut of the data, and can act on it in the same session, like rewriting a title in your code.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.The Search Console connector Connect with Google and see every site on the SEO screen too.Google Analytics 4 Channels, landing pages, and conversions.Bing Webmaster Bing queries, traffic, and inbound links.Cloudflare Web Analytics Cookieless pageviews, visits, and referrers. Give your agent your search data.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## SEO MCP server

URL: https://lopebase.com/agents/seo-mcp

One MCP server for your agent's SEO work: Search Console, Bing, GA4, Plausible, PostHog, and Cloudflare, for every site you run, in one set of tools.

Agents and MCP One MCP server for all your SEO data.
An MCP server for one API covers one tool. LopeBase connects Search Console, Bing, and your analytics tool for every product you run, then gives your agent two tools to read all of it. The interesting questions sit between the tools: which rankings bring buyers, and which only bring visitors.
Start free How to connect $ npx lopebase Or run this in your project folder. It signs you in and connects Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
Free for one product. Read-only connections, read-only agent access.
Questions one tool cannot answer
Your agent reads Search Console and your analytics side by side and joins them by page.
Every source, same shape
Search Console and Bing share field names, and so do GA4, Plausible, and PostHog, so your agent compares them without translating.
Every site, one connection list
list_sources shows every connected site and dataset in your workspace.
From finding to fixing
next_article_topic and submit_draft turn search gaps into drafts in your review queue.
What your agent gets
Two read tools cover every source. The rest are there when your agent needs them.
list_sourcesEvery connected search and analytics source, with its datasets and fields.
read_sourceRows from one dataset, with optional filters like a goal event or a list of searches.
query_metricA single headline number, the same one the console shows, like pageviews_7d.
get_digestThis week against last week for every product, plus what needs attention.
next_article_topicThe best unused topic from Search Console quick wins and your keywords.
submit_draftAn article from your agent, through the same checks, into your review queue.
Workflows across tools
Each of these needs at least two sources. That is the point.
Rank pages by business value
Join Search Console clicks with GA4 conversions by page and rank pages by signups per click.
Puts content work where it pays.
top_pageslanding_pagesFind Google and Bing differences
Which searches do well on Google and badly on Bing?
Often a title or a missing Bing verification.
search_queriestop_queriesCheck that search clicks arrive
Do Search Console clicks roughly match organic sessions in analytics this month?
A big gap can mean a tag missing from some pages.
search_performancetraffic_sourcesRun a portfolio SEO review
For each of my sites, give me one search to target and one page to fix this week.
Every site you run, in one pass.
search_queriestop_pagesWrite what search is asking for
Find a search we show up for but have no page about, then write that page in our voice.
From the gap to a reviewed draft in one session.
page_queriesnext_article_topicsubmit_draftMeasure a rewrite
We rewrote the invoice template post on the 1st. How have its searches moved since?
Daily history for the searches that page targets.
queries_daily Set it up in a few minutes
01Connect your sources. Start free, add a product, and connect Search Console, Bing, and your analytics tool. Google, Bing, and Cloudflare connect in one click.
02In a terminal agent, run npx lopebase in a project folder. It signs you in and adds LopeBase to Claude Code, Codex, Gemini CLI, opencode, or Cursor Agent.
03In a chat app or editor, add the remote MCP server https://app.lopebase.com/api/mcp and sign in when it asks. Any client that supports remote MCP servers with sign-in works.
Prefer to stay in the terminal? npx lopebase lets your agent do the connecting, and it asks you only for what needs a person.
Good to know
Read only, both waysEvery connection only reads your tools. Nothing an agent does through LopeBase changes Search Console, Bing, or your analytics.
Aggregates onlyAgents get counts, rates, and positions. No visitor or customer records reach an agent through these tools.
Each tool's own limits applySearch Console lags about two days; Bing's link index is smaller; Cloudflare counts visits, not people.
On the recordAnything an agent changes, like connecting a source, is in the audit log under the person who issued its token.
SEO MCP questions
Something else? Contact us.
01Why not run a separate MCP server for each tool?
You can. But each one needs its own keys, runs on your machine, and returns its own shapes. LopeBase connects each tool once, works for every site, and gives your agent one way to read all of them.
02Which agents does it work with?
Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent through npx lopebase, and any client that can add a remote MCP server with sign-in.
03Does it work for agencies with client sites?
Yes. Each client site is a product with its own sources. Plans scale by how many products you run.
04What does it cost?
Free for one product, with agent access included. Paid plans add products; see pricing.
05Can my agent publish changes to my site?
Only through your review queue. Articles from submit_draft go through the same checks as LopeBase's own and wait for approval unless you turn on Autopilot.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Every connector Search, analytics, revenue, errors, uptime, and more, each read-only.Pricing Free for one product. Agent access on every plan.Search Console Queries, pages, and positions for your agent.Google Analytics 4 Channels, landing pages, and conversions. Give your agent every number it needs for SEO.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card. Agent access is on every plan.
Start free Agents and MCP

---

## AI reviews

URL: https://lopebase.com/ai-reviews

A weekly briefing and reviews of revenue, traffic, and outages, written from your own numbers. Each one says what changed and what to do next.

Your numbers, read for you.
One button on the page you already use. LopeBase reads that page's numbers from your connected tools and tells you what changed, what is at risk, and what to do next. In plain words, with the numbers behind it.
Start free See the reviews Works with the tools you connect: Stripe or Polar, PostHog, Google Analytics, Plausible, Search Console, Sentry, and uptime checks.
The reviews
Six reviews, each where you already look.
Each one opens with the one thing that matters most, then what stands out, marked going well, worth watching, or act now, then numbered next steps.
Weekly briefingOverview, every product Signups on Product one up on last week
Product two traffic down after a quiet week of posts
Product three was down for 40 minutes on Tuesday
A weekly briefing
Every product's numbers against last week, what needs attention, uptime, and what your team did, read into what changed and what to do this week.
Revenue at risk$1803 past due, 2 cancelling Revenue review
MRR, cancellations, past-due subscriptions, and failed payments, and what to do about each.
This week vs last Traffic review
What is driving visits, what is slipping, and which pages to work on, from analytics, search clicks, and signups.
Conversion and retentionAnalytics Onboarding is sent under a different identity than the visit
Most people who land on one blog post leave after that page
Tracking: signup rate since the pricing page change
Conversion and retention review
Lines up every source you connected: where visitors come from, which pages they land on, how many sign up or buy, how many come back, and where tracking breaks. Each finding shows the numbers behind it, and you can track a step to see whether its number moved.
Sources readUnder every review Stripe
PostHog
Search Console
Shows its sources
Every review lists what it read and which model wrote it, so you can check the numbers before you act.
Product twoUp Status page noteDrafted from the outage, ready to postPost Incident review
Thirty days of uptime checks and each outage, with your top errors from Sentry when it is connected. It says what went wrong and what to fix first. After downtime, it drafts a calm note for your customers that you can post to your status page in one click.
Your own AI keyAny OpenAI-compatible key, under ConnectionsAdd Bring your own key
Reviews use LopeBase's own AI access by default. Add your own key and every review uses it instead.
XDocs drift because nobody owns the update. Three habits that keep them true. LinkedInEvery team says their docs are out of date. Here is what fixed ours. NewsletterThis week: how to review docs in the same pull request as the code. Community postA short guide to keeping docs in sync with code, with the part that helped most. Share an article
From any article, a post for X, one for LinkedIn, a newsletter blurb, and a community post, in your product's voice, each with its character count and a copy button. Works with articles from the content autopilot.
How a review works
No prompts to write and nothing to set up beyond the tools you have already connected.
01Open the page. Overview, Revenue, Analytics, Uptime, or an article. Pick one product or all of them.
02Run it. You see each step as it reads your numbers and writes.
03Read it. A headline, what stands out, and next steps, with the sources it read listed underneath.
04Come back to it. The latest review stays on the page for your whole team until someone runs it again.
What it will not do
A review is only useful if you can trust it, so each one works inside the same rules.
Make up numbersIt is given your numbers and told to use only those. When the data is thin, it says so.
Send your customers' detailsThe revenue review reads totals and payment results. Customer names and emails never leave LopeBase.
Mix things that do not add upAmounts in different currencies are never added together, and neither are visits from two different analytics tools.
Post anything for youStatus notes and social posts are drafts to read and copy. Nothing is published on your behalf.
Run without youOnly an admin can run a review. Everyone else on the team can read the latest one.
Hide its sourcesEvery review lists what it read and which model wrote it.
Questions
How the AI reviews behave, in plain terms.
Something else? Contact us.
01Which tools does each review read?
The weekly briefing reads every product's app numbers, analytics, uptime, and what needs attention. The revenue review reads Stripe or Polar, plus MRR your own app reports. The traffic review reads PostHog, Google Analytics, Plausible, or Cloudflare Web Analytics, with Search Console or Bing and your app's signups. The conversion and retention review reads the same analytics tools' sources, landing pages, goals, funnels, and retention, with Search Console, Stripe or Polar, your app's own numbers, and Sequenzy. The incident review reads your uptime checks and Sentry.
02Can I review one product instead of all of them?
Yes. The revenue, traffic, conversion and retention, and incident reviews follow the product picker on their page, so you can review one product or every product at once. The weekly briefing always covers the whole workspace.
03Does it run on its own?
No. A review runs when an admin presses the button, and the latest one stays on the page until it is run again. For a scheduled summary, the weekly digest email arrives on the day and hour you pick.
04Which AI model writes the reviews?
By default, LopeBase's own AI access. You can add your own OpenAI-compatible key under Connections instead, and every review uses it. Each review names the model that wrote it.
05Can it be wrong?
Yes, so it shows its work. It is told to use only the numbers it is given and to say when the data is thin, and it lists every source it read. Check the numbers on the same page before you act on a review.
06Are the social posts published for me?
No. Share an article writes four drafts to read, edit, and copy. LopeBase does not post to X, LinkedIn, or anywhere else.
All features Dashboards, SEO checks, uptime, revenue, and the weekly digest.Connectors The tools a review can read from, all with read-only keys. What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 06 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Know what changed before your coffee is cold.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Blog

URL: https://lopebase.com/blog

Practical notes on running a portfolio of SaaS products: admin, revenue across Stripe accounts, audit trails, and the tools that tie it together.

Notes on running more than one product.
Practical writing on admin, revenue, analytics, and keeping a record, for people who ship several small SaaS products. RSS
October 8, 2026A weekly SEO routine for founders running several SaaS products
A 20 minute weekly SEO check for founders running more than one SaaS site: page-two searches, skipped titles, competing pages, indexing, and speed.
Read October 5, 2026Tools for running several SaaS products at once
The tools founders use to run several SaaS products, from admin builders to revenue analytics, with current pricing and where each one falls short.
October 2, 2026A weekly review routine for founders running several SaaS products
A 30 minute Monday review for founders running more than one SaaS product: what to check, in what order, and how to turn it into a short list to act on.
Read September 30, 2026How to run several SaaS products without building an admin for each one
A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.
Read September 29, 2026How to track MRR across multiple Stripe accounts
Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.
Read September 28, 2026What an admin audit trail should record (and why "who changed this?" should take one search)
The fields every admin action should record, why the before and after matters most, and how to keep an audit log useful instead of noisy.
Read More for people running several products
The blog covers how to run a small portfolio well, whatever tools you use. These go with it.
Portfolio MRR calculator Add up MRR across every product, with yearly plans and discounts handled. Runs in your browser.Comparisons LopeBase next to Retool, Forest Admin, Databox, Baremetrics, ChartMogul, and building your own.An SEO MCP server Give your AI agent search and analytics data for every site you run.Changelog What shipped in LopeBase, by date.

---

## What an admin audit trail should record (and why "who changed this?" should take one search)

URL: https://lopebase.com/blog/audit-trail-for-admin-actions

The fields every admin action should record, why the before and after matters most, and how to keep an audit log useful instead of noisy.

Blog What an admin audit trail should record (and why "who changed this?" should take one search)
By Caden Sumner · September 28, 2026 · 6 min read
Sooner or later a customer writes in: "My plan changed and I did not change it." Without an audit trail, you guess. With a good one, you search, find the change, and answer in a minute.
The fields that matter
Who. The person or system that made the change. Not "admin". The actual operator.
When. A timestamp in UTC.
Where. Which product, and which record type and id. product-two / users / usr_8f2.
What. The named action, like extend_access, not "updated row".
Before and after. The exact values that changed. This is the field people skip and the one that answers the question.
Why named actions beat raw edits
If admins can edit any column, your log fills with field changes that nobody can interpret later. Named actions carry intent. grant_credits with a before and after of 40 and 65 tells the whole story.
Keep it where you can search it
An audit log you cannot filter by product, person, action, and date is a log nobody reads. Make it exportable too, as CSV or JSON, so a compliance question or a refund dispute is one download.
What not to record
An audit trail is read by more people than the data it describes, so keep secrets out of it. Never write passwords, tokens, API keys, or full card numbers into a before or after. For personal details, record enough to tell records apart, like a masked email, unless you truly need the full value. If a field is sensitive, record that it changed, not what it changed to.
How long to keep it
Keep it at least as long as anyone could reasonably ask about a change. Refund disputes and "why did my plan change?" emails often arrive weeks later. A year covers most questions; some teams keep everything. Whatever you choose, make the audit log append-only, so nobody, including you, can quietly edit history.
Common mistakes
Logging only failures. The changes that worked are the ones people ask about.
A shared admin login. If three people use one account, "who" is useless. Give every operator their own login.
Free text instead of fields. "Gave Dana some credits" cannot be filtered. Store the action, the record, and the values as fields.
No link to the record. An entry should open the record it changed, so the next question takes one click.
Write it on both sides
If your admin tool calls into your product to make a change, record the change in both places: in the admin tool, and in your product's own table. If either side is ever questioned, the other one agrees.
How LopeBase does it
Every change in LopeBase is a named action with a confirm step. Each one writes an audit event with the operator, product, record, time, and before and after, and the admin adapter in your product writes its own row too. The feed filters by product, person, action, and date, and exports as CSV or JSON. See it in the tour.
Run every product from one console.Free for one product. No card. Start free How to run several SaaS products without building an admin for each one A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.How to track MRR across multiple Stripe accounts Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.

---

## How to run several SaaS products without building an admin for each one

URL: https://lopebase.com/blog/run-several-saas-products-one-admin

A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.

Blog How to run several SaaS products without building an admin for each one
By Caden Sumner · September 30, 2026 · 6 min read
The first product gets an admin page because you need one. You need to look up a user, fix a plan, and see who signed up this week. It takes an afternoon.
The second product gets a copy of that page. The third gets a copy of the copy. By then you have three logins, three sets of tables that drift apart, and none of them show revenue, traffic, or errors. Those live in Stripe, PostHog, and Sentry, in three more tabs per product.
Here is a way to set things up so the next product costs you almost nothing in admin work.
1. Decide what "admin" actually means for you
For most small products it is the same short list:
Look things up. Find a user, their plan, their recent activity.
Fix things. Grant credits, extend access, resolve a report, publish or unpublish content.
Watch things. Revenue, signups, active users, errors, search traffic.
Know what changed. Who did what to which record, and when.
Write that list down for each product. You will notice the products differ in their records, not in the shape of the work.
2. Separate your records from your tools
Your product owns its records: users, subscriptions, content. Your tools own everything else: Stripe owns payments, PostHog or Google Analytics owns traffic, Sentry owns errors.
A good admin setup reads the tools and asks your product for its records. It should not copy your database, and it should not need a database password. Expose a small, explicit list of records and actions from each product, over HTTPS, behind a token.
3. Make every change a named action
"Edit any field on any row" is how data gets broken at 11pm. Instead, give each change a name and typed inputs: grant_credits(userId, amount), extend_access(userId, days). Named actions are easy to confirm, easy to permission, and easy to record.
4. Record the before and after
For every action, keep who ran it, which product, which record, the time, and the exact values before and after. When a customer asks why their credits changed, the answer should take one search. We wrote more about this in what an admin audit trail should record.
5. Put the numbers side by side
The reason to keep products in one place is comparison. Which product grew this month? Which one has a spike in errors? Which one lost search traffic? That only works if revenue, users, errors, and search sit on one screen with one row per product. If you are adding up MRR across several Stripe accounts by hand, this calculator does it in a minute, and this post covers the details that trip people up.
6. Make the next product a config change
With the above in place, launching a new product means describing its records and actions once and connecting its tools. No new admin pages, no new auth, no new tables of logs.
Doing it with LopeBase
This is the setup LopeBase is built around. Each product connects through a small adapter you host, connectors read Stripe, PostHog, Sentry, and the rest, actions run with a confirm step, and the audit log keeps the before and after. We built it to run our own products.
Run every product from one console.Free for one product. No card. Start free How to track MRR across multiple Stripe accounts Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.What an admin audit trail should record (and why "who changed this?" should take one search) The fields every admin action should record, why the before and after matters most, and how to keep an audit log useful instead of noisy.

---

## A weekly SEO routine for founders running several SaaS products

URL: https://lopebase.com/blog/seo-for-several-saas-products

A 20 minute weekly SEO check for founders running more than one SaaS site: page-two searches, skipped titles, competing pages, indexing, and speed.

Blog A weekly SEO routine for founders running several SaaS products
By Caden Sumner · October 8, 2026 · 6 min read
SEO for one product is a habit. You check Search Console on Monday, notice a page slipping, and fix it by Wednesday.
SEO for three products is a list of tabs you mean to open. Each site gets attention when traffic falls off a cliff, and the slow, fixable things go unnoticed for months: a search that has sat at position 12 since spring, a title nobody clicks, two blog posts quietly fighting over the same query.
You do not need a bigger SEO tool to fix that. You need a short routine that looks at the right five things, in the right order, for every site. Here is the one we use. It runs on free data from Google and Bing and takes about 20 minutes for all products together.
Before you start: use the data search engines give you
Most SEO dashboards lead with estimated search volume and keyword difficulty. Those numbers come from third-party panels and often disagree with each other. For a small site, the data that matters most is free and exact: Google Search Console tells you every search you appeared for, how often, where you ranked, and how often people clicked.
Two definitions are worth knowing before you read any of it. An impression is one appearance in a result someone saw, and position is your average spot across those impressions, with 1 at the top. Google explains both in its guide to the Performance report metrics. Search Console also runs a couple of days behind, so do not panic over a quiet Sunday.
Use the last 28 days for each check, and compare it with the 28 days before. Week to week is too noisy for a site getting a few hundred clicks.
1. Find the searches on page two
Open the Performance report, show the Queries table with position turned on, and filter for position between 11 and 20. These are often called striking distance keywords. Google already thinks your site is relevant for them, but page two gets a small share of the clicks that page one gets.
Sort what is left by impressions. The top few are your best bets: lots of people search them, and you are close. For each, find the page on your site that best answers the search and ask one question: does it answer this exact search, plainly, near the top? Usually the fix is a new section, a clearer heading that uses the searcher's words, and a link to the page from two or three related pages.
If no page answers it, that is next week's article. If you want to try this on an export without logging in to anything, our striking distance keyword finder does the filtering in your browser.
2. Fix the titles people skip
Next, look at page-one searches with a low click rate. "Low" should mean low for your site, not against a chart from someone else's industry. Work out your site's overall click rate (total clicks divided by total impressions), then list page-one queries and pages that fall well below it.
When a page ranks on page one and still gets skipped, the problem is almost always what people see in the result: the title and the snippet. Google builds the title link mostly from your page's title element, and often uses your meta description for the snippet. Rewrite both to say plainly what the page gives the reader, using the words from the searches it already shows up for. No clickbait; a title that overpromises gets clicked once and bounced from.
Change one or two pages a week, note the date, and check them again in four weeks. Changing everything at once makes it impossible to tell what worked.
3. Look for pages competing with each other
This one is easy to miss when you write a lot. Two pages on the same site both show up for one search, each getting a real share of the impressions. Google tends to pick one at a time and can switch between them, so neither ranks as well as one strong page would. It is often called keyword cannibalization.
In Search Console, click into a query and open the Pages tab to see which of your pages appear for it. If two pages each take a sizeable share, decide which one should be the answer. Then either merge the weaker page into it and redirect, or make the difference between them obvious and link from the weaker to the stronger. If the pages are near copies, tell Google which one you prefer with a canonical link, as described in Google's guide to consolidating duplicate URLs.
Do not chase every overlap. A page that gets a handful of impressions for a search is noise. Look at the searches with the most impressions first.
4. Check that new pages are indexed
A page Google has not indexed cannot rank at all, and new articles are the ones most likely to be stuck. Take anything you published in the last month and run it through the URL Inspection tool in Search Console, which tells you whether the page is on Google and, if not, why. The same check is available as the URL Inspection API if you want to automate it.
The common reasons a page is left out are fixable: a stray noindex tag left over from staging, the page missing from your sitemap, or no other page linking to it. Search engines that support IndexNow can also be told about new pages the moment they go live.
5. Glance at speed for real visitors
Last, and quickest: check Core Web Vitals. Google publishes the thresholds on web.dev. Loading (Largest Contentful Paint) under 2.5 seconds, responding to input (Interaction to Next Paint) under 200 milliseconds, and layout shift under 0.1 count as good, judged at the 75th percentile of visits. Google recommends good Core Web Vitals for success in Search, and they matter more to visitors than to rankings.
Use field data from the Chrome UX Report, which comes from real Chrome visits, rather than a single lab test from your fast laptop. You are only looking for one thing here: did a number cross from good into needs improvement since last time? That usually points at a recent change, like a new font, a heavy image above the fold, or a script added to every page.
Write the short list
End the same way every week: at most three actions across all your products, each with its reason. For example: add a section to the pricing page for a search at position 13, rewrite the title of a page seen 4,000 times and clicked 20, merge two posts that split one search. Next week, start by checking whether last week's three got done, then run the five checks again.
If you want this as part of a broader weekly review, with revenue, uptime, and errors alongside, the weekly review routine covers the rest.
Doing it with LopeBase
We run several products ourselves, so we built this routine into the LopeBase SEO tab. It reads Search Console and Bing for every product you connect. The Overview shows the last 28 days against the period before, an opportunity map with page-two searches picked out, and your own click rate at each position. The Pages tab lists pages seen but rarely clicked and pages competing for the same search. Health checks indexing, Core Web Vitals, and on-page basics, and Links shows who links to you. Every finding can be copied as a prompt for your coding agent or sent to the content autopilot as an article.
Every product's search, on one screen.Free for one product. No card. Start free The SEO suite in LopeBase Rank tracking, an opportunity map, site audits, Core Web Vitals, index checks, and backlinks, from your own search data.A weekly review routine for founders running several SaaS products A 30 minute Monday review for founders running more than one SaaS product: what to check, in what order, and how to turn it into a short list to act on.

---

## Tools for running several SaaS products at once

URL: https://lopebase.com/blog/tools-for-running-several-saas-products

The tools founders use to run several SaaS products, from admin builders to revenue analytics, with current pricing and where each one falls short.

Blog Tools for running several SaaS products at once
By Caden Sumner · October 5, 2026 · 7 min read
When we had one product, checking on it meant opening Stripe and PostHog. By the third, it was Stripe three times, PostHog three times, Search Console, Sentry, and an uptime monitor, most mornings. That is part of why we build LopeBase, which is one of the tools below, so read this knowing we have a stake in the answer. Every other tool here is described from its own website and pricing page as of October 2026, and where another tool does a job better than ours, we say so.
What we check every week
Our own weekly list is short. What each product earned, and whether any payments failed. How many people visited and signed up. Which searches brought them in. Whether anything went down, threw errors, or failed to build. And when someone on the team changed a customer's account, a record of what they changed.
Each of the tools below covers part of that list. None of them covers all of it without some setup.
What changes with several products
With one product, almost any tool works. With several, a few things start to matter. You want a total and a row per product, so growth in one product does not cover for a decline in another. You want read-only access, because a reporting tool has no reason to hold a key that can refund a charge. And you want to know what the price counts. Seats, data sources, billing accounts, and revenue all grow at different rates as you add products, and that can matter more than the starting price.
Building it yourself
For a single product, this is usually what we would suggest. A page that calls the Stripe API, your analytics API, and Search Console costs nothing, shows exactly the numbers you care about, and sits next to the rest of your code.
The trouble starts with the second product. You either copy the page and keep two of them working, or you make it generic and end up maintaining a dashboard alongside the products you actually sell. The parts that tend to get skipped are uptime checks, alerts, and an audit log, since nobody needs them until something breaks. Our page on LopeBase vs building your own goes into more detail.
Retool and Forest
Retool is for building internal apps on your own data. You put screens together from components and connect them to your databases and APIs, which makes it a good fit for something like a support console or a refund flow. It charges per person. On annual billing, Team is $10 a month per builder and $5 per internal user, and Business is $50 and $15. There is a free plan for up to 5 users.
Forest, which used to be called Forest Admin, puts an admin panel on top of your application's data. A backend runs on your own infrastructure and reads and writes your data sources directly. Forest describes itself as infrastructure for regulated companies, and the pricing reflects that: after the free Sandbox plan, Starter is $499 a month.
Both are about records, meaning finding a customer and changing something about them. In either one, a view of revenue, traffic, search, and uptime across products is something you would build yourself. We compare each with LopeBase on the Retool and Forest Admin pages.
Databox
Databox connects to more than 130 tools, by its own count, and builds dashboards, reports, and goals from them. It is aimed at teams reporting on marketing and sales across ads, CRMs, and spreadsheets.
If you run several products, look at how it counts data sources. Each account, property, or view counts as one, so three products with their own Google Analytics property use three. The free plan allows 3 data sources, and Analyst, at $71 a month on annual billing, allows 5. You also design the dashboards and set the thresholds yourself, so deciding what counts as a problem for each product is part of the setup. More on the Databox comparison.
Baremetrics and ChartMogul
Both are subscription analytics tools. They report MRR, churn, segments, and forecasts, and they read from many billing systems, including Stripe, Paddle, and the app stores. For detailed revenue analysis, they do more than anything else in this post.
Their pricing is tied to revenue. Baremetrics Launch costs $75 a month for up to $360K ARR. ChartMogul is free up to $10K MRR, and its paid plans cost more as revenue grows. They also count billing accounts. Baremetrics Launch includes one integration, ChartMogul's Free and Starter plans connect one billing system, and its Pro plan connects up to 5. If every product has its own Stripe account, that decides which plan you need. We compare both on the Baremetrics and ChartMogul pages.
LopeBase
LopeBase is what we built for our own version of this problem. You connect each product's existing tools, using read-only keys or one-click sign-in, and the products appear together on one Overview. Revenue comes from Stripe and Polar, traffic from PostHog, GA4, Plausible, or Cloudflare Web Analytics, and search data from Search Console and Bing. Sentry errors, GitHub builds, and uptime checks every 15 minutes sit alongside them. When something needs attention, like a past-due subscription or a site that stopped responding, it is listed on the Overview and can be sent to you by email or push notification. Changes made through the console are recorded in an audit log, with the values before and after.
It does not cover everything in this post. It cannot edit your database the way an admin panel can, though your app can expose specific actions through the LopeBase Adapter. It reports MRR, 30-day revenue, and past-due subscriptions, but not churn or cohorts. And for billing it reads only Stripe and Polar. Pricing is per product: free for one, $29 a month for 3, $99 for 10, and $299 with no limit.
Choosing
If you need screens that change your own data, look at Retool or Forest. If you report on marketing and sales from many different tools, Databox is built for that. If churn and forecasting are where you spend your time, try Baremetrics or ChartMogul. If you have one product and enjoy writing the code, build it yourself. LopeBase fits when you have several products and want their revenue, traffic, search, uptime, and errors together without building the view.
You may end up using two of these: one for the daily check across products, and one for a job that needs more depth, like an admin panel for support or a revenue tool for investor updates. If so, choose the daily one first, because that is the one you will open every morning.
If you are still adding up MRR by hand, the portfolio MRR calculator will do it in your browser, and our weekly review routine covers what to check once the numbers are in front of you.
Every product on one screen.Free for one product. No card. Start free How LopeBase compares Side by side with Retool, Forest Admin, Databox, Baremetrics, ChartMogul, and building your own, with pricing and sources.How to run several SaaS products without building an admin for each one A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.

---

## How to track MRR across multiple Stripe accounts

URL: https://lopebase.com/blog/track-mrr-across-multiple-stripe-accounts

Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.

Blog How to track MRR across multiple Stripe accounts
By Caden Sumner · September 29, 2026 · 7 min read
If each of your products has its own Stripe account, there is no single screen in Stripe that shows your total monthly recurring revenue. Here is how to get an honest number, and what usually makes it wrong.
What counts as MRR
MRR is the monthly value of your active recurring subscriptions. A few rules keep it consistent:
Normalize to a month. A yearly plan counts as its price divided by twelve. A quarterly plan counts as its price divided by three.
Use what customers actually pay. Apply ongoing discounts. A 50% off coupon that lasts forever halves that subscription's MRR.
Leave out one-off charges. Setup fees and credit packs are revenue, but not recurring revenue.
Decide on trials. Most people leave free trials out until the first paid invoice. Pick a rule and keep it.
Count past-due carefully. A subscription in past_due may still recover. Track it separately so a wave of failed cards is visible.
Currencies
If products charge in different currencies, convert to one reporting currency at a stated rate. Mixing euros and dollars in one total is the most common reason portfolio MRR looks off.
Getting the data safely
Use a restricted key per Stripe account, with read access to subscriptions, customers, and charges. Do not use a secret key for reporting. A read-only key cannot move money if it leaks, and you can revoke it without touching anything else.
Adding it up
For each account, list active subscriptions with their price, interval, quantity, and discount.
Normalize each one to a monthly amount.
Sum per product, then sum across products.
Keep past-due and trialing totals next to the main number, not inside it.
For a quick estimate, the portfolio MRR calculator does the normalizing and the totals in your browser. Nothing you type leaves the page.
Mistakes that make the total wrong
Counting a yearly payment in the month it lands. A $240 yearly plan is $20 of MRR every month, not $240 in March and nothing after.
Counting the same customer twice. If one customer pays for two products, they are two subscriptions and belong in both products' MRR. But if you report customers, count them once.
Including test mode. Make sure each key reads live data. Test subscriptions look real in a quick export.
Forgetting a product that sells elsewhere. If one product sells through Polar or another billing tool, its MRR needs adding in the same way, normalized to a month.
Hiding a falling product. A portfolio total can grow while one product shrinks. Keep a row per product under the total, and look at both.
Check against Stripe
Once you have a number, check one product against what Stripe reports for that account. If they differ, the cause is nearly always one of the rules above: trials, discounts, past-due, or a yearly plan counted in full. Settle the rule, write it down, and use it every month. A slightly different definition used consistently is more useful than a perfect one used once.
Keeping it current
A spreadsheet works for a month. After that you want the number to update itself, per product, next to signups and traffic. LopeBase's Stripe connector reads each account with its own restricted key and shows portfolio MRR on the Overview, with one row per product. Products that sell through Polar add into the same total, and past-due subscriptions show separately under Needs attention.
Run every product from one console.Free for one product. No card. Start free How to run several SaaS products without building an admin for each one A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.What an admin audit trail should record (and why "who changed this?" should take one search) The fields every admin action should record, why the before and after matters most, and how to keep an audit log useful instead of noisy.

---

## A weekly review routine for founders running several SaaS products

URL: https://lopebase.com/blog/weekly-review-for-saas-founders

A 30 minute Monday review for founders running more than one SaaS product: what to check, in what order, and how to turn it into a short list to act on.

Blog A weekly review routine for founders running several SaaS products
By Caden Sumner · October 2, 2026 · 4 min read
With one product, you notice when something is off. You are in the dashboard every day, you see the support emails, and a drop in signups is hard to miss.
With three products, you stop noticing. Each one gets a glance when something breaks, and the slow problems slip past: a payment method that keeps failing, a page that used to bring in visitors and quietly stopped, a site that went down for twenty minutes on Saturday night.
A short weekly review fixes that. Here is the routine we use, in the order that catches the most for the least time.
Pick one time and keep it small
Monday morning works for most people, before the week fills up. Give it 30 minutes for all products together, not per product. If the review takes longer than that, it will not survive a busy week, and a review you skip is worth nothing.
The goal is not to understand everything. It is to end with a short list: at most three things to do this week, each with a reason.
1. Money first: what is at risk
Start with revenue, because it is the one place where waiting costs you directly. For each product, look at:
Past-due subscriptions. These are customers who want to pay and could not. Most can be saved with one email asking them to update their card.
Subscriptions set to cancel. They have not left yet. A short, personal note asking what was missing sometimes changes the answer, and the reply tells you something either way.
Failed payments this week. One is noise. Several on the same product can mean a checkout or billing problem.
MRR against last week. Only after the above, since the total moves slowly and the problems inside it do not.
If your products bill through separate Stripe accounts, total them carefully. This post on MRR across Stripe accounts covers the details that make totals wrong.
2. Did anything break
Next, look back over the week for outages and errors. Two questions matter:
Was anything down, and for how long? Uptime checks every few minutes give you the start, the end, and what the failed check saw, like a timeout or a server error.
Is one error growing? In your error tracker, sort unresolved issues by events in the last day. A new error near the top that lines up with an outage is usually the one to fix first.
If customers could have noticed downtime, write a short note for your status page or changelog: what happened, when, and that it is fixed. Plain and calm beats detailed. People mostly want to know you saw it.
3. Traffic: what moved, and why
Compare this week's visitors with last week's for each product. Do not chase small changes; a busy news day elsewhere can move a small site's numbers. Look for:
A page that dropped out of your top pages. Check whether it still ranks for the searches that used to bring people in.
Pages that people see in search but do not click. A clearer title and description is often the cheapest win you have.
Visitors that do not turn into signups. If traffic rose and signups did not, the new visitors may be looking for something else.
4. What shipped, and what to share
Last, list what went out this week: features, fixes, articles. Two reasons. It keeps the review honest about where time went. And anything worth building is usually worth one post: a line on X, a few on LinkedIn, a paragraph in your newsletter, or a helpful summary in a community where people talk about the problem it solves.
5. Write the short list
End by writing down at most three actions, each with the reason from the review. For example: email the four past-due customers on one product, rewrite the title of a page people see but skip, post a status note about Saturday's outage. Then close the tabs.
Next Monday, start by checking whether last week's three got done.
Doing it with LopeBase
We built this routine into LopeBase because we run several products ourselves. Every product's revenue, traffic, uptime, and errors sit on one screen. On top of that, AI reviews do the reading for you: a weekly briefing on Overview, a revenue review that flags what is at risk, a traffic review that points at the pages to work on, an incident review that drafts the status note after downtime, and posts to share any article. Each one uses only your own numbers and lists what it read. The weekly digest email covers the same week if you would rather read it in your inbox.
Every product's week, on one screen.Free for one product. No card. Start free How to run several SaaS products without building an admin for each one A practical way to run two, three, or ten small SaaS products without rebuilding admin, analytics, and support tooling every time you launch.How to track MRR across multiple Stripe accounts Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.

---

## Changelog

URL: https://lopebase.com/changelog

Everything that has shipped in LopeBase, newest first: setup from the terminal, the content autopilot, the SEO toolkit, new connectors, and more.

What is new.
Everything that has shipped in LopeBase, newest first. We run our own products on it, so this moves quickly.
October 8, 2026 The contact form sends. Messages from the contact page now reach us, with a clear confirmation when they are on their way and a plain note if something goes wrong.
LopeBase is in Claude's directory. Find LopeBase at claude.ai/directory/lopebase and connect it from there in a couple of clicks. The one-address setup still works too.
A bonus for upgrading early. Subscribe to any paid plan, monthly or yearly, before your trial ends and get 500 bonus AI credits, on top of whatever the plan includes. It is added automatically and shows up on Billing. How it works.
Yearly billing, two months free. Every paid plan can now be billed yearly for the price of ten months: Studio $290, Portfolio $990, and Agency $2,990 a year, with the same limits as monthly. Pick Yearly on the Billing screen, and see how your current plan is billed and when it renews. How it works.
Write a review. You can now leave a star rating and a short review from the Feedback button. We only show a review on our site if you tick OK to share this publicly. LopeBase may ask for one after a big step, at most once every 14 days, and you can tell it not to ask again.
A clearer Uptime page. Uptime now opens with one line saying whether everything is up, and anything down or degraded is pinned under it with buttons to open the property, post a status note, or see the outage. Sites show as compact cards, problems first, and outages, Better Stack monitors, and status pages each have their own tab.
Delete a property. Admins can now delete a property they no longer run, from the bottom of its page or from Settings, Your data. It removes the property's connections, uptime history, status page, and SEO and content data, and the audit log keeps a record.
Better Stack monitors on the Uptime page. Monitors you connect from Better Stack now show on the Uptime page with their status and 30-day availability, and a monitor that is down counts in the summary at the top.
Property cards on Overview. Overview now shows each property as a card with its revenue, users, signups, and traffic, in place of the table, and stacks them in one column on a phone. Cards on Overview and SEO show the logos of the tools a property is connected to instead of their names; hover one to see which it is.
Docs and help. A new help center covers setup, every page in LopeBase, and fixes for common problems, with search and links straight to the right screen. Open it from Help and docs in the account menu at the bottom of the sidebar.
Dialogs that fit on a phone. A few dialogs, including the icon picker, could grow taller than what actually showed on a phone, hiding the buttons below the on-screen keyboard or the browser's toolbar. They now size to what is visible and scroll inside instead.
Service checks that test your own setup. LopeBase Adapter 0.4.1 lets you mark a service non-critical, so its failure shows as degraded on the Uptime page instead of reporting the whole product down. Setup now has your coding agent check each service with your app's own credentials, like a select 1 or Stripe balance.retrieve, instead of pinging a vendor's site, and keep a passing result for a minute but a failing one for only 10 seconds, so checks do not use up your API limits while a recovery still shows up quickly.
Know when a connection needs reconnecting. When a service stops accepting a connection's key or sign-in, LopeBase checks it again before saying anything, then shows "Needs reconnecting" on Connections, a notice in the bell, and a Reconnect link next to the numbers. A one-off hiccup no longer looks like a broken connection.
Faster dashboards, gentler on your services. Dashboards now open from numbers LopeBase keeps, like Overview does, and pages show when they were updated with a Refresh button. LopeBase only asks a service again for numbers someone is looking at, and waits when a service asks it to slow down.
One address for Claude. Connect LopeBase in Claude with one address, app.lopebase.com/api/mcp, and sign in as usual: LopeBase opens your own workspace, or asks which one if you belong to several.
Sign up from Claude without starting over. If you create your LopeBase account while connecting Claude or npx lopebase login, you now land back on the approval step even if signing up took a while, and the same holds when you pick from several workspaces.
Signed out cleanly. After you sign out of every device, a phone or installed app that was still open now lands on the sign-in page instead of reloading over and over.
Notifications. A bell at the top of the sidebar shows how many things need a look, and opens one page with all of them, grouped by property. Adapter updates and connections that stopped refreshing land there. Mark each one done or dismiss it, and it stays quiet until something new happens.
Know when to update. Notifications now say when a product's LopeBase Adapter is behind, what the new version adds, and gives you a prompt to copy. Run npx lopebase update in the product's folder and your coding agent does the upgrade, asking before each change. New npx lopebase releases show on Overview too.
The same nudge on Connections. The LopeBase Adapter card on Connections now shows a small icon when a property is running an older adapter. Open the card to see which properties are behind, what the newer version adds, and copy buttons for the update command and the prompt for your coding agent.
Pageviews counted by LopeBase. Pick a product on Analytics and copy one tag into your site, or let your coding agent add it. LopeBase then counts pages, sources, and visits itself, with no cookies and no visitor ids.
Watch every service, not just the home page. The LopeBase Adapter can now list the services your app depends on, like the database, a queue, or a second API. Point the product's uptime check at the adapter's health address and each one is checked every 15 minutes, with alerts that name the service that failed.
A smarter npx lopebase. The setup command has a fresh look, lists what in your stack is worth an uptime check, and asks whether you want LopeBase pageviews before your coding agent takes over.
Status pages, better. Public status pages now show your site's icon, 90 days of history, and uptime over the last 12 months, with a calmer look. Edit a note after posting it, say which part of the product it is about, and follow notes by RSS. Each page has a live status badge for your site or README. Paid plans can also pick the colors and light or dark.
Post the incident note in one click. After downtime, the incident review's drafted note has a button to post it straight to your status page.
Status page updates as alerts. Turn on "Status page updates" in your alert settings to get each note a teammate posts by email or browser push.
A year of uptime. The Uptime page now shows uptime over 90 days and 12 months next to the shorter windows, and status pages show each part's uptime over the last 12 months.
Public status pages. Turn on a status page for any property from the Uptime page and share the link. It shows live status and 30 days of uptime for the parts you pick, plus updates you post. Free on every plan. Paid plans can add a logo and leave off the LopeBase footer.
A clearer SEO overview. The SEO tab now shows how clicks, impressions, and position moved against the period before, an opportunity map of every search with page-two searches picked out, how many searches rank in each stretch of the results, your own click rate at each position, and how many clicks come from people searching your name.
AI runs keep going when you leave. Start an SEO audit, an AI review, an article draft or rewrite, topic and keyword ideas, a discussion search, an AI report, or a pipeline, then carry on using LopeBase or close the tab. It finishes in the background, shows as running when you come back, and a note tells you when it is done if you are elsewhere in the app.
That note follows you across tabs too. If LopeBase is open in more than one tab, the note that a run finished shows once, in whichever tab you are looking at, with a button straight to the result.
Links tab to Discussions. Under "Where people talk about it", a link now takes you to Discussions, which finds recent threads about the problem your product solves.
A new Pages tab in SEO. See clicks by site section, pages on page one that are seen but rarely clicked, your top pages, and searches where two of your own pages compete with each other, with what to do about each.
Competitors on their real site. The SEO audit now checks that each competitor it finds lives at that address and names the product, skips parked and for-sale domains, and finds the right ending when a guess was wrong (such as .dev instead of .com).
A trial reminder on Overview. Partway through your trial, Overview shows what you have connected and used so far, and which of it would be affected by moving to Free, with a button to upgrade and how many days are left. Admins can dismiss it for a few days at a time.
October 6, 2026 A clearer indexing check. The SEO Health tab now says plainly that its indexing ring is a spot check of up to 40 pages, and shows beside it how many of your pages appeared in Google search over the last 28 days, a site-wide number.
One Cloudflare connection. Cloudflare is now a single card on Connections, under Infrastructure, Monitoring, and Analytics. One sign-in reads your Worker health and also turns on Web Analytics for each property whose site it finds, and a switch inside the card moves between Workers and Web Analytics, where you can turn either off for a property.
Easier to find what to connect. Connections now has fewer, clearer categories. Error trackers like Sentry sit under Monitoring with uptime checks, GitHub sits under Infrastructure with Cloudflare and Supabase, Stripe, Polar, and your bank accounts share one Money category, and the LopeBase Adapter has its own category with the LopeBase mark.
Connect Better Stack and Bugsnag. Bring the Better Stack monitors you already run: a monitor Better Stack reports as down shows under Needs attention and alerts you right away, with 30-day availability beside each product. Bugsnag joins Sentry, Rollbar, and Honeybadger for errors. Both connect read-only and list your monitors or projects to pick from.
Connect Rollbar and Honeybadger. Both now sit under Monitoring on Connections, read-only. Their open errors, daily counts, and error spikes show for each property the way Sentry's do, including in the incident review, and npx lopebase spots them in your code.
Errors from PostHog. If you use PostHog error tracking, LopeBase now reads its exceptions the way it reads Sentry: top errors, a daily count, error spikes on a property's timeline, and the incident review. The setup cards on a property can now be closed when it does not use a tool.
One-time revenue next to MRR everywhere. Overview now has its own One-time (30d) tile beside MRR and a One-time column for each property, the Overview and Revenue dashboards show it as its own card, and the weekly email lists it with your numbers and in the table by property. Recurring and one-off revenue stay separate, so you see all of it without mixing the two.
Emails that show your own numbers. The emails about your trial ending, moving to Free, or a plan ending now say what LopeBase tracked for you that week, such as pageviews, signups, and MRR across your properties, and a new email the day after your first connection shows your first numbers.
A setup list for your first week. Overview shows a short list of first steps, each with a button to where it is done: add your site, connect a tool, then three, turn on alerts, run an AI review, and invite a teammate. Each step ticks itself off, and you can hide the list. Skip any step that does not apply to you, such as inviting a teammate when you work alone, and undo it later if you change your mind.
Setup starts with your website. Adding your first property now asks for its website first and names the property from it, so its icon and connections are ready when you arrive. A product with no site yet can still skip it.
See what an AI button is doing. While the SEO audit, an AI review, or article writing runs, the line under its button now names the step it is on, such as Writing the draft, 3 of 6, instead of a list that pushed the page around.
A calmer Now list on Overview. A connected tool that stops answering now shows there only after it has failed for an hour, the same wait as alert emails, so short blips no longer fill the list. A card can be tapped to read it in full only when its words are cut off.
The theme button waits for a click. The theme picker next to your name no longer pops open when you only move the mouse over it.
Charts on every connection. Open any connection, or one of its lists, and its data now shows as a picture that fits it: totals and a trend per day for daily numbers like Bing clicks and impressions, ranked bars for top lists like search queries, and counts for a set of values like statuses. The full table is still underneath.
The CLI spots Plausible. npx lopebase now finds Plausible on your site and offers to connect it, and no longer says a Plausible site has no analytics.
Discussions (beta). A new page finds threads on Reddit, X, Hacker News, and other forums where people talk about what each property does, with a line on why each fits. Open one on its site, then mark it responded or not relevant. Set the topics it searches for yourself, or have it suggest some from your site. Each search uses AI credits.
Recent activity follows your focus. When you focus Overview on one property, its recent activity list now shows only that property's actions and workspace-wide changes, and it stays within your plan's audit history like the Audit page.
No false alerts when a service is busy. When a connected tool such as Cloudflare Web Analytics briefly limits how often LopeBase can read it, LopeBase no longer reports the connection as down or its data as missing. It waits for the next reading instead.
Fewer alerts for brief connection hiccups. When a connected tool stops answering, LopeBase now waits until it has failed for an hour before it emails you or sends a browser alert. Short blips still show on Overview, and a site that goes down still alerts right away.
October 5, 2026 Products over your plan pause instead of running free. When a trial ends or a workspace moves to a smaller plan, the products connected first keep updating up to the plan's limit, and the rest pause with their settings and history kept. Billing lists what is paused, and choosing a plan with room turns them back on right away.
Pick a plan before you sign up. Choosing Studio, Portfolio, or Agency on the pricing page now opens Billing on that plan as soon as your workspace is ready.
Undo a deleted workspace. Deleting a workspace closes it right away, then removes it for good after 14 days. Until then, every admin gets an email with a link to restore it as it was.
Tidier content settings, with image examples. A product's content voice is now split into tabs: Voice, Rules, Each article, Images, and Checks. Images shows an example of each style, photos, illustrations, diagrams, and interface mockups, so you can see the look before you pick one.
Closer credit estimates for square images. Square images cost less than wide or tall ones, and the estimate on the content settings now says so instead of pricing every shape the same.
AI fills in your SEO tabs. On Keywords, Suggest searches proposes searches worth tracking (add one with a click) and Clear junk searches stops tracking the ones that are not worth it. On Links, Find competitors names sites you compete with, and Where to get links lists directories, review sites, communities, and newsletters where you could earn a link. Every suggested site is checked to be real before it shows, and each button shows its credit cost first.
A calmer SEO overview. What to do next is now one list, most seen first, with one action per search and the rest behind Show more. The AI review lists articles to write without a wall of tags, and it and Top searches can be folded away. The Health tab now says what each check is for and how to fill it in, including when your domain runs out.
Your AI agent can read your search and analytics data. Two new MCP tools, list_sources and read_source, let Claude, Codex, Cursor, or any MCP client read every Search Console query and page with its position, Bing queries and inbound links, and the channels, landing pages, conversions, retention, and funnels from GA4, Plausible, PostHog, and Cloudflare Web Analytics, for every site you connected. They return totals only, never visitor or customer records. list_metrics now also lists the pageview numbers for PostHog, GA4, Plausible, and Cloudflare sources, which it left out before. See what you can ask.
Bing Webmaster Tools works, by signing in. Connect Bing on one product or all of them at once: approve read-only access on Bing's own page, and each product is matched to its verified site by domain. Bing was turning away every request from LopeBase's servers, so Bing numbers never arrived before. They do now. Pasted Bing API keys are no longer accepted, since they cannot be limited to reading, so if you connected Bing with a key, connect it again with Connect Bing.
SEO groups search by property. A property with both Search Console and Bing shows as one group in SEO, with each source on its own line and its own logo, the way Analytics does. Bing's line now shows its last 7 days like Search Console's, and says Not reported for position, which Bing does not give.
MRR from Stripe everywhere. When a property's app does not report MRR itself, Overview, dashboards, the weekly email, the Monday briefing, and your AI agent now take it from that property's Stripe or Polar account, the way its property page already did, instead of showing n/a. Revenue dashboards now include those properties too, and MRR shows in the account's own currency.
One-time revenue on its own line. Revenue now shows how much of the last 30 days came from one-time payments rather than subscriptions, in total and for each property, from Stripe or Polar. Overview shows it under MRR, and each property page beside its MRR. If your Stripe key cannot read invoices, it says Not reported instead of guessing.
Dashboards show their numbers up front. Each dashboard's card now shows its headline numbers and a trend or status breakdown, so you can read them at a glance and click in for the full board. Dashboards still waiting on a source are listed underneath with what they need.
The Analytics dashboard is easier to read. With every property combined, each number now leads with the total and shows each property's part of it as a bar, and the daily chart has a clear legend. Two new charts show where visitors come from and which devices they use. The switcher at the top now lists your properties; a property measured by two services, such as PostHog and Google Analytics, gets its own small switch between them. Your AI agent can read the two new numbers too.
A nudge to refresh after an update. When a new version of LopeBase goes live while you have it open, a small notice offers to refresh. It never reloads on its own, so nothing you are typing is lost, and Later hides it until the next update.
Mentions from more places. SEO's Where people talk about it now searches Lobsters, GitHub issues and pull requests, and Stack Overflow as well as Hacker News, with a count for each and the newest posts from all of them in one list. Competitors in Domain Rating and on the Links tab now show their logo and their own site name.
Weekly email pageviews count each product once. A product measured by two analytics services, such as PostHog and Google Analytics, had its pageviews added twice in the weekly email's total. It now counts once, from the preferred service, the same as Overview.
Alerts are sent. Each alerts check failed to save what it found, so LopeBase never noticed a change and no alert went out. That is fixed. The first check after this may tell you about anything that is already down or failing.
Indexing checks finish. SEO's check of whether Google has indexed each page often timed out and saved nothing. Pages are now checked a few at a time, and one Google is slow to answer is checked again on the next run instead of holding up the rest.
Domain expiry fills in. SEO's Health tab never showed when your domain runs out, because the public domain registry was turning away LopeBase's lookups. It reads now, and if the registry ever turns a lookup away, Check now says so instead of just Refreshed.
See what Check now is doing. While SEO's Check now runs, it lists each reading as it goes: indexing, page speed, links, domain expiry, competitors, and blog posts. A long running line under a button that spends credits now slides across so you can read all of it, instead of being cut off.
Every checked page in one list. On SEO's Health tab, See all checked pages opens every page Google was asked about, filtered by indexed, not indexed, or not checked yet, each with Google's reason in plain words and when it last crawled the page. The ring chart's hover label no longer has the count showing through it.
Email delivery checks stop false warnings. With one Resend account split across several products, the delivery check often warned on one of them because Resend turned away too many requests at once. Products on the same Resend key now share one read of the account, and a request Resend asks to slow down is tried again.
Pick which lines a chart shows. On any chart with several lines or bars, such as pageviews per day across all properties, click a name in the legend to hide it and click again to bring it back. The chart rescales to what is left, so a small property is easy to read next to a big one.
All my properties for Cloudflare Web Analytics. The All my properties choice now shows for Cloudflare Web Analytics too, so one Cloudflare sign-in connects every product's site at once.
October 4, 2026 Find what to improve, across every source. Analytics has a new Conversion and retention review. It lines up PostHog, Google Analytics, Plausible, or Cloudflare with Search Console, billing, and your app's own numbers: where visitors come from, which pages they land on, how many sign up or buy, how many come back, and where tracking breaks. Each finding shows the numbers behind it, each step names the number it should move, and you can track a step to see on the next review whether that number moved. It uses AI credits, or your own key.
More from your analytics tools. PostHog, Google Analytics, and Plausible now report traffic sources, landing pages, devices, and goals, and PostHog adds funnels and weekly retention. LopeBase finds your signup or purchase event for you, or you can set one on the connection.
Connect Cloudflare in one click. The Cloudflare connector and Cloudflare Web Analytics both have a Connect Cloudflare button: approve read-only access on Cloudflare's own page, and each product's Web Analytics site is matched by its domain, for one product or all of them at once. One sign-in covers both, there is no token to create, and LopeBase never changes anything in Cloudflare. Pasting a read-only API token still works.
Read-only keys, said plainly. Every tool that takes a key now says how to make a read-only one where the service offers it, and exactly what LopeBase does with it: almost all of them only read, and the few that can change something say what. Brex, Rho, and Wise have step-by-step setup too.
Connecting works while a tool is busy. When a tool like Bing is limiting requests as you connect it, LopeBase now saves your key anyway instead of failing, and its numbers fill in once the tool lets LopeBase through. If Bing cannot list your sites at that moment, type the site address instead. A key the tool refuses is still never saved.
Change your name in Settings. Settings has a new Account tab with your name and sign-in email. The Your name item is gone from the account menu.
October 3, 2026 Alerts, in your browser and by email. LopeBase now checks your properties every 15 minutes and tells you when something changes: a site goes down, a build fails on your main branch, payments go past due, email bounces near Resend's limit, or a review is waiting on you. You hear once when it starts, again only if it gets worse, and once when it is fixed. Turn alerts on in any browser, or in the installed app, from Settings, Alerts, and choose how serious, which kinds, and which properties you hear about.
Overview, SEO, Content, and Settings built for phones. Tap a card in Overview's Now list to read all of it, or tap the cards behind it to see the whole list. The audit log and recent activity read as rows, audit filters fold behind one button, and buttons that stood alone fill the width. Article pages keep Approve in reach with the rest under More actions, and chart labels stay readable.
Pipeline runs open again. A pipeline's run page, and the sample pipelines' own pages, could fail to load. They open now, and a check waiting for you shows in orange.
Connections and Pipelines built for phones. On a phone every tool to connect is one short row, dialogs keep a margin and stack their buttons with the next step on top, pipeline steps never run into each other, the step builder uses the full width, and dashboards show two numbers to a row.
Faster pages and property switching. LopeBase now runs next to its database and asks it for less on each page. Overview's Now section checks only the property you are viewing, runs every check at once, and reuses results from the last 30 seconds, so switching back and forth is quick.
Add LopeBase to your home screen. On a phone, LopeBase offers once to install itself: one tap on Android, and on iPhone it shows where Safari's Add to Home Screen is. It never asks again, and never inside the installed app.
Cleaner sign-in and workspace picker. Sign-in has calmer buttons and a tidier card, and choosing a workspace shows each one with its initials and your role, with a way to switch accounts.
Ask for a tool we do not connect yet. Every list on Connections ends with a Missing a tool card. Name the tool, its website, and what you would want from it, and it comes straight to us. A search that finds nothing fills in the name for you.
Switch properties from the top bar on phones. The phone's top bar centers the LopeBase logo and has the property switcher on the left, showing the property's icon.
Overview analytics grouped by property. Like Analytics, a property with more than one source shows its own row with each source under it.
SEO fits on phones. Long searches wrap inside their tags instead of pushing the page sideways, article ideas put Write this under the title, and search opportunity buttons stay inside their card.
Install LopeBase as an app. Add it to your phone's home screen or your computer's dock and it opens in its own window, with its icon and shortcuts to SEO, Analytics, Revenue, and Uptime. When you lose your connection it says you are offline instead of showing a browser error.
Analytics grouped by property. On Analytics, a property with more than one source shows its own row with each source under it, marked with the service's logo. A property with one source names it under the property's name.
Overview's to-do list as a queue. What needs a look sits in one queue, failing first, then reviews waiting, then things to watch. A long one stacks under the top item with a count, and Show all lists the rest. Next moves the top item to the back, and Dismiss hides one you are done with until it changes or a week passes.
Bing connects through busy moments. When Bing limits requests from LopeBase's servers, connecting and checking Bing wait and try again, and if it lasts, say so plainly instead of showing an error code.
Charts tell properties apart. Charts with a line per property use eight distinct colors chosen to stay apart for color-blind readers too, and each property keeps its color on every chart, so Moxie is the same color on Analytics and Uptime.
A fuller Uptime card. On a property's page, the Uptime card shows the last day's response times as a full-width chart under its status, instead of a small line in the corner.
Numbers that stay put. Overview no longer shows n/a for a number like MRR for a moment. When your app answers once without the number, the last one is kept and noted as a failed refresh, and a brief database hiccup shows the number already on hand instead of none.
AI buttons stay put, and say what they used. Review, audit, and other AI buttons keep their place while they run: the steps show under the section's heading instead of beside the button. When a review finishes, the line under its button shows a tick and the credits it actually used for a few seconds.
Weekly summary by property. In Settings, the weekly summary lists your properties with their icons instead of every connection. A property you pick brings everything connected to it, including what you connect later.
Your agent's to-dos tidy themselves. A step your coding agent left for you, like creating a PostHog key, closes on its own once that service is connected for the property, and steps left open for a month close too. Clear all empties the rest in one go, and your agent sees the change next time it checks.
A connection's data on its own page. Opening a connection, like a property's GitHub, now shows what it reads right there: summaries as a row of numbers and lists as their latest rows, with See all for the full list, instead of a card to click for each.
The LopeBase Adapter, by name. The piece your coding agent adds to your app, which sends its users, signups, revenue, and content, is now called the LopeBase Adapter everywhere, including when you pick a dashboard's data.
Every connector on the connectors page. Plausible, Cloudflare Web Analytics, Supabase, Brex, Rho, and Wise now each have a page saying what LopeBase reads and how to connect them.
October 2, 2026 No more false alarms on Connections. Connections are checked a few at a time, and one that does not answer is tried again before it shows as failing, so PostHog or Polar no longer turn red for a moment and then come back.
Bing lists your sites. Paste your Bing API key and pick the site from the ones verified on your account, or connect all your properties at once. A site address typed on its own now works, and a key Bing turns away says so.
Connect buttons let you pick your tool. Prompts to add search data, error tracking, builds, or a newsletter now open that group on Connections, so you choose the tool you use instead of being sent to one.
Apps under every group they fit. On Connections, GitHub also shows under Infrastructure for its builds and deploys, and Cloudflare and Supabase also show under Monitoring for their error rates and service health.
Connect GitHub in one click. Press Connect GitHub and install the LopeBase app on the repos you pick, instead of creating a token. Each property's repo is matched by name and site, with a dropdown to change any before it connects, and All my properties matches every property from one install. Install it on your own account and your organization's, and repos from both are listed together. Blog posts sent to GitHub open their pull requests through the same app, so there is no write token to keep either.
See which way traffic is heading. On Analytics, each property's weekly pageviews carry a small tag: up, down, or steady. It compares the last 6 full days with the 6 before, so a half-finished today never reads as a drop.
One Resend account for every property. Each property's Resend connection now counts only the emails sent from its own domain, so bounce and complaint rates read apart. Connecting lists your Resend domains with each property's matched by its site, and All my properties sets them all with one key. Connections made before keep reading the whole account until you add a domain.
See which properties each app covers. On Connections, each app shows the icons of the properties it is connected for, with their names on hover, instead of just Connected.
Quicker feedback when connecting several properties. Connect 3 properties now says Connecting the moment you click it, and each property shows its spinner while it is checked, instead of a pause before anything moved.
Connector status, without false alarms. Connections opens on Connector status: each property's tools, checked live as the page opens and red only when one does not answer or stops refreshing. A LopeBase connector that simply does not report a number, like MRR, no longer shows as failing. The separate row of connected pills is gone, and your app's connection is called the LopeBase connector everywhere.
Connect every property at once. For PostHog, Sentry, GitHub, and Supabase, pick All my properties, paste one key, and each property is matched to its project by name and site. Change any match or skip it, then connect them together. No project IDs to look up, for one property or all of them.
One key for all your properties. PostHog, Google Analytics, Search Console, Plausible, Cloudflare Web Analytics, Sentry, Supabase, Bing, and GitHub reuse the key you saved for one property when you connect the next, so you only pick its project, site, or repo. PostHog, Sentry, GitHub, and Supabase list what your key can see with the best match picked, and after one property connects you can connect the rest in one go.
Connections at a glance. Is your data arriving is now a card per property: its tools as logos with a dot for whether each is working, one-click buttons for the key tools it does not have yet, and the details a click away. The whole section folds away.
Brex, Rho, and Wise. Connect them with a read-only token for their balances, money in and out over 30 days, and recent transactions. Cash on Revenue and Overview adds up every bank you connect, and money in another currency is listed beside it, never added in.
A shorter sidebar. The list of properties with app data is gone from the sidebar, since it left out properties without it. Pick a property with the switcher at the top, or open Properties.
Amounts in their own currency. Mercury transactions and balances, Stripe and Polar payments, and subscription values show with their currency symbol, like $1,234.50 or €12.00, instead of a bare number.
More warnings on Overview. Now lists a GitHub workflow whose latest run on your main branch failed, a busy Cloudflare Worker failing 5% or more of its requests, and Resend email whose bounces or spam complaints are near or over Resend's own limits, where it can pause sending.
What happened, by day. Each property's page has a 30-day timeline: failed builds and deploys from GitHub, outages, error spikes from Sentry, days traffic swung well above or below its usual, and articles published, so a drop sits next to what shipped that day.
Cash beside revenue. With Mercury connected, Revenue shows cash in the bank, money in and out over 30 days, and runway at the last 30 days' pace, and Overview shows cash next to MRR.
See whether your data is arriving. Connections lists each connection with when its numbers last refreshed and the last error, failing ones first. If one stops, Overview says so, and Overview, Revenue, and Analytics say when their numbers were last updated, so old numbers never pass as current.
Build your own pipelines. On Pipelines, New pipeline lets you chain steps like writing an article, auditing the site, finding topic ideas, finding customers who are leaving, or writing anything with AI, with a check by you wherever you want one. Any template can be copied and changed. Each pipeline shows its steps as a flow, with its cost before you run it, and recent runs show how far each one got.
Fold away the weekly briefing. The weekly briefing and the revenue, traffic, and incident reviews collapse to their title with the arrow beside them, and stay that way in your browser until you open them again.
A property's data page shows its numbers. Opening a property's own app data (Browse data) now starts with its analytics, search, revenue, users, and uptime, each with its latest number or a button to connect it, plus daily charts of pageviews and search clicks. The property page has the same charts.
No false alarm for a shared company site. A Stripe account that lists your company website but goes by the property's name (its business name, display name, or statement descriptor) no longer warns that it belongs to another property.
The wrong-property warning stays in Manage. After It is right hides the Revenue banner, opening that Stripe or Polar connection's Manage still says whose account it is, with one click to move it to the property it matches.
Better on phones. The theme button opens again. Tables swipe sideways in their frame instead of squeezing every column, and page buttons and filters swipe instead of widening the page. The top bar and tab bar float as rounded bars, the audit date fields say From and To, and SEO suggestions and AI next steps put their buttons under the text.
More opens quickly on phones. The full menu behind More is ready before you tap it and slides up in a third of a second, instead of rebuilding the whole page each time.
Tidier copy buttons and tables. Copy prompt, Copy emails, and every other copy button keep their icon and label on one line with the same padding as other buttons. Tables have the same header band as the property lists.
A weekly briefing. On Overview, one button reads every product's numbers against last week, uptime, and what needs you, then says what changed and what to do this week.
Revenue review. On Revenue, a read of MRR, cancellations, past-due subscriptions, and failed payments, with what is at risk and what to do about it. Customer names and emails are never sent.
Traffic review. On Analytics, what is driving visits, what is slipping against last week, and which pages to work on, from your analytics, search clicks, and signups.
Incident review. On Uptime, what went wrong in the last 30 days and what to fix first, with your top Sentry errors when it is connected. After downtime it drafts a status note for your customers.
Share an article. On any article, a post for X, one for LinkedIn, a newsletter blurb, and a community post in your product's voice, each with a copy button.
Content has its own page. Articles, the review queue, and each product's autopilot moved out of SEO into Content in the sidebar. Old links still land there.
Edit live EmDash posts. Updating a published article now changes the same post on your EmDash 1.x site. LopeBase checks EmDash's revision first, so it never overwrites an edit made there.
Drafts fix themselves first. When a draft fails a check, the writer fixes what failed and it is checked again, up to the number of rounds you set, before it reaches you.
Stricter checks. The editor check now also flags writing that sounds machine-made and claims that look invented. A new check catches broken Markdown: unclosed code blocks, empty sections, and links with no address.
Your look for images. Pick how many images each article gets, their shape, and describe the look you want. Images never carry text or logos.
Choose whether articles link other sites. Turn it off and articles cite only your own posts, with a check that holds any outside link for review.
Email when an article needs you. LopeBase emails you when a draft is ready to approve or something fails, and optionally when an article goes live. Pick the addresses per product, or leave it to every admin.
See what articles will cost. Content setup shows the credits per article and per month on your schedule, updating as you change length, images, or revision rounds. Write one now shows the estimate too.
Publish to your CMS. Articles can now go straight to WordPress, Ghost, Webflow, Shopify, Contentful, Sanity, Strapi, or Hashnode, with a connection test before anything publishes. Editing a published article updates the same post there.
Let LopeBase host your blog. Pick Host it for me and each product gets a blog with nothing to set up: pages in your colors and type, RSS, a sitemap, and a JSON feed your own site can show. It is the default for new products.
Overview stays on every property. Opening one property's page no longer narrows Overview to it. Only picking a property in the sidebar does, and a focused Overview has a Show all properties button.
See when the sidebar scrolls. On shorter screens the sidebar fades at the edge when there are more items above or below.
A cleaner sign-in page, and faster. Sign-in and signup load without waiting on your workspace data, and wide screens show what LopeBase does beside the form. Overview loads its numbers side by side, so switching properties is quicker.
One place to switch properties. SEO, Analytics, Revenue, Uptime, and Content no longer have their own property row; the switcher at the top of the sidebar changes the page you are on.
Settings in tabs. Email, AI credits, Agent access, and Your data each have their own tab, and the address keeps your place.
An Agent setup guide. A new page in the account menu explains the CLI, the MCP server, and the adapter: why each helps and how to set it up, with commands to copy.
Your blog, as a grid. On Content, your posts show as cards with pictures and tags from your feed, with search, tag filters, sorting, and a Write a new article card. More load as you scroll.
Copy a prompt for your coding agent. Next steps in every AI review, each page in the SEO audit, and each search opportunity have a Copy prompt button. It gives your agent the task, what LopeBase found, and how to know it is done.
Better article emails. Ready for review, published, and failed emails now look like LopeBase: the article's title, summary, first lines, and picture, which checks need a look, and one button to review it.
Spot your CMS at a glance. Content setup shows each CMS by its logo, and the GitHub option uses GitHub's mark.
Clear on and off switches. The content schedule and the weekly summary email each have one switch at the top. When it is off, everything under it is greyed out.
Drafts get closer on the first try. When a draft runs short or misses links to your posts, the fix round now gets the word count it needs and your post list. Links to posts on a blog subdomain count as your own.
Reject looks like reject. Reject, remove, and disconnect buttons share one red tint across the app. Copy as Markdown moved off the review step and shows once an article is live.
Better AI models, matched to the job. Articles, editor checks, and reviews now use a stronger model, and simple data steps use a fast, cheap one. Credit estimates count the thinking these models do, and what you are charged still comes from what each call actually used, with cached input at its lower price.
Catches a key on the wrong property. When you connect Stripe or Polar to a property, LopeBase checks whose account it is. If its website or business name is another property's, it says so before saving, with one click to connect it there instead. Connections made before now show the same warning on Revenue, with Move it and It is right.
One property, shown in full. With a property picked in the sidebar, Revenue lists its subscriptions (failed payments and cancellations first) instead of a one-row table, and Overview shows its numbers directly.
Connect revenue from one list. Connect buttons for revenue open the list of billing tools to choose from. Changing or removing a connection's key clears its saved totals, so a new account never shows the old one's numbers.
Pipelines that do real work. Start from four templates: write, review, and publish an article; an SEO checkup that then writes the top fix; plan next month's articles onto your calendar; and win back customers who are cancelling, with a drafted note to send. Each runs on its own, stops for your OK where it matters, and shows its credit cost before you start.
A Users page. See who uses each property in one list: your app's users, paying customers from Stripe or Polar, and newsletter subscribers from Sequenzy, matched by email. Above it, what to act on: failed payments, people cancelling, new signups this week, paying customers not on your newsletter, and subscribers who have not tried the product, each with their emails to copy.
The audit log records everything. Connecting and disconnecting apps, content settings, articles written, edited, rewritten, approved, rejected, and published (including by the schedule), SEO audits and reviews, tracked keywords and competitors, AI reports, and email settings now all show in Audit, in plain words. With a property picked in the sidebar, it shows that property's events and workspace-wide ones.
Setup links that go to the right place. The Sequenzy connect guide opens your Sequenzy dashboard, and the Ghost, Shopify, Webflow, Sanity, Resend, and PostHog guides link to their current pages. Every key field also says what to paste in it.
Clearer buttons and tips. Copy prompt buttons look like buttons, hover tips across the app use one consistent style that also shows on keyboard focus, and the credit cost frame stands out on gray cards too.
Improve a draft with AI. On an article waiting for review, Improve with AI fixes the checks that failed, or rewrites it from your notes, like "shorter, with a worked example". The checks run again after, and each option shows its credit cost first.
The credits bar shows small use. On Billing, the bar for included credits stayed empty until you had used a full percent. It now shows any use, and says how many are used and how many are left.
AI credit pricing. Each AI call now costs its provider price plus 35%, up from 30%, so an article costs about a credit more. Estimates in the app already include it.
Let AI set up your blog. After you pick where articles go, one button reads your site and blog, fills in your voice, picks keywords and topics, sets a schedule that matches your pace, and writes a first article, showing each step as it works. You end on a summary with the article ready to review.
Content setup remembers you are done. Once a product is set up, its content page opens on what is coming, recent articles, and Write one now, with each part of the setup a card you can edit.
AI help on every step. Fill in your voice from your site and pick keywords from your site, blog, and Search Console, each with its credit cost shown under the button.
First drafts that pass. Setup's first article keeps getting fixed until every check passes, so it is ready when you see it.
A cleaner review page. The article fills the page. Checks fold into one button that says whether all pass, and the actions sit in a bar above the article.
Every AI button shows its cost. The SEO audit, the AI review, reports, and writing an article share one button style with the estimate underneath and a note on how it is worked out.
One click to the next step. Wherever LopeBase says to connect a service, add an AI key, run the SEO audit, or add a site address, there is now a button or link that takes you straight there.
No model names. Articles and AI reviews no longer show which AI model wrote them.
October 1, 2026 Start from your terminal. Run npx lopebase in a product's folder. Sign in or create an account in the browser, and your coding agent does the rest of the setup.
Connect Google Analytics with Google. The same one-click, read-only Google sign-in Search Console uses. Pick the GA4 property for each product.
Plausible and Cloudflare Web Analytics. Two more traffic sources, shown on Analytics and Overview next to PostHog and GA4.
See where AI credits went. Each AI task, like an article or an SEO audit, shows what it cost and links to what it made. A Usage page covers the last 90 days.
Credits in the sidebar. Your AI credit balance is always in view, with a bar of how much is left this month and a warning when it runs low.
A guided start for new products. A product with nothing connected shows the tools it can use, each one click away.
Pick your analytics tool. Connect analytics now opens Connections filtered to analytics tools, set to that product. Connected apps also stay in the full list, so a search or filter finds them.
Uptime comes with the adapter. Connecting the LopeBase adapter now checks its health endpoint on the uptime schedule, unless that product already has a check.
Operators list fixes. Teammates who have signed in no longer show as invite pending, and the role menu reads Admin, Support, Viewer.
Honest dashboard counts. Each dashboard counts only the sources that fill it, so Revenue no longer says Live when nothing reports revenue.
A clearer way to build a dashboard. New dashboard sits at the top of the page and walks you through picking the data, the charts and their order, then a name.
Workspace changes in the audit log. Connecting or removing an app or property, inviting or changing a teammate, dashboards, and agent access now show on the Audit page under Workspace.
A property page that shows its numbers. Analytics, Search, Revenue, App data, Blog, and Uptime are cards with the latest number and trend. Click one to open it, or connect it from the card.
A clearer SEO audit. While it runs you see each step it is on. The result opens with totals, then each page with what to fix first, and the competitors it found.
A tidier SEO page. Overview now covers search only, in three parts: performance, what to do next, and top searches. The SEO audit moved to the Health tab.
The SEO audit tidies your keywords. It stops tracking searches that are not worth it, like unrelated or spam terms, and lists each one with why. Track any of them again from the Keywords tab.
Faster pages. Numbers are stored as they refresh, so pages open without waiting on each service.
Deleting a workspace deletes everything. Uptime history, SEO data, and digest settings now go with it.
September 30, 2026 Content autopilot. Each product gets its own content plan: topics from Search Console and search suggestions, drafts in your voice, automatic checks, and review or autopilot mode on a schedule. Publishes to EmDash, a GitHub pull request, or a signed webhook.
Article results. Clicks, impressions, and position from Search Console for every published article, and an IndexNow ping on publish.
AI credits. Every plan includes a monthly allowance of AI credits, with packs of 2,000 for $20 when you need more. Or bring your own key and use none.
Sign in with Google, GitHub, or an email link. Name your workspace after you sign in, and switch between workspaces from one place.
Products screen. Each product now has one place for all of its connections: its own adapter, analytics, search, errors, and revenue.
LopeBase MCP server. Connect an AI agent and let it help set up products and connectors.
A guided blog per product. Set up an EmDash blog for a product step by step, in your own Cloudflare account.
Pick when the weekly summary arrives. Choose the day and time for your weekly email.
Content calendar. Drafts are written days ahead of their date, and edits after publishing reach your site at the same address.
Connect Search Console with Google. Sign in with Google in one click, read-only, and pick each product's property.
Uptime page. Every site is checked every 15 minutes, with 30 days of history and every outage.
SEO toolkit. A one-button audit that shows its credit cost first, tabs for health, keywords, and links, free Domain Rating, and an AI review of pages people see in search but skip.
Supabase. Project health, advisors, disk, and backups for each product's Supabase project, read-only.
Signed admin adapter. Requests from LopeBase are signed, and you choose what personal data reaches LopeBase.
One Connections page. Every tool, for every product, in one place, with a step-by-step connect dialog.
September 29, 2026 Weekly summary email. A short digest of what changed across your products, with settings for each operator.
14 days of Portfolio for new workspaces. Every new workspace starts with the Portfolio plan for 14 days, then moves to Free unless you choose a plan. No card needed.
Referral program. Invite other people who run products, right from your workspace.
Faster sign-in. One-click sign-up and sign-in, with each sign-in taken straight to its workspace.
Export and delete your data yourself. Download everything in your workspace, or delete it, from Settings.
Billing through Polar. Polar handles checkout, sales tax, and VAT.
A phone layout that feels native. Bottom tabs, a sheet for everything else, and touch-friendly controls.
A cleaner console. One surface and button system across every screen, a verified connect flow, and Settings in the sidebar.
September 28, 2026 Content studio. Draft posts with AI, filter by status, and publish across products.
EmDash connector and SEO pipeline. Draft from target keywords, review, publish to EmDash, and ping search engines.
Search insights. A search dashboard built on Search Console data.
Color themes. Five palettes in light and dark, with the frosted sidebar.
Encrypted AI keys. Bring your own AI provider key, stored encrypted.
August 27, 2026 The first version. The engine behind LopeBase, the admin adapter kit for connecting your own product, and the first live product connected end to end.

---

## Compare

URL: https://lopebase.com/compare

How LopeBase compares with Retool, Databox, Geckoboard, Baremetrics, ChartMogul, ProfitWell, and more, plus head-to-head tool comparisons.

How LopeBase compares.
LopeBase is an ops console: growth, revenue, uptime, and SEO for every product you run, read from the tools you already use. Here is where it fits next to other options, including when the other option is the better call. Every comparison is based on the other product's own pages, and notes the month we checked them.
Internal tool and admin panel builders
These build screens on your own database, so your team can find and change records. LopeBase never connects to your database; it reads the tools each product uses. Many teams use one of these and LopeBase side by side.
vs Retool Build internal apps on your data, or open a ready ops console.vs Forest Admin An admin panel on your database, or a view of your tools. Dashboards and reporting
General dashboard tools connect to almost anything and leave the screens to you. LopeBase is made for one job, running several SaaS products, so the screens, checks, and alerts already exist.
vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs AgencyAnalytics Client marketing reports, or ops for products you run. Subscription revenue analytics
These go deep on subscription metrics like churn and segments, across many billing systems. LopeBase shows each product's MRR next to its traffic, uptime, errors, and SEO, so you can see why a number moved.
vs Baremetrics Deep subscription analytics, or revenue next to everything else.vs ChartMogul A revenue analytics platform, or a portfolio ops console.vs ProfitWell Metrics Free subscription metrics, or a whole view of each product. Head to head
Choosing between two of these tools? These compare them with each other, from each company's own pricing page, and say who each one suits.
Baremetrics vs ChartMogul Two subscription analytics tools, side by side.ChartMogul vs ProfitWell Paid revenue analytics against a free one.Databox vs Geckoboard Two KPI dashboard tools, and who each suits.Retool vs Forest Build your own admin, or generate one from your database. Building your own
The most common alternative is no tool at all: a tab per service per product, or a dashboard you wrote yourself. It works for one product and gets heavy with three.
vs building your own What stitching your own dashboards costs across products.Running several products How to run several SaaS products without building an admin for each.Tools for running several products The tools founders use to run several SaaS products, and where each one falls short. Questions
Something else? Contact us.
01Who is LopeBase for?
Founders, indie hackers, and small studios who run more than one SaaS product and want growth, revenue, uptime, and SEO for all of them in one place.
02Does LopeBase replace my analytics or billing tools?
No. It reads them. Keep Stripe, PostHog, Search Console, and the rest; LopeBase puts their numbers side by side for every product.
03How are these comparisons kept honest?
Each one describes the other product from its own website and pricing page, links to them, and notes the month we checked. If something is out of date, email us and we will fix it.
04Can I try LopeBase before paying?
Yes. LopeBase is free for one product with no time limit, and a new workspace gets 14 days of the Portfolio plan. Neither needs a card.

---

## vs AgencyAnalytics

URL: https://lopebase.com/compare/agencyanalytics

LopeBase vs AgencyAnalytics. AgencyAnalytics automates marketing reports for agency clients. LopeBase is an ops console for products you run yourself.

All comparisons LopeBase vs AgencyAnalytics
AgencyAnalytics is built for marketing agencies: white-labeled reports and a client portal across SEO, PPC, social, and email data, priced per client. LopeBase is built for the people running the products, not reporting on them. It watches revenue, uptime, errors, and search for each product, and tells you what needs fixing. If you are a studio that builds and runs its own SaaS products, LopeBase is the closer fit. If you report marketing results to clients, AgencyAnalytics is.
Side by side
TopicAgencyAnalytics LopeBaseMade forMarketing agencies reporting to clients.Founders and studios running their own SaaS products.Pricing unitPer client: $20 a month each on annual billing.Per product, with plans from free to unlimited.Integrations85+ marketing integrations: SEO, PPC, social, email, call tracking, local, and ecommerce.Billing, product analytics, search, errors, uptime, email delivery, hosting, and banking.RevenueEcommerce sources like Shopify. Stripe is not in its integrations list.MRR, one-time revenue, and past-due payments from Stripe or Polar, per product.Uptime and errorsNot covered.Uptime every 15 minutes, Sentry errors, and failing builds.Client viewWhite-labeled portal and automated client reports.Workspaces with operators and per-property access, not client-branded.Best whenYou send monthly marketing reports to clients.You run the products and need to know which one needs you. Based on how each product describes itself, checked October 2026. Sources: AgencyAnalytics pricing, AgencyAnalytics integrations. If something here is out of date, tell us and we will fix it.
How the pricing compares
AgencyAnalytics' pricing page, checked October 2026, lists one Core plan at $20 per client a month on annual billing, with unlimited data sources, reports, dashboards, and staff accounts, 85+ integrations, a white-labeled portal, and goals and alerts. Rank tracking and an AI tracker are paid add-ons. There is a free 14 day trial with no card, and volume pricing from 25 clients.
Per-client pricing suits agencies, where each client pays its own way. For a studio running its own products, the closer comparison is per product: ten products would be $200 a month on AgencyAnalytics before add-ons.
LopeBase counts products. Free for one product with no time limit. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats, and a new workspace gets 14 days of Portfolio with no card.
Where each one is stronger
Where AgencyAnalytics is stronger
Client reportingWhite-labeled reports and a portal that clients log into, with automated sends.
Marketing breadthPPC, social, call tracking, local listings, and email marketing, well beyond what LopeBase reads.
Rank trackingKeyword rank tracking as an add-on, sized for agency client lists.
Unlimited staffEvery staff account is included.
Where LopeBase is stronger
Revenue and product healthMRR, signups, active users, uptime, and errors per product, which marketing reporting tools leave out.
Checks that alert youA site down, a failing build, or payments past due reaches you by email or browser.
SEO you can act onIndexing checks and a content autopilot that drafts articles for searches on page two.
Your own app's numbersThe LopeBase Adapter reads your own users and signups, without database access.
The overlap is search: both read Search Console and Bing. Past that they answer different questions. AgencyAnalytics proves marketing results to someone else. LopeBase helps you run the product.
Which one to pick
Pick AgencyAnalytics if
You are a marketing agency that reports SEO, ads, and social results to clients each month and wants it white-labeled.
Pick LopeBase if
You build and run your own SaaS products and need their revenue, uptime, errors, and search in one place, more than client-ready marketing reports.
Start free Questions
Something else? Contact us.
01Can an agency use LopeBase?
Yes, if the agency builds or runs SaaS products. The Agency plan has no limit on products or operators. It is not a white-labeled client reporting tool.
02Does LopeBase do rank tracking?
It tracks the searches you choose from Search Console and Bing, with positions over time. It does not run its own rank checks the way a dedicated rank tracker does.
03Does AgencyAnalytics read Stripe?
Stripe was not in its integrations list when we checked in October 2026. It covers ecommerce sources like Shopify.
vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Baremetrics Deep subscription analytics, or revenue next to everything else.

---

## vs Baremetrics

URL: https://lopebase.com/compare/baremetrics

LopeBase vs Baremetrics. Baremetrics is deep subscription analytics. LopeBase puts MRR next to traffic, uptime, errors, and SEO for every product you run.

All comparisons LopeBase vs Baremetrics
Baremetrics is subscription analytics: MRR, churn, trial insights, segmentation, benchmarks, and forecasting, with add-ons for failed-payment recovery and cancellation insights. LopeBase covers revenue too, but as one part of a wider console. It shows MRR for every product next to traffic, uptime, errors, and SEO, so you can see why a number moved.
Side by side
TopicBaremetrics LopeBase What it isSubscription analytics for a business.An ops console for a portfolio of SaaS products.Revenue depthMRR, churn, retention, segmentation, benchmarks, forecasting.MRR, subscriptions, 30-day gross, net, and one-time revenue, recent charges, past-due subscriptions.Billing sourcesStripe, Braintree, Chargebee, Recurly, Shopify, App Store, Google Play, and more.Stripe and Polar, any number of accounts.Bank cashQuickBooks and Xero integrations.Mercury, Brex, Rho, and Wise balances next to revenue.Everything elseRevenue focused.Analytics, Search Console, Bing, Sentry, uptime, GitHub, Cloudflare, Supabase, and email delivery.Payment recoveryPaid add-on.Not offered. Past-due subscriptions show under needs attention.Pricing modelBy ARR band.By number of products.Best whenSubscription metrics are the main thing you study.You want each product's revenue in the context of everything else. Based on how each product describes itself, checked October 2026. Sources: Baremetrics pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
Baremetrics prices by revenue. Its pricing page, checked October 2026, lists Launch at $75 a month for up to $360K ARR with a single integration, Growth at $255 a month for $360K to $3.6M ARR with two integrations, and Scale at $1,152 a month above that. Annual billing takes up to 35% off. Payment recovery and cancellation insights are $129 a month each.
LopeBase prices by products, not revenue. Free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats.
Because Baremetrics pricing rises with ARR, a portfolio that grows moves up bands. LopeBase pricing only changes when you add products.
Where each one is stronger
Where Baremetrics is stronger
Subscription depthChurn, retention, trial insights, segmentation, benchmarks, and forecasting.
Many billing systemsStripe, Braintree, Chargebee, Recurly, Shopify, and the app stores.
Recovery toolsFailed-payment recovery and cancellation insights as add-ons.
Finance planningScenario planning and expense tracking on the Scale plan.
Where LopeBase is stronger
The whole pictureMRR beside traffic, signups, uptime, errors, and SEO, so a dip has context.
Many productsEvery product on its own row, with totals across Stripe and Polar accounts.
Cash in the bankMercury, Brex, Rho, and Wise balances next to what you earn.
Not priced on revenueThe price stays the same as revenue grows.
If subscription analytics is a daily job for you, Baremetrics goes deeper than LopeBase on revenue, and the two can sit side by side. If you mostly need to know what each product earns and whether anything is wrong, LopeBase covers that along with everything else you would otherwise check in separate tabs.
Which one to pick
Pick Baremetrics if
Revenue analytics is the center of your week: churn, segments, forecasting, and recovering failed payments.
Pick LopeBase if
You run several products and want MRR for each next to its traffic, uptime, errors, and SEO, on one screen.
Start free Questions
Something else? Contact us.
01Does LopeBase track churn?
Not today. LopeBase shows MRR, active subscriptions, 30-day gross, net, and one-time revenue, recent charges, and past-due subscriptions. For churn and retention analysis, a tool like Baremetrics goes further.
02Can LopeBase combine several Stripe accounts?
Yes. Add a restricted read-only key for each account. Each product keeps its own row and Overview shows the combined MRR.
03Does LopeBase support Paddle or Chargebee?
Not today. LopeBase reads Stripe and Polar. Your own app can also report revenue through the LopeBase Adapter.
Baremetrics vs ChartMogul Two subscription analytics tools, side by side.vs ChartMogul A revenue analytics platform, or a portfolio ops console.vs ProfitWell Metrics Free subscription metrics, or a whole view of each product.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Databox A general KPI dashboard, or a console made for SaaS products.

---

## Baremetrics vs ChartMogul

URL: https://lopebase.com/compare/baremetrics-vs-chartmogul

Baremetrics vs ChartMogul, compared on pricing, billing sources, and features, from each company's own pricing page in October 2026.

All comparisons Baremetrics vs ChartMogul
Baremetrics and ChartMogul both turn your billing data into subscription metrics: MRR, churn, lifetime value, and segments. They differ most in how they price, how many billing systems they combine, and what they sell on top. Here is how they compare, using each company's own pricing page as of October 2026.
Side by side
TopicBaremetricsChartMogulFree planNo. A free trial.Yes, up to $10K MRR with one billing source.How price is setBands by ARR: up to $360K, $360K to $3.6M, then above.Scales with ARR tracked in ChartMogul.Entry price$75 a month, or $49 on annual billing.Starter from $69 a month, or $57 on annual billing.Billing systems1 on Launch, 2 on Growth, unlimited on Scale.1 on Free and Starter, 5 on Pro.Team membersNot stated on the pricing page.Up to 3 on Starter, unlimited on Pro.Recovering revenuePayment Recovery and Cancellation Insights add-ons, $129 a month each.Not sold as an add-on; CRM sync and data warehouse push on Pro.PlanningScenario planning and budget tracking on Scale.Enterprise adds BI workflows and expert support. Based on how each product describes itself, checked October 2026. Sources: Baremetrics pricing, ChartMogul pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
ChartMogul has the cheaper start. Its Free plan covers up to $10K MRR, and Starter begins at $69 a month ($57 annual). Pro, which you need to combine more than one billing system, begins at $119 a month ($99 annual). Both paid plans rise as your ARR grows, and Enterprise starts at $19,900 a year.
Baremetrics has no free plan. Launch is $75 a month ($49 annual) up to $360K ARR with one integration, Growth is $255 ($189 annual) up to $3.6M with two, and Scale is $1,152 ($749 annual) beyond that. Payment Recovery and Cancellation Insights cost $129 a month each on top.
For a company under $10K MRR on one Stripe account, ChartMogul costs nothing and Baremetrics costs at least $49 a month. Once you add dunning, Baremetrics' add-on is part of the price; with ChartMogul you would bring a separate tool for it.
Where each one is stronger
Where Baremetrics is stronger
Recovery built inPayment Recovery for failed charges and Cancellation Insights for why people leave, sold by the same company.
Simple bandsThree price bands by ARR, easy to predict.
Planning toolsScenario planning and budget and expense tracking on Scale.
Slack and IntercomBoth on Growth and up, for sharing numbers where the team already is.
Where ChartMogul is stronger
Free to startFree up to $10K MRR, which covers most products in their first year or two.
Several billing systemsPro combines up to 5 billing sources, including Paddle and Xero through a partner.
CRM and warehouseTwo-way CRM sync and data warehouse push on Pro.
Startup discount$50 a month off for 12 months for eligible early-stage companies.
Both are serious subscription analytics tools, and neither is a bad pick. The cleaner split is what you want around the metrics: Baremetrics bundles revenue recovery, ChartMogul leans toward connecting revenue data to the rest of your stack.
Which one to pick
Pick Baremetrics if
You want subscription metrics and failed payment recovery from one vendor, and prefer simple price bands.
Pick ChartMogul if
You are under $10K MRR and want it free, or you need several billing systems combined with CRM sync.
If you run several products
Both tools go deep on one thing, subscription revenue. If you run several SaaS products, revenue is only part of what you check each morning: is each site up, are people finding it, did a build break, is email delivering.
LopeBase reads Stripe or Polar for each product and puts MRR next to traffic, signups, uptime, errors, and search, for every product on one page. It does not replace Baremetrics or ChartMogul for cohort analysis. It is free for one product.
See what LopeBase does
Questions
Something else? Contact us.
01Is Baremetrics or ChartMogul cheaper?
Under $10K MRR on one billing source, ChartMogul is free and Baremetrics starts at $49 a month on annual billing. Above that, both rise with ARR, so compare at your own revenue on each pricing page.
02Which one handles several Stripe accounts?
Baremetrics allows 2 integrations on Growth and unlimited on Scale. ChartMogul allows 5 billing sources on Pro.
03Does either include dunning?
Baremetrics sells Payment Recovery as a $129 a month add-on. ChartMogul does not list one on its pricing page.
vs Baremetrics Deep subscription analytics, or revenue next to everything else.vs ChartMogul A revenue analytics platform, or a portfolio ops console.ChartMogul vs ProfitWell Paid revenue analytics against a free one.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Databox A general KPI dashboard, or a console made for SaaS products.

---

## vs building your own

URL: https://lopebase.com/compare/build-your-own

LopeBase vs building your own dashboards for each product: what it takes to stitch Stripe, analytics, Search Console, and uptime together, and when to.

All comparisons LopeBase vs building your own
Most people who run a few small products check Stripe, then PostHog, then Search Console, then an uptime tool, once for each product. Some build a dashboard to pull it together. That works for one product. With three, you maintain three, and the SEO work still happens somewhere else.
Side by side
TopicYour own LopeBase SetupAPI code, charts, and a login for each product.One console. Connect each tool once per product.Daily checkA tab per tool per product.One Overview with totals and a row per product.CredentialsKeys in each app's environment, with whatever access you gave them.Read-only keys, stored encrypted, with a guide for the narrowest permissions.UptimeAnother service to sign up for and watch.Checked every 15 minutes, with 30 days of history.SEOSearch Console in one tab, ideas in a doc.Indexing, keywords, Domain Rating, competitor watch, and checked articles.AlertsSomething you wire up per check.Needs attention, by email or push, with thresholds built in.Audit trailUsually none.Every operator action, with the exact before and after.UpkeepYours to fix when an API changes.Ours to fix. You keep working on the product.Best whenYou need a chart no general tool will ever have.You want the overview handled so you can work on the products. Based on how each product describes itself, checked October 2026. If something here is out of date, tell us and we will fix it.
What it costs
Building your own looks free, and for one product it often is. The cost is time: an API client per tool, charts, a login, somewhere to host it, and fixes each time a provider changes an API or deprecates a version. Multiply that by each product, or generalize it, which is how most internal dashboards grow into a product of their own.
LopeBase is free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats.
Where each one is stronger
Where building your own is stronger
Exactly your chartA report so specific to one product that no general tool will ever have it.
Full controlYour code, your hosting, your data model.
No vendorNothing to sign up for, and nothing to stop paying for.
Where LopeBase is stronger
Connect, don't codeRead-only keys or one-click sign-in, and the numbers show up.
Every product at onceOne Overview with totals and a row per product.
Checks you would not buildPast-due subscriptions, bounce rates near Resend's limit, failing builds, Worker error rates, Supabase advisors.
No upkeepWhen an API changes, we fix the connector.
It does not have to be one or the other. Build the one view that only your product needs, and connect the rest of the product to LopeBase for the everyday numbers. Your app can even send its own records through the LopeBase Adapter.
Which one to pick
Build your own if
One product needs a very specific chart or report. Build that one view, and connect the rest to LopeBase.
Pick LopeBase if
You would rather connect each tool once than write and maintain dashboard code for every product you run.
Start free Questions
Something else? Contact us.
01Is it hard to move from my own dashboard?
No. LopeBase reads the same tools your dashboard does. Connect them, and keep your dashboard running until you no longer open it.
02Can my own app send numbers to LopeBase?
Yes. The LopeBase Adapter is a small handler in your app that exposes the records, numbers, and actions you choose.
03Where are my keys kept?
Encrypted at rest in your workspace. Each connector's guide asks for the narrowest read-only permission the service offers.
vs Retool Build internal apps on your data, or open a ready ops console.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs Databox A general KPI dashboard, or a console made for SaaS products.vs Forest An admin panel on your database, or a view of your tools.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs AgencyAnalytics Client marketing reports, or ops for products you run.

---

## vs ChartMogul

URL: https://lopebase.com/compare/chartmogul

LopeBase vs ChartMogul. ChartMogul is a revenue analytics platform. LopeBase shows MRR next to traffic, uptime, errors, and SEO for every product.

All comparisons LopeBase vs ChartMogul
ChartMogul is a subscription analytics platform: MRR, ARR, churn, and customer data across many billing systems, with CRM sync and a free plan for small businesses. LopeBase covers revenue as one part of an ops console for several SaaS products, next to traffic, uptime, errors, and SEO.
Side by side
TopicChartMogul LopeBase What it isRevenue analytics and customer data.An ops console for a portfolio of SaaS products.Revenue depthMRR, ARR, churn, customer segments, CRM sync.MRR, subscriptions, 30-day gross, net, and one-time revenue, recent charges, past-due subscriptions.Billing sourcesStripe, Chargebee, Paddle, Recurly, Braintree, the app stores, and many more.Stripe and Polar, any number of accounts.Several billing accounts1 on Free and Starter, 5 on Pro, 15 on Enterprise.No limit per plan. Plans cap products.Everything elseRevenue and customer focused.Analytics, Search Console, Bing, Sentry, uptime, GitHub, Cloudflare, Supabase, email, and bank cash.Pricing modelBy MRR or ARR band.By number of products.Best whenRevenue analytics across complex billing.Each product's revenue in the context of everything else. Based on how each product describes itself, checked October 2026. Sources: ChartMogul pricing, ChartMogul integrations. If something here is out of date, tell us and we will fix it.
How the pricing compares
ChartMogul's pricing page, checked October 2026, lists a Free plan for up to $10K MRR with one billing source. Starter starts at $69 a month ($57 on annual billing) with one billing system plus two custom sources. Pro starts at $119 a month ($99 annual) and connects up to 5 billing sources in one view. Paid plans rise with revenue, and Enterprise starts at $19,900 a year.
That billing source count matters with several products. If each product has its own Stripe account, seeing them together on ChartMogul means Pro or above.
LopeBase counts products, not billing accounts. Free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats.
Where each one is stronger
Where ChartMogul is stronger
Billing coverageDozens of billing systems, from Stripe and Paddle to the app stores.
Revenue depthMRR, ARR, churn, and customer segments, which ChartMogul calls investor-grade SaaS metrics.
Customer dataCRM sync and a unified customer record.
Free planFree up to $10K MRR for one billing source.
Where LopeBase is stronger
The whole pictureMRR beside traffic, signups, uptime, errors, and SEO, so a dip has context.
Several accounts on every planConnect every product's Stripe or Polar account on any plan.
Cash in the bankMercury, Brex, Rho, and Wise balances next to revenue.
Growth workSEO checks, a content autopilot, and AI reviews of your numbers.
ChartMogul is the better pick for deep revenue analysis, especially across complicated billing. LopeBase is the better pick for running the products: knowing each morning what every product earned, whether it is up, and what needs fixing. Some founders use both.
Which one to pick
Pick ChartMogul if
You need investor-grade revenue analytics, churn work, or billing systems beyond Stripe and Polar.
Pick LopeBase if
You run several products, each with its own billing account, and want revenue next to everything else that tells you how a product is doing.
Start free Questions
Something else? Contact us.
01Is LopeBase a ChartMogul alternative?
For seeing MRR across several products next to their traffic, uptime, and SEO, yes. For deep subscription analytics, ChartMogul goes further.
02Can I connect several Stripe accounts on the Free plan?
The Free plan covers one product. Studio covers 3 products and Portfolio 10, and each product can bring its own Stripe or Polar account.
03Does LopeBase report churn?
Not today. It reports MRR, subscriptions, 30-day gross, net, and one-time revenue, and flags past-due subscriptions.
Baremetrics vs ChartMogul Two subscription analytics tools, side by side.ChartMogul vs ProfitWell Paid revenue analytics against a free one.vs ProfitWell Metrics Free subscription metrics, or a whole view of each product.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Databox A general KPI dashboard, or a console made for SaaS products.

---

## ChartMogul vs ProfitWell

URL: https://lopebase.com/compare/chartmogul-vs-profitwell

ChartMogul vs ProfitWell Metrics, compared on price, billing integrations, and depth, from each company's own pages in October 2026.

All comparisons ChartMogul vs ProfitWell
ProfitWell Metrics, now part of Paddle, gives subscription metrics away for free. ChartMogul is free up to $10K MRR and paid after that. So the real question is what ChartMogul's paid plans give you that free does not, and whether that matters at your size.
Side by side
TopicChartMogulProfitWellPriceFree to $10K MRR, then from $69 a month ($57 annual), rising with ARR.Free.Owned byIndependent.Paddle.Billing systemsStripe, Chargebee, and others; Paddle and Xero through a partner. 5 sources on Pro.Stripe, Chargebee, Braintree, Zuora, Recurly, Paddle, and others.Core metricsMRR, churn, cohorts, segments, and customer data.MRR, churn, upgrades and downgrades, lifetime value, cohorts, and segments.BenchmarksNot listed on the pricing page.Against 30,000+ SaaS companies, by Paddle's count.Other dataCustom sources, CRM sync, and data warehouse push.HubSpot, Zapier, Zendesk, and Intercom.Sold alongsideEnterprise BI workflows and support.Paddle's paid products, like Retain for churn. Based on how each product describes itself, checked October 2026. Sources: ChartMogul pricing, ProfitWell Metrics. If something here is out of date, tell us and we will fix it.
How the pricing compares
ProfitWell Metrics costs nothing at any revenue, according to Paddle's page in October 2026, and you do not need Paddle billing to use it.
ChartMogul is free to $10K MRR. Above that, Starter begins at $69 a month ($57 annual) with one billing source, and Pro at $119 ($99 annual) with up to five. Both scale with ARR. Enterprise starts at $19,900 a year.
So past $10K MRR, choosing ChartMogul means paying for what it adds: custom data sources, CRM sync both ways, warehouse export, and an independent vendor.
Where each one is stronger
Where ChartMogul is stronger
Your data, connectedCustom sources, two-way CRM sync, and data warehouse push on Pro.
IndependentNot tied to a billing provider, which some teams prefer for their revenue data.
Combining sourcesUp to 5 billing sources in one view on Pro.
Startup discount$50 a month off for 12 months for eligible early-stage companies.
Where ProfitWell is stronger
Free at any sizeNo revenue cap on the metrics.
BenchmarksSee how your churn and growth compare with other SaaS companies.
Broad billing supportBraintree, Zuora, and Recurly as well as Stripe and Chargebee.
Health signalsCustomer health scoring and at-risk alerts.
For most small SaaS companies, ProfitWell Metrics covers the numbers that matter at no cost. ChartMogul earns its price when revenue data has to flow into your CRM or warehouse, or when you would rather keep it with an independent vendor.
Which one to pick
Pick ChartMogul if
Your revenue data needs to reach your CRM or warehouse, you combine several billing systems, or you want an independent vendor.
Pick ProfitWell if
You want solid subscription metrics and benchmarks for free, on almost any billing system.
If you run several products
Neither tool looks past revenue. If you run several products, you also want to know whether each site is up, whether traffic and signups are moving, and whether a build or email provider is failing.
LopeBase puts each product's MRR from Stripe or Polar next to its traffic, signups, uptime, errors, and SEO, for every product at once. Many founders pair it with a dedicated revenue tool. It is free for one product.
See what LopeBase does
Questions
Something else? Contact us.
01Is ProfitWell still free?
Yes, as of October 2026, according to Paddle's ProfitWell Metrics page.
02Do I need Paddle to use ProfitWell Metrics?
No. Paddle's page says it works with Stripe, Chargebee, and other billing tools.
03When is ChartMogul worth paying for?
When revenue data has to sync with your CRM or warehouse, or you need several billing systems in one view. Under $10K MRR, it is free anyway.
vs ProfitWell Metrics Free subscription metrics, or a whole view of each product.vs ChartMogul A revenue analytics platform, or a portfolio ops console.Baremetrics vs ChartMogul Two subscription analytics tools, side by side.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Databox A general KPI dashboard, or a console made for SaaS products.

---

## vs Databox

URL: https://lopebase.com/compare/databox

LopeBase vs Databox. Databox is a general KPI dashboard for many kinds of business. LopeBase is an ops console made for running several SaaS products.

All comparisons LopeBase vs Databox
Databox is a business analytics platform: connect data from many tools, build dashboards and reports, and track goals. It serves agencies and businesses of every kind. LopeBase is narrower on purpose. It is an ops console for people who run several SaaS products, with the screens, checks, and alerts already set up for that job.
Side by side
TopicDatabox LopeBase What it isA general dashboard and reporting platform.An ops console for a portfolio of SaaS products.SetupPick metrics and build dashboards and reports.Connect tools; Overview, Revenue, Analytics, Uptime, and SEO already exist.How sources are countedEach account, property, or view is a data source, and plans cap them.Plans cap products. A product's sources count once.Uptime and errorsNot the focus.Uptime checks, Sentry errors, failing builds, and Worker error rates.SEO workSearch data on dashboards.Indexing, keywords, Domain Rating, competitors, and a content autopilot.What needs attentionGoals and alerts you set up.Checks with thresholds built in, like past-due subscriptions or a bounce rate near Resend's limit.Acting on thingsReporting.Confirmed actions on your own product, each in the audit log.Best whenYou report on marketing and sales across many kinds of tools.You run several SaaS products and want each one's health in one place. Based on how each product describes itself, checked October 2026. Sources: Databox pricing, Databox integrations. If something here is out of date, tell us and we will fix it.
How the pricing compares
Databox's pricing page, checked October 2026, lists a Free plan with 1 user, 3 data sources, 1 dashboard, and daily syncs. Analyst is $71 a month on annual billing for 1 user and 5 data sources. Team Core is $199 a month for 3 users and 10 data sources, and Team Scale is $319 a month for 10 users and 30 data sources. Paid plans sync hourly.
Databox counts a data source as a specific account, property, or view, so one Google Analytics connection with three website properties counts as three. With several products, sources add up fast.
LopeBase counts products instead. Free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats. A product's Stripe, analytics, Search Console, and other sources all count as that one product.
Where each one is stronger
Where Databox is stronger
BreadthDatabox says it connects 130+ tools, spreadsheets, databases, and APIs, well beyond SaaS tooling.
Reports and goalsDashboards and reports, plus goals and OKRs tracked against your metrics.
AgenciesAn agency plan built around client packs.
Metrics and AIBuild and forecast your own metrics, with an AI analyst and a semantic layer over them.
Where LopeBase is stronger
Made for SaaS productsMRR across Stripe and Polar accounts, active users, signups, uptime, and errors, per product.
Checks that flag problemsNeeds attention lists what is wrong today, with alerts by email or push.
SEO and contentSEO checks and a content autopilot that drafts and publishes posts for review.
Your own productYour app's users and plans, through the LopeBase Adapter, with confirmed actions.
They overlap less than it looks. Databox suits a marketing team reporting across ads, CRM, and spreadsheets. LopeBase suits a founder who wants to know, each morning, whether every product is up, earning, and growing, and what to fix first.
Which one to pick
Pick Databox if
You need reports across many kinds of business tools, for a marketing or sales team, or for agency clients.
Pick LopeBase if
You run several SaaS products and want revenue, traffic, uptime, errors, and SEO for each one, with what needs attention already worked out.
Start free Questions
Something else? Contact us.
01Is LopeBase a Databox alternative?
If what you report on is a set of SaaS products, yes. If you need dashboards across ad platforms, CRMs, and spreadsheets, Databox covers more ground.
02Can I build custom dashboards in LopeBase?
Yes. Custom dashboards and saved views work on the numbers LopeBase reads from your connected tools.
03How does LopeBase count sources?
By product. A product's Stripe account, analytics, Search Console property, and other sources count as one product toward your plan.
Databox vs Geckoboard Two KPI dashboard tools, and who each suits.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs AgencyAnalytics Client marketing reports, or ops for products you run.

---

## Databox vs Geckoboard

URL: https://lopebase.com/compare/databox-vs-geckoboard

Databox vs Geckoboard, compared on pricing, users, dashboards, and integrations, from each company's own pages in October 2026.

All comparisons Databox vs Geckoboard
Databox and Geckoboard both put business metrics on dashboards, and they are often compared. They lean different ways. Databox is an analytics platform with reports, goals, forecasting, and an agency plan. Geckoboard is about live numbers on shared screens, with unlimited viewers. Here is how they compare, from each company's own pricing page as of October 2026.
Side by side
TopicDataboxGeckoboardFree planYes: 1 user, 3 data sources, 1 dashboard, daily sync.No. A 14 day trial.Entry priceAnalyst, $71 a month annual ($85 monthly), 1 user, 5 data sources.Essentials, $79 a month annual, 2 dashboards, 1 editor, 1 screen.Next tierTeam Core, $199 a month annual: 3 users, 10 data sources.Performance, $319 a month annual: 20 dashboards, 3 editors, 5 screens.What is countedUsers and data sources. Dashboards unlimited on paid plans.Dashboards, editors, and screens. Viewers unlimited.FreshnessHourly on paid plans, daily on Free.Real time per data source.Integrations130+, by Databox's count.90+.AgenciesAn Agency plan from $79 a month plus $20 per client pack.No agency plan listed. Based on how each product describes itself, checked October 2026. Sources: Databox pricing, Geckoboard pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
Databox counts users and data sources. Free covers 1 user and 3 sources. Analyst is $71 a month on annual billing for 1 user and 5 sources, Team Core $199 for 3 users and 10, and Team Scale $319 for 10 users and 30. Annual plans save 20%. A data source is a specific account, property, or view, so they add up.
Geckoboard counts dashboards, editors, and screens, never viewers. Essentials is $79 a month on annual billing with 2 dashboards, 1 editor, and 1 screen, with extra dashboards at $24 and extra editors or screens at $20. Performance is $319 with 20 dashboards, 3 editors, and 5 screens.
If many people need to look but few build, Geckoboard's unlimited viewers go a long way. If a few people need deep analysis across many sources, Databox's model fits better.
Where each one is stronger
Where Databox is stronger
Analysis and reportsReports, goals, forecasting, custom metrics, and an AI analyst.
A free planFree forever for one user, three sources, and one dashboard.
AgenciesA dedicated plan with client packs.
More integrations130+, against Geckoboard's 90+.
Where Geckoboard is stronger
Built for screensDashboards designed for a TV in the office, with snapshots and sharing links.
Unlimited viewersEveryone can see the numbers without a seat.
Real-time dataRefreshed as fast as each source allows, not hourly.
Simple to runFewer concepts to learn: pick metrics, lay out, share.
Both are general tools: they show any business metric, from any team. That breadth is useful for a company, and more than a founder running a few products needs.
Which one to pick
Pick Databox if
You want analysis, reports, and goals across many sources, or you run an agency.
Pick Geckoboard if
You want live numbers on a shared screen that everyone can see without a seat.
If you run several products
If the dashboards you have in mind are for SaaS products you run, both tools leave you building them: one board per product, with your own thresholds for when something is wrong.
LopeBase starts with those screens already made. Connect Stripe, analytics, Search Console, Sentry, and the rest, and every product's revenue, traffic, uptime, errors, and SEO sit side by side, with what needs attention at the top. It is free for one product.
See what LopeBase does
Questions
Something else? Contact us.
01Is Databox or Geckoboard cheaper?
Databox has a free plan and Geckoboard does not. Their first paid plans are close: $71 and $79 a month on annual billing. Which costs less after that depends on whether you add users and sources (Databox) or dashboards and editors (Geckoboard).
02Which updates faster?
Geckoboard lists real-time refresh per data source. Databox syncs hourly on paid plans and daily on Free.
03Which is better for agencies?
Databox, which has an agency plan with client packs. Geckoboard does not list one.
vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs AgencyAnalytics Client marketing reports, or ops for products you run.

---

## vs Forest Admin

URL: https://lopebase.com/compare/forest-admin

LopeBase vs Forest Admin (now Forest). Forest is an admin panel on your database. LopeBase is an ops console that reads the tools your products use.

All comparisons LopeBase vs Forest Admin
Forest Admin, now called Forest, builds an admin panel on your application's data so your team can find and edit users, orders, and records. LopeBase does a different job: it never touches your database. It reads the tools each product already uses and shows growth, revenue, uptime, and SEO across all of them.
Side by side
TopicForest Admin LopeBase What it is forOperating on one app's records: find, edit, approve.Watching how a portfolio of products is doing.How it connectsA backend on your infrastructure that reads and writes your data sources directly.Read-only keys to Stripe, PostHog, Search Console, and the rest. No database access.Seeing every product at onceBuilt around an application's data sources.Built in. Totals across products, then one row per product.Stripe, PostHog, Search ConsoleOutside the core product.The core of it. Connect each with a read-only key or one click.Uptime and SEONot what it is for.Uptime every 15 minutes, plus indexing, keywords, Domain Rating, and competitors.Pricing modelBy plan, with users and data sources included.Per product. Every plan includes its operators.Best whenOne product whose team manages records every day.Several small products you want to keep an eye on in one place. Based on how each product describes itself, checked October 2026. Sources: Forest pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
Forest's pricing page, checked October 2026, lists a free Sandbox plan with 2 users and 2 data sources. Starter is $499 a month with 7 users included, then $60 a user, and 10 data sources. Professional is $2,199 a month with 25 users and unlimited data sources. Enterprise starts at $5,999 a month.
LopeBase is priced for small teams running several products. Free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats.
The two are not really priced against each other, because they do different jobs. Forest is priced for teams that operate on production data all day, often in regulated industries. LopeBase is priced for founders and small studios keeping several products healthy.
Where each one is stronger
Where Forest Admin is stronger
Editing recordsLive read and write to your databases, so your team can act on users, orders, and any table.
Schema syncForest introspects your schema and keeps the panel in step as it changes.
Your stack, your dataA backend that runs in your infrastructure, with SDKs for Node.js, Rails, and more.
Regulated companiesForest describes itself as operational infrastructure for regulated companies, with SSO on paid plans.
Where LopeBase is stronger
Many products, one viewEvery product on one Overview, with growth, revenue, uptime, and SEO side by side.
No database accessLopeBase never connects to your database, so there is nothing to grant write access to.
Growth workSEO checks, a content autopilot, and AI reviews of your numbers, beyond managing records.
Small-team pricingFree for one product, and $29 a month for three.
Many teams would use both. An admin panel on your database answers questions about one customer. LopeBase answers how each product is doing. If you want a few safe actions on your own records in LopeBase, like extending a trial, the LopeBase Adapter lets your app expose exactly those, each with a confirm step and an audit log entry.
Which one to pick
Pick Forest Admin if
Your team needs to look up and change users, orders, or records in your own database every day. That is an admin panel, and LopeBase is not one.
Pick LopeBase if
You want to know how every product is growing, earning, staying up, and ranking, from the tools you already pay for, without opening a dashboard per tool.
Start free Questions
Something else? Contact us.
01Is Forest Admin the same as Forest?
Yes. Forest Admin now goes by Forest, at forest.app. The old forestadmin.com address redirects there.
02Can LopeBase edit records in my database?
Not directly. LopeBase never connects to your database. Your app can expose specific actions through the LopeBase Adapter, and those run inside your app.
03Does LopeBase replace an admin panel?
For most small products, the everyday numbers are what matter, and LopeBase covers those. If your team edits records all day, keep an admin panel for that.
Retool vs Forest Build your own admin, or generate one from your database.vs Retool Build internal apps on your data, or open a ready ops console.vs building your own What stitching your own dashboards costs across products.vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.

---

## vs Geckoboard

URL: https://lopebase.com/compare/geckoboard

LopeBase vs Geckoboard. Geckoboard puts a team's live numbers on a dashboard or office TV. LopeBase is an ops console for running several SaaS products.

All comparisons LopeBase vs Geckoboard
Geckoboard is built to put a team's key numbers somewhere everyone can see them, often a TV on the office wall. You pick the metrics, lay out the dashboard, and share it. LopeBase starts from a different question: across every product you run, is anything broken, slipping, or worth doing today? The screens for that already exist when you connect your tools.
Side by side
TopicGeckoboard LopeBaseWhat it isLive dashboards for teams, built to be shown on screens and shared.An ops console for a portfolio of SaaS products.SetupChoose metrics and arrange widgets on each dashboard.Connect tools; Overview, Revenue, Analytics, Uptime, and SEO already exist.What it countsDashboards, editors, and TV screens. Viewers are unlimited.Products. Every tool a product uses counts once.Integrations90+, including Stripe, Search Console, GitHub, and Pingdom.Stripe, Polar, PostHog, Google Analytics, Plausible, Cloudflare, Search Console, Bing, Sentry, GitHub, Resend, and more.Uptime and errorsShown if you connect a tool that tracks them.Uptime checks every 15 minutes, Sentry errors, and failing builds, built in.SEO workSearch Console numbers on a dashboard.Indexing, keywords, Domain Rating, competitors, and a content autopilot.AlertsAlerts on the Performance plan and up.Alerts by email and browser on every plan.Best whenA team wants shared numbers on a screen all day.One person or a small team runs several products and wants each one's health in one place. Based on how each product describes itself, checked October 2026. Sources: Geckoboard pricing, Geckoboard integrations. If something here is out of date, tell us and we will fix it.
How the pricing compares
Geckoboard's pricing page, checked October 2026, lists Essentials at $79 a month on annual billing with 2 dashboards, 1 editor, and 1 screen. More dashboards are $24 each, and more editors or screens $20 each. Performance is $319 a month on annual billing with 20 dashboards, 3 editors, and 5 screens, and adds alerts, drilldown, and custom templates. Enterprise is custom. Every plan has unlimited viewers, and there is a 14 day free trial.
That model fits a team looking at the same few boards. It gets expensive the other way: one dashboard per product, across five products, already means extra dashboards on Essentials.
LopeBase counts products. Free for one product with no time limit. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats, and a new workspace gets 14 days of Portfolio with no card.
Where each one is stronger
Where Geckoboard is stronger
Made for screensDashboards look good on a TV across a room, with sharing links and snapshots for everyone else.
Unlimited viewersEveryone in the company can look without a paid seat.
Broad integrations90+ sources, so sales, support, and marketing numbers can sit next to product ones.
Metrics over MCPGeckoboard lists a Metrics MCP on its plans, for AI assistants to read your numbers.
Where LopeBase is stronger
Nothing to lay outEach product's revenue, visitors, signups, uptime, and search clicks are on Overview the moment they connect.
It tells you what is wrongChecks with thresholds built in, like a site down, a failing build, or payments past due, sorted to the top.
SEO you can act onIndexing checks, keyword tracking, and drafts for the searches stuck on page two, beyond a Search Console chart.
Priced for many productsAdding a product never means paying for another dashboard or screen.
The two can live side by side. A team that wants its sales and support numbers on the office TV is well served by Geckoboard. A founder who wants to open one page each morning and see which product needs attention is the person LopeBase is made for.
Which one to pick
Pick Geckoboard if
Your team wants live numbers from sales, support, and marketing tools on a shared screen, and you are happy to lay out the dashboards yourself.
Pick LopeBase if
You want to open one page each morning and see which of your products is down, slipping, or worth working on, without laying out a dashboard for each.
Start free Questions
Something else? Contact us.
01Is LopeBase a Geckoboard alternative?
For running SaaS products, yes. If you want a TV dashboard mixing sales, support, and marketing tools, Geckoboard is the better fit.
02Can I show LopeBase on a TV?
There is no dedicated TV mode. Overview and dashboards work full screen in a browser, and the weekly email covers people who do not log in.
03Does LopeBase have unlimited viewers?
No. Plans include operators: 1 on Free, 3 on Studio, 10 on Portfolio, and no limit on Agency.
Databox vs Geckoboard Two KPI dashboard tools, and who each suits.vs Databox A general KPI dashboard, or a console made for SaaS products.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs AgencyAnalytics Client marketing reports, or ops for products you run.

---

## vs Klipfolio

URL: https://lopebase.com/compare/klipfolio

LopeBase vs Klipfolio. Klipfolio builds custom dashboards from 130+ sources. LopeBase is an ops console made for running several SaaS products.

All comparisons LopeBase vs Klipfolio
Klipfolio's Klips is a dashboard builder with a lot of reach: 130+ integrations, data modelling, and dashboards you design widget by widget. That flexibility is the point, and it also means someone has to build and maintain each dashboard. LopeBase does one job, keeping several SaaS products healthy, so its screens are already made and the work is connecting your tools.
Side by side
TopicKlipfolio LopeBaseWhat it isA dashboard builder (Klips), with a separate metrics product, PowerMetrics.An ops console for a portfolio of SaaS products.SetupBuild each dashboard from data sources and Klips.Connect tools; the screens already exist.What it countsDashboards. Users are unlimited.Products. Every tool a product uses counts once.Data freshnessFrom every 4 hours on Base to up to the minute on Team+.Stored readings refresh every 15 minutes; product pages read live.Integrations130+, including Stripe, Google Analytics 4, Search Console, and GitHub.The tools SaaS products run on: billing, analytics, search, errors, email, hosting, and banking.Uptime and errorsOnly from a tool you connect.Uptime checks, Sentry errors, and failing builds, built in.Acting on thingsReporting.Alerts, AI reviews, a content autopilot, and confirmed actions on your own product.Best whenYou want custom dashboards across many kinds of data.You run several products and want each one's health without building anything. Based on how each product describes itself, checked October 2026. Sources: Klipfolio pricing, Klipfolio integrations. If something here is out of date, tell us and we will fix it.
How the pricing compares
Klipfolio's pricing page, checked October 2026, lists four Klips plans, all with unlimited users and 130+ integrations. Base is $120 a month on annual billing ($140 monthly) for 3 dashboards refreshed every 4 hours. Grow is $190 ($220 monthly) for 10 dashboards refreshed hourly. Team is $310 ($350 monthly) for 20 dashboards every 15 minutes, with SSO. Team+ is $600 ($690 monthly) for 40 dashboards with up-to-the-minute refresh. There is a 14 day trial with no card.
Unlimited users is generous, and the dashboard cap is what to watch. One dashboard per product plus a summary board puts a five product portfolio on Grow.
LopeBase counts products. Free for one product with no time limit. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats, and a new workspace gets 14 days of Portfolio with no card.
Where each one is stronger
Where Klipfolio is stronger
Reach130+ integrations and data modelling, so almost any number can end up on a dashboard.
Design controlEvery Klip is yours to shape, from the query to the chart.
Unlimited usersEvery plan, so a whole company or a client can view.
ReportsPDF reports, published links, and scheduled reports on Grow and up.
Where LopeBase is stronger
Already builtOverview, Revenue, Analytics, Uptime, and SEO exist the moment you connect a tool. Nothing to design or maintain.
Made for SaaSMRR across Stripe and Polar accounts, active users, signups, errors, and uptime per product.
What needs youFailing checks and reviews waiting, sorted to the top of Overview, with alerts by email and browser.
A lower starting priceThree products for $29 a month, against $120 for Klipfolio's first plan.
If your question is "how do I chart this data," Klipfolio answers it well. If your question is "which of my products needs me today," building that in a dashboard tool takes real time, and LopeBase starts there.
Which one to pick
Pick Klipfolio if
You need custom dashboards across many kinds of data, want full control over each chart, and have someone to build and keep them up.
Pick LopeBase if
You would rather connect Stripe, analytics, and Search Console and have each product's screens ready than build and maintain dashboards yourself.
Start free Questions
Something else? Contact us.
01Is LopeBase a Klipfolio alternative?
For running SaaS products, yes. For custom dashboards across finance, sales, and operations data, Klipfolio covers more.
02Can I build my own charts in LopeBase?
Yes. Custom dashboards and saved views work on the numbers LopeBase reads from your connected tools, and every connection's data has its own charts.
03Does LopeBase do PDF or scheduled reports?
It sends a weekly summary by email, per person, with the products and sections they choose. There are no PDF exports of dashboards yet.
vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs building your own What stitching your own dashboards costs across products.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs AgencyAnalytics Client marketing reports, or ops for products you run.

---

## vs ProfitWell Metrics

URL: https://lopebase.com/compare/profitwell

LopeBase vs ProfitWell Metrics. ProfitWell, from Paddle, is free subscription analytics. LopeBase puts each product's revenue next to traffic, uptime, and SEO.

All comparisons LopeBase vs ProfitWell Metrics
ProfitWell Metrics, now part of Paddle, is free subscription reporting: MRR, churn, upgrades and downgrades, customer lifetime value, and cohorts, with benchmarks against other SaaS companies. It is hard to argue with free for revenue numbers alone. LopeBase covers less of subscription analytics and more of everything around it, so you can see why revenue moved: a traffic drop, a site outage, a search that fell to page two.
Side by side
TopicProfitWell Metrics LopeBaseWhat it isFree subscription analytics, from Paddle.An ops console for a portfolio of SaaS products.PriceFree.Free for one product; paid plans from $29 a month.Billing systemsStripe, Chargebee, Braintree, Zuora, Recurly, Paddle, and others.Stripe and Polar.Revenue depthMRR, churn, upgrades and downgrades, lifetime value, cohorts, segments, and benchmarks.MRR, one-time revenue, past-due payments, and cash from Mercury, Brex, Rho, or Wise.Beyond revenueCustomer health signals and at-risk alerts.Traffic, signups, uptime, errors, builds, email delivery, and SEO for each product.Several productsReporting per billing account.Every product side by side on one Overview.Best whenYou want strong subscription metrics for free.You want each product's revenue in context with everything else. Based on how each product describes itself, checked October 2026. Sources: ProfitWell Metrics. If something here is out of date, tell us and we will fix it.
How the pricing compares
ProfitWell Metrics is free. Paddle's page, checked October 2026, describes it as "completely free" revenue reporting for subscription and SaaS companies, and says it connects to Stripe, Chargebee, and other billing tools including Paddle, so you do not need to bill through Paddle to use it.
Paddle also sells paid products alongside it, like Retain for failed payments and churn. The metrics themselves cost nothing.
LopeBase counts products. Free for one product with no time limit. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats, and a new workspace gets 14 days of Portfolio with no card.
Where each one is stronger
Where ProfitWell Metrics is stronger
It is freeSubscription metrics at no cost, at any revenue.
Subscription depthCohorts, segmentation by plan, lifetime value, and upgrade and downgrade tracking that LopeBase does not attempt.
BenchmarksCompares your numbers with 30,000+ SaaS companies, by Paddle's count.
More billing systemsChargebee, Braintree, Zuora, Recurly, and Paddle as well as Stripe.
Where LopeBase is stronger
Revenue in contextMRR next to visitors, signups, uptime, and errors, so a drop has an explanation on the same page.
Every product at onceSeveral Stripe or Polar accounts, one per product, side by side.
Checks and alertsPayments past due, a site down, or a failing build reach you by email or browser.
Cash and runwayBank balances from Mercury, Brex, Rho, or Wise beside revenue.
Plenty of founders could use both: ProfitWell Metrics for deep, free subscription reporting, and LopeBase for the daily view of every product. If you only care about subscription metrics, start with ProfitWell.
Which one to pick
Pick ProfitWell Metrics if
You only need subscription metrics, want them free, or bill through Chargebee, Braintree, Zuora, or Recurly.
Pick LopeBase if
You want each product's MRR next to its traffic, signups, uptime, and SEO, so a change in revenue comes with a reason on the same page.
Start free Questions
Something else? Contact us.
01Is ProfitWell Metrics really free?
Paddle's page says so, as of October 2026. Paddle charges for other products, such as Retain, but not for the metrics.
02Do I have to use Paddle billing for ProfitWell Metrics?
No. Paddle's page says it works with Stripe, Chargebee, and other billing tools.
03Can I use LopeBase and ProfitWell together?
Yes. Both only read from your billing system, so connecting one does not affect the other.
ChartMogul vs ProfitWell Paid revenue analytics against a free one.vs Baremetrics Deep subscription analytics, or revenue next to everything else.vs ChartMogul A revenue analytics platform, or a portfolio ops console.vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs Databox A general KPI dashboard, or a console made for SaaS products.

---

## vs Retool

URL: https://lopebase.com/compare/retool

LopeBase vs Retool. Retool builds internal apps on your data. LopeBase is a ready ops console for growth, revenue, uptime, and SEO across products.

All comparisons LopeBase vs Retool
Retool is a platform for building internal apps and automations on your own data. You assemble screens from components and wire them to databases and APIs. LopeBase is a finished ops console for people who run several small SaaS products: connect the tools each product already uses, and growth, revenue, uptime, and SEO for all of them are on one screen.
Side by side
TopicRetool LopeBase What it isA builder for internal apps and workflows.A ready console with Overview, Analytics, Revenue, Uptime, SEO, and Content screens.Starting pointA blank canvas. You design each screen.Connect a tool and its numbers appear on screens that already exist.Seeing every product at onceYou build a portfolio view yourself.Built in. Totals across products, then one row per product.Stripe, PostHog, Search ConsoleYou wire each API and chart it.Connectors. A read-only key, or one-click sign-in for Google, Bing, Cloudflare, and GitHub.Uptime and SEOSomething you would build, or another tool.Uptime checks every 15 minutes, plus indexing, keywords, Domain Rating, and competitors.Your databaseUsually a direct connection, so apps can read and write records.Never connected. Your own records come through a small adapter you control.Pricing modelPer builder and per internal user.Per product. Every plan includes its operators.HostingRetool cloud, or self-hosted.Hosted by us. Nothing to run.Best whenYou need custom apps that change your own data.You run several small products and want to see how each is doing, today. Based on how each product describes itself, checked October 2026. Sources: Retool pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
Retool charges per person. On its pricing page, checked October 2026, the Free plan covers up to 5 users and 500 workflow runs a month. Team is $10 per builder and $5 per internal user a month on annual billing ($12 and $7 monthly). Business is $50 per builder and $15 per internal user on annual billing ($65 and $18 monthly). Enterprise is custom, and adds SSO, SCIM, and full self-hosting options.
LopeBase charges per product. Free for one product. Studio is $29 a month for 3 products, Portfolio $99 for 10, and Agency $299 with no limit. Priced by products, not seats. A new workspace gets 14 days of Portfolio with no card.
The bigger cost is rarely the invoice. With Retool you are also paying in build time: every screen, query, and chart is yours to make and keep working when an API changes.
Where each one is stronger
Where Retool is stronger
Custom internal appsSupport consoles, refund tools, approval flows: screens shaped exactly to how your team works.
Writing to your dataApps can read and write your databases and APIs directly.
WorkflowsScheduled and triggered automations, with run limits by plan.
Self-hostingRun it in your own infrastructure, including air-gapped on Enterprise.
Where LopeBase is stronger
Ready on day oneThe screens exist. Connect Stripe, PostHog, or Search Console and the numbers show up.
Many products, one viewEvery product rolls up into one Overview, with a row each and totals across them.
Growth work as well as recordsUptime checks, SEO checks, a content autopilot, and AI reviews of your numbers.
Read-only by designLopeBase reads your tools with read-only keys and never touches a product's database.
Plenty of teams would use both. Retool is a good place for the one internal app a product really needs, like a support screen that edits accounts. LopeBase covers the daily question of how every product is doing, without building a dashboard for it. LopeBase can also run a product's own actions, like granting credits, through the LopeBase Adapter, with a confirm step and an audit log entry for each one.
Which one to pick
Pick Retool if
You need custom internal apps that edit your own data: support screens, refunds, approval flows. Retool is built for that, and LopeBase does not try to be.
Pick LopeBase if
You run two or more small SaaS products and want growth, revenue, uptime, and SEO side by side, without building or maintaining dashboards.
Start free Questions
Something else? Contact us.
01Is LopeBase a Retool alternative?
For one job, yes: seeing how several SaaS products are doing. For building custom internal apps, no. LopeBase is a finished console, not a builder.
02Can I build my own screens in LopeBase?
You can build custom dashboards from the numbers LopeBase reads, and save views. You cannot design arbitrary apps the way you can in Retool.
03Does LopeBase connect to my database like Retool does?
No. LopeBase reads the tools you already use with read-only keys. If you want your own records in the console, the LopeBase Adapter exposes only what you choose, from inside your app.
04Which is cheaper for a solo founder?
For a single builder, Retool's Team plan costs less per month than LopeBase Studio, but you build every screen. LopeBase is free for one product, and Studio covers three products for $29 a month with the screens already built.
Retool vs Forest Build your own admin, or generate one from your database.vs Forest An admin panel on your database, or a view of your tools.vs building your own What stitching your own dashboards costs across products.vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.

---

## Retool vs Forest

URL: https://lopebase.com/compare/retool-vs-forest

Retool vs Forest, formerly Forest Admin, compared on how you build, pricing, and fit, from each company's own pages in October 2026.

All comparisons Retool vs Forest
Retool and Forest both give a team screens on top of its own data, and both are common answers to "we need an admin panel." They get there differently. Retool is a builder: you assemble apps from components and queries. Forest, which dropped the "Admin" from its name, generates an admin panel from your database that you then customize. Prices are far apart too.
Side by side
TopicRetoolForestApproachBuild apps from components, queries, and code.An admin panel generated from your data, then customized.Free planUp to 5 users and 500 workflow runs a month.Sandbox: 2 users, 2 data sources, 500 write events a month.Entry priceTeam: $10 per builder and $5 per internal user a month, annual.Starter: $499 a month with 7 users and 10 data sources.How price growsPer builder and per user.Per user past the included seats, plus write events.Beyond admin panelsWorkflows, agents, a database, and external apps.Focused on operating on your production data.Self-hostingYes, on every plan.Not listed on the pricing page.Best whenEngineers want to build many internal tools.An ops team needs a full admin on production data quickly. Based on how each product describes itself, checked October 2026. Sources: Retool pricing, Forest pricing. If something here is out of date, tell us and we will fix it.
How the pricing compares
Retool charges per person. Team is $10 per builder and $5 per internal user a month on annual billing ($12 and $7 monthly). Business is $50 per builder and $15 per internal user ($65 and $18 monthly). The Free plan covers up to 5 users.
Forest charges per plan with seats included. Starter is $499 a month with 7 users and 10 data sources, then $60 per extra user, and 5,000 write events with a charge per event after that. Professional is $2,199 a month with 25 users and unlimited data sources, and Enterprise starts at $5,999.
For a small team, Retool is much cheaper on paper. The trade is build time: Forest gives you a working admin from day one, while every Retool screen is one you make and maintain.
Where each one is stronger
Where Retool is stronger
FlexibilityAdmin panels and every other internal tool: dashboards, workflows, and apps for outside users.
Price for small teamsA team of five on Team costs a fraction of Forest's Starter.
Self-hostingAvailable on every plan, including Free.
Wider platformWorkflows, agents, and its own database.
Where Forest is stronger
Ready on day oneThe admin panel comes from your data model, so there is little to build before it is useful.
Made for operationsBuilt around support and ops teams working on production records.
Seats includedStarter includes 7 users, Professional 25.
Less to maintainScreens follow your data model instead of being hand-built.
Both connect to your database, so both carry the care that comes with writing to production. Retool fits engineering-led teams that want to build many tools. Forest fits ops-heavy teams that want a complete admin quickly.
Which one to pick
Pick Retool if
Engineers on your team want to build many kinds of internal tools, and you want to self-host.
Pick Forest if
Your ops or support team needs a complete admin panel on production data soon, and the budget is there.
If you run several products
If what you need is not editing records but knowing how each of your products is doing, an admin panel builder is a long way round.
LopeBase never connects to your database. It reads the tools each product already uses, like Stripe, PostHog, Search Console, and Sentry, and shows revenue, traffic, uptime, errors, and SEO for every product in one place. Many teams use an admin panel and LopeBase side by side. It is free for one product.
See what LopeBase does
Questions
Something else? Contact us.
01Is Forest Admin now called Forest?
Yes. Its site at forest.app uses the name Forest, and forestadmin.com redirects there.
02Is Retool or Forest cheaper?
For a small team, Retool: Team is $10 per builder and $5 per user a month. Forest's first paid plan is $499 a month, though it includes 7 users.
03Can I self-host Retool or Forest?
Retool lists self-hosting on every plan. Forest's pricing page does not list a self-hosted option.
vs Retool Build internal apps on your data, or open a ready ops console.vs Forest An admin panel on your database, or a view of your tools.vs building your own What stitching your own dashboards costs across products.vs Databox A general KPI dashboard, or a console made for SaaS products.vs Geckoboard A team TV dashboard, or a console that tells you what to fix.vs Klipfolio Dashboards you build from 130+ sources, or ones already built.

---

## Connectors: Stripe, PostHog, GA4, and more

URL: https://lopebase.com/connectors

Connect Stripe, Polar, PostHog, GA4, Search Console, Sentry, Supabase, and more to one ops console, with read-only keys, matched to each product.

Connect the tools you already use.
Stripe, Polar, PostHog, Google Analytics 4, Plausible, Cloudflare Web Analytics, Search Console, Bing, Sentry, Cloudflare, Supabase, GitHub, Resend, Sequenzy, Mercury, Brex, Rho, Wise, EmDash, uptime checks, your AI provider, and your own app through the LopeBase Adapter. Connect Google, GitHub, Cloudflare, and Bing in one click, and paste a scoped key for the rest.
Every connector
PostHogProduct analytics Google Analytics 4Traffic Search ConsoleSearch clicks and rank Bing WebmasterSearch clicks and rank SentryErrors RollbarErrors HoneybadgerErrors BugsnagErrors StripeMRR and revenue EmDashPosts and publishing AI providerOpenAI, Anthropic, AI Gateway CloudflareWorkers, deploys, D1 GitHubPRs, issues, Actions ResendDelivery and bounces SequenzyNewsletters and sequences Uptime checksIs it up Better StackUptime MercuryCash and burn PolarRevenue and subscriptions PlausiblePrivate traffic Cloudflare Web AnalyticsCookieless traffic SupabaseDatabase health BrexCash and burn RhoCash and treasury WiseEvery currency LopeBase AdapterYour app: users, billing, content Your own product, without handing over the database.
Describe it once. List the records and actions your product exposes, like users and a grant-credits action.
Mount the LopeBase Adapter. A small handler in your app, usually at /api/lopebase. Your coding agent can install it from one prompt.
Connect it. Paste its address and signing secret into LopeBase. Your users, billing, and content show up next to everything else.
// Example: what your product exposes resources: { users: { fields: ["email", "plan", "credits"] }, }, actions: { grant_credits: { params: { userId: "string", amount: "number" }, capability: "write", }, }, How connecting works
Each connector asks for the narrowest access the service offers, and the connect dialog walks through it step by step. Where a service lets a link fill in the key's name and permissions, the link does, so you only press Create.
01Sign in with Google, Bing, Cloudflare, or GitHub and approve read-only access. For the rest, paste a read-only key.
02Match each source to a product. One account can cover several products, like a Supabase token that reaches every project.
03The numbers land on Overview and the screen they belong to, and anything wrong shows under Needs attention.
Connector questions
Something else? Contact us.
01Can LopeBase change anything in my tools?
Almost never. Connectors read with read-only keys. The exceptions are spelled out on each page: Sequenzy can turn a sequence on or pause it when you ask, and EmDash publishes only the posts you approve.
02Does LopeBase connect to my database?
No. It reads the tools you already use. Your own records come through the LopeBase Adapter, which exposes only the fields you declare.
03How are my keys stored?
Encrypted at rest in your workspace. You can remove a connection at any time.
04Do my sources count against my plan?
Plans count products, not sources. A product's Stripe account, analytics, Search Console property, and the rest all count as that one product.
05What if a tool I use is missing?
Tell us on the contact page. In the meantime, your own app can send its numbers through the LopeBase Adapter.
See every product in one place.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Connect one product for free. Add the rest when you are ready.
Start free Sign in

---

## AI providers

URL: https://lopebase.com/connectors/ai-providers

Connect OpenAI, Anthropic, OpenRouter, or a Cloudflare AI Gateway to see available models and test completions without leaving the console.

All connectors Your AI providers, in the same console.
Connect OpenAI, Anthropic, OpenRouter, or a Cloudflare AI Gateway to see available models and test completions without leaving the console.
Connect AI providers free Provider API key, or a gateway URL and token.
What LopeBase reads
Model catalogThe models your key can use, per provider.
Test completionsSend a prompt to check a model and key are working.
How to connect it
01Paste an API key for your provider.
02Point it at a gateway URL if you route through one, and pick a default model.
03Pipelines that draft content use the default model.
What LopeBase does with it
Your key goes straight to your provider. LopeBase uses it only for the drafting and research you run.
What it is used forDrafting posts for the content autopilot, keyword research, and AI reviews of your numbers.
Credits or your own keyEvery plan includes monthly AI credits. Bring your own key and those runs use no credits.
AI providers questions
Something else? Contact us.
01Which providers work?
OpenAI, Anthropic, OpenRouter, and Cloudflare AI Gateway, or any OpenAI-compatible endpoint.
02Does LopeBase train on my data?
No. Requests go straight to your provider with your key.
03Which model runs by default?
gpt-4o-mini, unless you pick another default model.
04Do I need my own key?
No. Every plan includes AI credits each month. A key of your own is optional.
Content autopilot Plan articles on a calendar, draft them days ahead in your voice, check every one, and publish on schedule. Edit before or after it goes live.AI reviews A weekly briefing and reviews of revenue, traffic, and outages, written from your own numbers. Each one says what changed and what to do next.EmDash CMS Read posts and categories from every EmDash site, check each one's SEO health, and publish new posts through a review gate, all from one console. Put AI providers next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Better Stack

URL: https://lopebase.com/connectors/betterstack

Bring the Better Stack monitors you already run into LopeBase: whether each is up, 30-day availability and incidents, and alerts beside revenue and traffic.

All connectors Better Stack uptime for every product, beside everything else.
Keep your Better Stack monitors. LopeBase reads whether each one is up and its 30-day availability, and puts them next to each product's revenue, traffic, and errors.
Connect Better Stack free A Better Stack Uptime API token. LopeBase lists your monitors to pick from.
What LopeBase reads
Monitor statusWhether each monitor is up, down, paused, or in maintenance, and when it was last checked.
30-day availabilityAvailability, number of incidents, and total downtime from Better Stack's own SLA report.
Several monitors per productMap a product's home page, API, and app monitors to it together.
How to connect it
01In Better Stack, open Settings, then API tokens, and copy an Uptime API token.
02Pick the monitor, or monitors, that watch each property.
03A down monitor shows under Needs attention and can alert you by email or browser.
What LopeBase does with it
LopeBase only reads monitors and their availability. It never pauses, edits, or acknowledges anything in Better Stack.
On the Uptime pageEvery monitor sits beside LopeBase's own checks, with its status and 30-day availability.
Down monitors flaggedA monitor Better Stack reports as down shows under Needs attention for its product, with an alert by email or browser.
Availability beside revenueEach product's 30-day availability and incidents sit next to its revenue and traffic.
A broken connectionIf the token is revoked, the connection shows under Needs attention, so a gap in the numbers never goes unnoticed.
Better Stack questions
Something else? Contact us.
01Can I keep LopeBase's own uptime checks too?
Yes. They run side by side. Better Stack covers the monitors you already set up there, and LopeBase's checks are there for any site that has none.
02How fast does a down monitor show up?
On LopeBase's next check, every 15 minutes, and it alerts on that first check, since Better Stack has already confirmed the outage.
03Does it read Better Stack logs or incidents?
Not yet. It reads Uptime monitors and their availability.
Uptime checks LopeBase's own checks every 15 minutes, for sites with no monitor elsewhere.Sentry Unresolved issues and error volume across all of your Sentry projects.Cloudflare Requests and errors for every Worker, next to the products they run. Put Better Stack next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Bing Webmaster Tools

URL: https://lopebase.com/connectors/bing-webmaster

Bing also feeds ChatGPT search and Copilot. Read Bing Webmaster Tools data for every product's site, right next to Google Search Console.

All connectors Bing search data for every site, next to Google's.
Bing also feeds ChatGPT search and Copilot. Read Bing Webmaster Tools data for each site alongside Search Console.
Connect Bing Webmaster Tools free Sign in with Bing and approve read-only access. LopeBase only reads search data and never submits or changes anything.
What LopeBase reads
Search performanceClicks, impressions, click-through rate, and position per site.
Top queriesThe searches that bring people in from Bing.
Daily trafficClicks and impressions over time.
Your AI agent can read Bing too. See what it can ask.
How to connect it
01Click Connect Bing and approve read-only access on Bing's own page.
02Each product is matched to its verified site by domain, for one product or all of them at once.
03Bing numbers use the same fields as Search Console, so they sit side by side.
What LopeBase does with it
Connect Bing asks only to read: LopeBase reads search data and never submits or changes anything.
Next to GoogleBing clicks, impressions, and queries sit beside Search Console's on the SEO screen.
Readable by your agentOver MCP, an AI agent can read Bing data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Bing Webmaster Tools questions
Something else? Contact us.
01Why bother with Bing?
Bing's index powers answers in several AI assistants, so its search data is a useful early signal for AI visibility.
02Is it read only?
Yes.
03Do I need to copy a key from Bing?
No. Press Connect Bing and approve read-only access on Bing's own page. There is nothing to copy.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Bing Webmaster MCP Give your AI agent Bing Webmaster data over MCP: search queries, daily clicks, and inbound links for every site, next to your Google numbers.Google Search Console See clicks, impressions, and rankings for all of your products' sites together in one view, and spot the one that dropped. Read-only access.SEO MCP server One MCP server for your agent's SEO work: Search Console, Bing, GA4, Plausible, PostHog, and Cloudflare, for every site you run, in one set of tools. Put Bing Webmaster Tools next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Brex

URL: https://lopebase.com/connectors/brex

See your Brex cash balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.

All connectors Brex cash next to your revenue.
See your Brex cash balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.
Connect Brex free A Brex user token with read-only cash scopes. It cannot move money.
What LopeBase reads
Cash summaryWhat is available across your cash accounts.
AccountsEach cash account and its balance. Account numbers are never shown.
TransactionsRecent money in and out, with who it was with.
How to connect it
01In Brex, open Developer settings and create a user token with only accounts.cash.readonly and transactions.cash.readonly.
02Paste it once for the workspace.
03Cash shows on Revenue and Overview, beside MRR, and adds up with any other bank you connect.
What LopeBase does with it
LopeBase only reads balances and transactions. A read-only token cannot move money or change anything in Brex.
Cash beside revenueBalances show on Revenue and Overview, next to MRR, and add up with any other bank you connect.
No account numbersAccount and routing numbers never show in the console.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Brex questions
Something else? Contact us.
01Can LopeBase move money?
No. The token can only read, and LopeBase never asks for more.
02Is money in another currency added in?
No. It is listed beside your total, never added to it.
03Why did my Brex connection stop?
Brex stops a token that goes 90 days unused. Create a new read-only token and paste it in.
Mercury See your Mercury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.Rho See your Rho checking, savings, and treasury balances, money in and out over the last 30 days, and your recent transactions.Stripe Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row. Put Brex next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Bugsnag

URL: https://lopebase.com/connectors/bugsnag

See open Bugsnag errors, daily events, and the busiest errors for every product you run, next to its revenue, traffic, and uptime.

All connectors Bugsnag errors for every product, in one place.
See open errors, events per day, and the busiest errors, for each Bugsnag project, next to the rest of each product.
Connect Bugsnag free Your Bugsnag personal auth token. LopeBase lists your projects to pick from.
What LopeBase reads
Error summaryOpen errors per project, and events in the last 24 hours.
Busiest errorsThe open errors with the most events, with class, message, severity, and users affected.
Daily eventsEvents per day for the last two weeks.
How to connect it
01Create a personal auth token in your Bugsnag account settings.
02Pick each property's project from the list LopeBase shows.
03Error totals and spikes show next to each product's revenue and traffic.
What LopeBase does with it
LopeBase only reads errors and event counts. It never fixes, snoozes, or changes anything in Bugsnag.
Errors beside revenueEach product's open errors sit on its row, next to its revenue and traffic, so a spike has context.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Bugsnag questions
Something else? Contact us.
01Which errors does it count?
Open ones: everything not fixed, snoozed, or ignored, the same as Bugsnag's own Open filter.
02Does it work with mobile apps?
Yes. It reads any Bugsnag project, web or mobile, the same way.
03Can I fix errors from LopeBase?
No. The Bugsnag connector only reads. Mark errors fixed in Bugsnag.
Sentry Unresolved issues and error volume across all of your Sentry projects.Rollbar Active items and daily occurrences for every Rollbar project.Honeybadger Unresolved errors and the busiest ones, per project. Put Bugsnag next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Cloudflare

URL: https://lopebase.com/connectors/cloudflare

See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.

All connectors Every Worker, and what it is doing.
See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.
Connect Cloudflare free Connect Cloudflare in one click, read-only. It cannot deploy or change anything. A read-only API token works too.
What LopeBase reads
WorkersRequests, errors, and error rate over the last 24 hours, per Worker.
Latest deploysWhen each Worker last shipped, from where, and who shipped it.
D1 databasesSize and table count for each database.
How to connect it
01Press Connect Cloudflare and approve read-only access to Workers, D1, and analytics. It never sees your Workers' code.
02Pick the account to watch, if you have more than one.
03A Worker with a rising error rate shows up next to that product's revenue and traffic.
What LopeBase does with it
LopeBase only reads Workers, deploys, D1, and analytics. It never deploys or changes anything in Cloudflare.
Worker error ratesA Worker with 5% of requests failing over 24 hours is worth a look, and 20% is flagged as broken. Workers with fewer than 100 requests are left out.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Cloudflare questions
Something else? Contact us.
01Can I deploy or roll back from LopeBase?
Not today. The Cloudflare connector reads. Deploy and roll back with Wrangler or the dashboard.
02Do I connect it once per product?
No. One sign-in covers the whole Cloudflare account, and the same sign-in connects Web Analytics for each product.
03Which permissions does a token need?
Read access to Workers scripts, D1, and account analytics. The link in the connect guide fills them in.
Cloudflare Web Analytics See pageviews, visits, and top pages from Cloudflare's free, cookieless Web Analytics for each product, next to its revenue, errors, and search.GitHub See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering. Put Cloudflare next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Cloudflare Web Analytics

URL: https://lopebase.com/connectors/cloudflare-web-analytics

See pageviews, visits, and top pages from Cloudflare's free, cookieless Web Analytics for each product, next to its revenue, errors, and search.

All connectors Cloudflare Web Analytics next to everything else.
See pageviews, visits, and top pages from Cloudflare's free, cookieless Web Analytics for each product's site.
Connect Cloudflare Web Analytics free Connect Cloudflare in one click, read-only. A read-only API token works too.
What LopeBase reads
Web analyticsPageviews and visits over the last 7 and 28 days.
Daily pageviewsPageviews and visits per day, for the trend on Analytics.
Top pagesThe most-viewed pages over the last 7 days.
Your AI agent can read Cloudflare Web Analytics too. See what it can ask.
How to connect it
01Press Connect Cloudflare and approve read-only access to your analytics. LopeBase never changes anything in Cloudflare.
02Each product's site is matched by its domain, or you pick it from a list.
03Its traffic shows on Analytics and Overview, beside the other products.
What LopeBase does with it
LopeBase only reads analytics. It never changes anything in Cloudflare.
Tracking that stoppedA site with no pageviews in the last 7 days is flagged. That usually means a tracking snippet broke in a deploy.
Free traffic numbersSites already on Cloudflare get pageviews, visits, and top pages without adding another analytics tool.
Readable by your agentOver MCP, an AI agent can read Cloudflare Web Analytics data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Cloudflare Web Analytics questions
Something else? Contact us.
01Why visits, not visitors?
Cloudflare Web Analytics counts visits, not unique visitors, so LopeBase shows visits and leaves visitor counts out instead of guessing.
02Is this the same as the Cloudflare connector?
No. This reads Web Analytics only. The Cloudflare connector covers Workers and deploys.
03What permission does a token need?
Only Account Analytics: Read. Or press Connect Cloudflare and approve read-only access.
04Where do I find a site's ID?
Connect in one click and pick the site from a list. With a token, open Web Analytics, pick the site, and copy the siteTag from the address bar.
Cloudflare Analytics MCP Connect Cloudflare Web Analytics to your AI agent over MCP. Read cookieless pageviews, visits, top pages, and referrers for every site you run.Cloudflare See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.Plausible See pageviews, visitors, and top pages for each product's site in Plausible, next to its revenue, errors, and search clicks. Put Cloudflare Web Analytics next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## EmDash CMS

URL: https://lopebase.com/connectors/emdash

Read posts and categories from every EmDash site, check each one's SEO health, and publish new posts through a review gate, all from one console.

All connectors Run your EmDash blogs from one console.
Read posts and categories from every EmDash site, check their SEO health, and publish through a review gate.
Connect EmDash CMS free EmDash access token. LopeBase only creates and publishes the posts you approve.
What LopeBase reads
Posts and categoriesEvery post with its status, author, and category.
SEO overviewA computed summary of each site's posts, like missing descriptions or thin content.
What you can do
Create and publish postsDraft a post, send it through review, and publish it.
Notify search enginesPing IndexNow after publishing and refresh llms.txt.
How to connect it
01Create an access token in your EmDash site.
02Paste the site URL and token. Add an IndexNow key to ping search engines on publish.
03Posts show up under Content, and the SEO pipeline can use the site.
What LopeBase does with it
LopeBase reads your posts, and only creates or publishes the posts you approve. It never deletes or edits your other content.
Content queueThree posts waiting for review, or five in the queue, are flagged so drafts do not pile up.
Faster indexingAdd an IndexNow key and each published post is sent to Bing and other search engines right away.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
EmDash CMS questions
Something else? Contact us.
01What is EmDash?
A headless CMS that runs on Cloudflare, with a REST API LopeBase reads and writes through.
02Does publishing need approval?
When you use a pipeline, yes. It stops for a person before the publish step.
03Can LopeBase delete my posts?
No. It never deletes or edits your other content. It only creates and publishes the posts you approve.
Content autopilot Plan articles on a calendar, draft them days ahead in your voice, check every one, and publish on schedule. Edit before or after it goes live.Google Search Console See clicks, impressions, and rankings for all of your products' sites together in one view, and spot the one that dropped. Read-only access.AI providers Connect OpenAI, Anthropic, OpenRouter, or a Cloudflare AI Gateway to see available models and test completions without leaving the console. Put EmDash CMS next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## GitHub

URL: https://lopebase.com/connectors/github

See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch.

All connectors Open work and failing builds for every repo.
See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch.
Connect GitHub free Connect GitHub in one click and pick the repos LopeBase can see. A fine-grained read-only token works too.
What LopeBase reads
Repository summaryOpen pull requests, open issues, and failed runs on the default branch.
Pull requestsEvery open PR with its author, age, and draft state.
Actions runsRecent workflow runs and how each one ended.
IssuesOpen issues, without pull requests mixed in.
How to connect it
01Press Connect GitHub and install the LopeBase app on the repos you pick. Or paste a fine-grained token with read access to Contents, Pull requests, Issues, and Actions.
02Check the repo matched to each product by name and site, and change any that are wrong.
03Each product's open work sits next to its errors and revenue.
What LopeBase does with it
With a token, LopeBase only reads pull requests, issues, and Actions runs. It never pushes code or changes your repo.
Failing buildsIf the latest run of a workflow on the default branch failed, the product is flagged, with the workflow names.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
GitHub questions
Something else? Contact us.
01Can I merge or re-run builds from LopeBase?
Not today. The GitHub connector reads. Merge and re-run in GitHub.
02Does it work with private repos?
Yes. LopeBase sees the repos you add to its GitHub app, or that your token can read.
03Which permissions does a token need?
Read access to contents, pull requests, issues, and Actions. The link in the connect guide fills them in for you.
Cloudflare See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.Sentry See unresolved issues, error volume, and the loudest problems across all of your Sentry projects, on the same screen as the rest of each product.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering. Put GitHub next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Google Analytics 4

URL: https://lopebase.com/connectors/google-analytics

Read the GA4 property for each of your products and compare traffic side by side, without switching between properties in Google Analytics.

All connectors Google Analytics 4 for every site, on one screen.
Read GA4 properties for each of your products and compare traffic without switching between properties.
Connect Google Analytics 4 free Connect with Google in one click, read-only. A service account works too.
What LopeBase reads
Web analyticsVisitors, pageviews, and active users per GA4 property.
Daily pageviewsTraffic over time, ready for a dashboard.
Top pathsThe most viewed pages on each site.
Sources, landing pages, and devicesChannels, landing pages, and device types, with how many people reached a key event.
Key eventsThe events you marked as key events in GA4, for the conversion and retention review.
Your AI agent can read GA4 too. See what it can ask.
How to connect it
01Press Connect with Google and sign in with an account that can see the property.
02Pick the GA4 property for each product. Read access only.
03Each property shows up as its own source, next to PostHog if you use both.
What LopeBase does with it
As a Viewer, LopeBase can only read reports. It never changes your Google Analytics setup.
Tracking that stoppedA site with no pageviews in the last 7 days is flagged. That usually means a tracking snippet broke in a deploy.
Key eventsPick one of your GA4 key events, and channels, landing pages, and devices show how many people reached it.
Readable by your agentOver MCP, an AI agent can read GA4 data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Google Analytics 4 questions
Something else? Contact us.
01Do I need a service account?
No. Connect with Google is the quick way. A service account still works if you would rather not use anyone's personal Google login.
02Do GA4 and PostHog numbers show together?
Yes. Both use the same field names inside LopeBase, so dashboards and Overview work the same with either.
03What access does LopeBase need in GA4?
Viewer on each property. With a service account, add its email as a Viewer; with Connect with Google, sign in with an account that can see the property.
Google Analytics MCP Connect GA4 to Claude, Codex, or Cursor over MCP. Your agent reads channels, landing pages, devices, and conversions for every property you run.Google Search Console See clicks, impressions, and rankings for all of your products' sites together in one view, and spot the one that dropped. Read-only access.PostHog Point LopeBase at your PostHog projects and see active users, pageviews, and top pages for every product on one screen, with read-only keys. Put Google Analytics 4 next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Honeybadger

URL: https://lopebase.com/connectors/honeybadger

See unresolved Honeybadger errors, daily occurrences, and the busiest errors for every product you run, next to its revenue, traffic, and uptime.

All connectors Honeybadger errors for every product, in one place.
See unresolved errors, occurrences per day, and the busiest errors, for each Honeybadger project, next to the rest of each product.
Connect Honeybadger free Your personal Honeybadger auth token. LopeBase lists your projects to pick from.
What LopeBase reads
Error summaryUnresolved errors per project, and occurrences in the last 24 hours for the busiest ones.
Busiest errorsThe open errors seen most in the last day, with class, message, and environment.
Daily occurrencesOccurrences per day for the busiest open errors over the last two weeks.
How to connect it
01Copy your personal auth token from your Honeybadger profile, under Authentication.
02Pick each property's project from the list LopeBase shows.
03Error totals and spikes show next to each product's revenue and traffic.
What LopeBase does with it
LopeBase only reads errors and occurrence counts. It never resolves, assigns, or changes anything in Honeybadger.
Errors beside revenueEach product's open errors sit on its row, next to its revenue and traffic, so a spike has context.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Honeybadger questions
Something else? Contact us.
01Which errors does it count?
Errors that are neither resolved nor ignored, the same as Honeybadger's default view.
02Why are daily counts limited to the busiest errors?
Honeybadger reports occurrences per error, so LopeBase adds up the 25 busiest open errors. Rare errors may be left out of the daily chart.
03Can I resolve errors from LopeBase?
No. The Honeybadger connector only reads. Resolve errors in Honeybadger.
Sentry Unresolved issues, error volume, and the loudest problems across all of your Sentry projects.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering.GitHub See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch. Put Honeybadger next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Mercury

URL: https://lopebase.com/connectors/mercury

See your Mercury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.

All connectors Cash in the bank, next to what you earn.
See your Mercury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.
Connect Mercury free Mercury Read Only token. It cannot move money.
What LopeBase reads
CashAvailable balance across accounts, and money in, money out, and net over the last 30 days.
AccountsEach account with its available and current balance. Account numbers are never shown.
TransactionsRecent transactions with counterparty, amount, and status.
How to connect it
01Create a Read Only API token in Mercury settings.
02Paste it once for the workspace.
03Cash and burn sit next to your Stripe revenue.
What LopeBase does with it
LopeBase only reads balances and transactions. A read-only token cannot move money.
Cash beside revenueBalances show on Revenue and Overview, next to MRR, and add up with any other bank you connect.
No account numbersAccount and routing numbers never show in the console.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Mercury questions
Something else? Contact us.
01Can LopeBase send payments?
No. The token is read-only, and the connector has no payment actions.
02Do you store my account numbers?
No. LopeBase never reads account or routing numbers into the console.
03Which Mercury token should I create?
An API token set to Read Only. It starts with secret-token: and cannot move money.
Brex See your Brex cash balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.Stripe Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row.MRR calculator Free MRR calculator for more than one SaaS product. Add plans per product, normalize yearly and quarterly billing, apply discounts, and see total MRR and ARR. Put Mercury next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Plausible

URL: https://lopebase.com/connectors/plausible

See pageviews, visitors, and top pages for each product's site in Plausible, next to its revenue, errors, and search clicks.

All connectors Plausible traffic next to everything else.
See pageviews, visitors, and top pages for each product's site in Plausible, next to its revenue and errors.
Connect Plausible free A Plausible Stats API key, which can only read. Self-hosted Plausible works too.
What LopeBase reads
Web analyticsPageviews and visitors over the last 7 and 28 days.
Daily pageviewsPageviews and visitors per day, for the trend on Analytics.
Top pagesThe most-viewed pages over the last 7 days.
Sources, entry pages, and devicesChannels, entry pages, and device types, with how many visitors reached your goal.
GoalsYour Plausible goals, for the conversion and retention review.
Your AI agent can read Plausible too. See what it can ask.
How to connect it
01In Plausible, open Account settings, API keys, and create a Stats API key.
02Paste it, then pick each product's site.
03Its traffic shows on Analytics and Overview, beside the other products.
What LopeBase does with it
Stats API keys can only read. LopeBase never changes anything in Plausible.
Tracking that stoppedA site with no pageviews in the last 7 days is flagged. That usually means a tracking snippet broke in a deploy.
GoalsPick a Plausible goal, and sources, entry pages, and devices show how many visitors reached it.
Readable by your agentOver MCP, an AI agent can read Plausible data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Plausible questions
Something else? Contact us.
01Does it work with self-hosted Plausible?
Yes. Set your Plausible address when you connect it.
02Are its numbers added to my other analytics?
No. Each source has its own row, since tools count visitors differently.
03How do I name each site?
Use the site's domain exactly as your Plausible dashboard lists it.
Plausible MCP Connect Plausible to Claude, Codex, or Cursor over MCP. Your agent reads goals, channels, entry pages, and devices for every site, self-hosted too.Cloudflare Web Analytics See pageviews, visits, and top pages from Cloudflare's free, cookieless Web Analytics for each product, next to its revenue, errors, and search.PostHog Point LopeBase at your PostHog projects and see active users, pageviews, and top pages for every product on one screen, with read-only keys. Put Plausible next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Polar

URL: https://lopebase.com/connectors/polar

See MRR, subscriptions, and 30-day revenue for each product that sells through Polar, on the same screen as the products that sell on Stripe.

All connectors Polar revenue next to everything else.
See MRR, subscriptions, and 30-day revenue for each product that sells through Polar, next to the ones on Stripe.
Connect Polar free Polar organization access token with read scopes only. Works with the Polar sandbox too.
What LopeBase reads
Revenue overviewGross and net revenue over the last 30 days. Net is after discounts, tax, and refunds.
SubscriptionsEvery live subscription with its monthly value and status, feeding MRR and the past-due check.
Recent ordersThe latest orders with product, amount, status, and why they were billed.
How to connect it
01Create an organization access token in Polar with subscriptions:read and orders:read.
02Paste it for each product that sells through Polar.
03MRR adds up across Polar and Stripe on one screen.
What LopeBase does with it
LopeBase only reads orders and subscriptions. It never changes anything in Polar.
Past-due subscriptionsA subscription that slips into past due is flagged under Needs attention for that product.
MRR across bothProducts on Polar and products on Stripe add up into one portfolio MRR.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Polar questions
Something else? Contact us.
01Does net include Polar's fee?
No. Net is after discounts, tax, and refunds, before Polar's own fee.
02Can I mix Polar and Stripe?
Yes. Connect each product to whichever one it sells through, and MRR adds up across both.
03Which scopes does the Polar token need?
subscriptions:read and orders:read. Nothing else.
Stripe Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row.MRR calculator Free MRR calculator for more than one SaaS product. Add plans per product, normalize yearly and quarterly billing, apply discounts, and see total MRR and ARR.vs ChartMogul LopeBase vs ChartMogul. ChartMogul is a revenue analytics platform. LopeBase shows MRR next to traffic, uptime, errors, and SEO for every product. Put Polar next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## PostHog

URL: https://lopebase.com/connectors/posthog

Point LopeBase at your PostHog projects and see active users, pageviews, and top pages for every product on one screen, with read-only keys.

All connectors PostHog analytics for every product, side by side.
Point LopeBase at your PostHog projects and see active users, pageviews, and top pages for every product on one screen.
Connect PostHog free Personal API key with read access. One-click PostHog OAuth is on the way.
What LopeBase reads
Web analyticsVisitors, pageviews, and weekly and monthly active users for each project.
Daily pageviewsA day-by-day series you can pin to a dashboard next to revenue and errors.
Top pathsThe pages that get the most views, per product.
Sources, landing pages, and devicesWhere visitors come from, where they land, and on what, with how many of each reached your goal.
Goals and funnelsYour signup or purchase events, and how many people go from a visit through each step in order.
Weekly retentionHow many new visitors came back a week and a month later, for the conversion and retention review.
ErrorsIf you use PostHog error tracking, exceptions from the last day, the top errors, and a daily count, next to Sentry's if you use both.
Your AI agent can read PostHog too. See what it can ask.
How to connect it
01Create a personal API key in PostHog with read access.
02Choose which projects to read and the host your projects live on.
03Each project shows up as its own source, rolled up on Overview.
What LopeBase does with it
LopeBase only runs read queries. It never changes your PostHog data or settings.
Tracking that stoppedA site with no pageviews in the last 7 days is flagged. That usually means a tracking snippet broke in a deploy.
Goals and funnelsSet a goal event and the sources, landing pages, and devices views count who reached it. Add funnel events in order to see each step.
Readable by your agentOver MCP, an AI agent can read PostHog data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
PostHog questions
Something else? Contact us.
01Does this replace PostHog?
No. Keep PostHog for deep analysis. LopeBase shows the numbers you check every day, next to revenue and errors from your other tools.
02Can I read projects in different PostHog regions?
Yes. Set the host for the projects you connect.
03Which scope does the PostHog key need?
A personal API key with the Query read scope, and the project ID from Project settings.
PostHog MCP Read PostHog retention, funnels, goal events, and traffic from your AI agent over MCP, for every project, next to your Search Console data.Google Analytics 4 Read the GA4 property for each of your products and compare traffic side by side, without switching between properties in Google Analytics.Plausible See pageviews, visitors, and top pages for each product's site in Plausible, next to its revenue, errors, and search clicks. Put PostHog next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Resend

URL: https://lopebase.com/connectors/resend

See bounce and complaint rates over your recent emails, what went out, and whether your sending domains are verified, for every product you run.

All connectors Know your emails actually arrive.
See bounce and complaint rates over your recent emails, what went out, and whether your sending domains are verified.
Connect Resend free Resend API key with Full access, since a Sending access key cannot read emails. LopeBase only reads and never sends.
What LopeBase reads
DeliveryDelivered, bounced, and spam complaints across your most recent 100 emails, with rates.
Recent emailsWhat went out, to whom, and where each one ended up.
DomainsEach sending domain and whether it is verified.
How to connect it
01Create a Resend API key with Full access.
02Paste it once, even if every product sends from the same account: each product counts only the emails from its own domain.
03A bounce spike shows up next to that product's signups and revenue.
What LopeBase does with it
Resend has no read-only key, and sending-only keys cannot read your emails. LopeBase only reads: it never sends email or changes your domains.
Delivery limitsResend can pause sending above a 4% bounce rate or 0.08% spam complaints. A product over either is flagged, and one within a quarter of a limit gets a warning.
Enough emails to judgeRates wait for at least 50 recent emails, so one bounce on a quiet day is not an alarm.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Resend questions
Something else? Contact us.
01Can LopeBase send email through Resend?
No. The Resend connector reads. Your product keeps sending as it does today.
02Why does it need a Full access key?
Resend only lets Full access keys read emails and domains. LopeBase never sends with it.
Sequenzy See your audience size, who joined recently, and which lifecycle sequences are actually running, and turn a sequence on or pause it.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering.LopeBase Adapter The LopeBase Adapter is a small handler inside your app. It shares only the records and actions you declare, over signed requests, and audits every change. Put Resend next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Rho

URL: https://lopebase.com/connectors/rho

See your Rho checking, savings, and treasury balances, money in and out over the last 30 days, and your recent transactions.

All connectors Rho cash next to your revenue.
See your Rho checking, savings, and treasury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.
Connect Rho free A Rho API access token. Rho's API is read-only.
What LopeBase reads
Cash summaryWhat is available across checking, savings, and treasury.
AccountsEach account and its balance. Account numbers are never shown.
TransactionsRecent money in and out, with who it was with.
How to connect it
01In Rho banking settings, create an API access token. Owners and admins can make one.
02Paste it once for the workspace.
03Cash shows on Revenue and Overview, beside MRR, and adds up with any other bank you connect.
What LopeBase does with it
Rho tokens are read-only: LopeBase can see balances and transactions, and cannot move money.
Cash beside revenueBalances show on Revenue and Overview, next to MRR, and add up with any other bank you connect.
No account numbersAccount and routing numbers never show in the console.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Rho questions
Something else? Contact us.
01Can LopeBase move money?
No. Rho's API is read-only.
02Is money in another currency added in?
No. It is listed beside your total, never added to it.
03Who can create a Rho token?
Only Owners and Admins. The token starts with rhobat_.
Mercury See your Mercury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.Wise See every Wise currency balance, money in and out over the last 30 days, and recent transactions, next to what each product earns.Stripe Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row. Put Rho next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Rollbar

URL: https://lopebase.com/connectors/rollbar

See active Rollbar items, daily occurrences, and the errors seen most recently for every product you run, next to its revenue, traffic, and uptime.

All connectors Rollbar errors for every product, in one place.
See active items, occurrences per day, and the errors seen most recently, for each Rollbar project, next to the rest of each product.
Connect Rollbar free A project access token with only the read scope, one per property.
What LopeBase reads
Error summaryActive items and occurrences in the last 24 hours, per project.
Recent errorsThe active items seen most recently, with level, environment, and their running total.
Daily occurrencesError-level occurrences per day for the last two weeks.
How to connect it
01In each property's Rollbar project, create a project access token with only the read scope.
02Paste it on that property's connection in LopeBase.
03Error totals and spikes show next to each product's revenue and traffic.
What LopeBase does with it
LopeBase only reads items and occurrence counts. It never resolves, mutes, or changes anything in Rollbar.
Errors beside revenueEach product's open errors sit on its row, next to its revenue and traffic, so a spike has context.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Rollbar questions
Something else? Contact us.
01Which token scope does it need?
Only read. Create a project access token in the project's settings and leave every other scope off.
02Why one token per property?
Rollbar's project access tokens each belong to one project, so each property's connection uses its own project's token.
03Can I resolve items from LopeBase?
No. The Rollbar connector only reads. Resolve items in Rollbar.
Sentry Unresolved issues, error volume, and the loudest problems across all of your Sentry projects.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering.GitHub See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch. Put Rollbar next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Google Search Console

URL: https://lopebase.com/connectors/search-console

See clicks, impressions, and rankings for all of your products' sites together in one view, and spot the one that dropped. Read-only access.

All connectors Search Console for every site, in one view.
See clicks, impressions, and rankings for all of your products' sites together, and spot the one that dropped.
Connect Google Search Console free Connect with Google in one click, read-only. A service account works too.
What LopeBase reads
Search performanceClicks, impressions, click-through rate, and average position per site.
Top queriesThe searches that bring people to each product.
Your AI agent can read Search Console too. See what it can ask.
How to connect it
01Press Connect with Google and sign in with an account that can see the property.
02Pick the Search Console property for each product. Read access only.
03Each site shows up as its own source.
What LopeBase does with it
As a Restricted user, LopeBase can only read search data. It never changes your Search Console settings.
The SEO screenClicks, impressions, click-through rate, and position for every site, with Bing beside it if you connect that too.
Topics for the content autopilotThe content autopilot picks article topics from the queries each site already shows up for.
Readable by your agentOver MCP, an AI agent can read Search Console data for every site with list_sources and read_source. See what it can read.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Google Search Console questions
Something else? Contact us.
01Can I connect domain properties?
Yes. List each Search Console property you want to read, domain or URL prefix.
02Does LopeBase submit sitemaps or change settings?
No. The Search Console connector only reads.
03What access does LopeBase need in Search Console?
Restricted user is enough. With a service account, add its email as a Restricted user; with Connect with Google, sign in with an account that can see the property.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Search Console MCP Give Claude, Codex, or Cursor your Search Console data over MCP: every query, page, and position for each site, so your agent can find SEO wins.Bing Webmaster Tools Bing also feeds ChatGPT search and Copilot. Read Bing Webmaster Tools data for every product's site, right next to Google Search Console.Content autopilot Plan articles on a calendar, draft them days ahead in your voice, check every one, and publish on schedule. Edit before or after it goes live. Put Google Search Console next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Sentry

URL: https://lopebase.com/connectors/sentry

See unresolved issues, error volume, and the loudest problems across all of your Sentry projects, on the same screen as the rest of each product.

All connectors Sentry errors for every product, before customers notice.
See unresolved issues, error volume, and the loudest problems across all of your Sentry projects.
Connect Sentry free Sentry auth token with read scopes. One-click Sentry sign-in is on the way.
What LopeBase reads
Error summaryUnresolved issues and events per project.
Top issuesThe noisiest issues, with level, culprit, and how many users they hit.
Daily eventsError volume over time, per project.
How to connect it
01Create a Sentry auth token with read access.
02List the projects to read, and your Sentry URL if you self-host.
03Error totals sit next to each product's revenue and traffic.
What LopeBase does with it
LopeBase only reads issues and events. It never resolves, assigns, or changes anything in Sentry.
Errors beside revenueEach product's unresolved issues sit on its row, next to its revenue and traffic, so a spike has context.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Sentry questions
Something else? Contact us.
01Does it work with self-hosted Sentry?
Yes. Set your Sentry URL.
02Can I resolve issues from LopeBase?
Not today. The Sentry connector reads. Resolve issues in Sentry.
03Which scopes does the Sentry token need?
project:read and event:read.
Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering.GitHub See open pull requests, open issues, and recent Actions runs for each product's repo, and spot a failing default branch.Cloudflare See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run. Put Sentry next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Sequenzy

URL: https://lopebase.com/connectors/sequenzy

See your audience size, who joined recently, and which lifecycle sequences are actually running, and turn a sequence on or pause it.

All connectors Your newsletter and sequences, at a glance.
See your audience size, who joined recently, and which lifecycle sequences are actually running, and turn a sequence on or pause it.
Connect Sequenzy free Sequenzy API key. Turning a sequence on always asks you to confirm first.
What LopeBase reads
AudienceActive, unsubscribed, and bounced subscribers, and how many sequences are running.
SequencesEvery sequence with its real state, including ones that look active but have enrollment paused.
Recent subscribersWho joined lately, their status, and their tags.
How to connect it
01Copy an API key from Settings, API keys in Sequenzy.
02Paste it for each product's Sequenzy company.
03Turn a sequence on or pause it from LopeBase. Every change lands in the audit log.
What LopeBase does with it
LopeBase reads your audience and sequences. It only changes something when you press Turn on or Pause on a sequence.
Confirmed changesTurning a sequence on asks you to type to confirm, and the audit log records who did it and when.
Sequences as they really areA sequence that looks active but has enrollment paused shows as paused.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Sequenzy questions
Something else? Contact us.
01Can a sequence start sending by accident?
No. Turning a sequence on asks you to type to confirm, and the change is recorded with who made it.
02Can I write campaigns here?
Not yet. Write and schedule campaigns in Sequenzy.
03What can LopeBase change in Sequenzy?
Only a sequence's state, when you press Turn on or Pause. Everything else is read.
Resend See bounce and complaint rates over your recent emails, what went out, and whether your sending domains are verified, for every product you run.EmDash CMS Read posts and categories from every EmDash site, check each one's SEO health, and publish new posts through a review gate, all from one console.Content autopilot Plan articles on a calendar, draft them days ahead in your voice, check every one, and publish on schedule. Edit before or after it goes live. Put Sequenzy next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Stripe

URL: https://lopebase.com/connectors/stripe

Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row.

All connectors Stripe revenue for every product, in one place.
Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row.
Connect Stripe free Restricted API key, read only. One-click Stripe OAuth is on the way.
What LopeBase reads
Revenue overviewMRR, active subscriptions, and 30-day gross and net volume, per account and summed across all of them.
Recent chargesAmount, status, currency, and customer email for the latest charges, so a failed payment is easy to spot.
SubscribersActive subscriber counts per account, next to each product's MRR.
How to connect it
01Create a restricted key in Stripe with read access to charges, customers, subscriptions, and balance. The link in the connect guide fills these in.
02Add one key per product, labeled with a short name like product-one.
03LopeBase checks the key and starts reading. Nothing in Stripe can be changed from the console.
What LopeBase does with it
LopeBase only reads charges, customers, subscriptions, and balances. It never charges, refunds, or changes anything in Stripe.
Past-due subscriptionsA subscription that slips into past due is flagged under Needs attention for that product.
One-time revenueGross charges over 30 days, less what paid subscription invoices took, so one-off sales show beside MRR.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Stripe questions
Something else? Contact us.
01Can LopeBase refund or change anything in Stripe?
No. The Stripe connector is read only. Changes to a customer run through actions your own product defines, like extending access or granting credits.
02Can I connect more than one Stripe account?
Yes. Add one restricted key per account. Each product keeps its own row, and Overview shows the combined MRR.
03Which permissions does the Stripe key need?
Read access to charges, customers, subscriptions, and balance. The link in the connect guide fills these in, so you only press Create key.
04How is net revenue worked out?
From Stripe's balance ledger over the last 30 days, after fees, refunds, and disputes.
Polar See MRR, subscriptions, and 30-day revenue for each product that sells through Polar, on the same screen as the products that sell on Stripe.How to track MRR across multiple Stripe accounts Running more than one product on separate Stripe accounts? How to add up MRR correctly, which keys to use, and the details that make totals wrong.MRR calculator Free MRR calculator for more than one SaaS product. Add plans per product, normalize yearly and quarterly billing, apply discounts, and see total MRR and ARR. Put Stripe next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Supabase

URL: https://lopebase.com/connectors/supabase

See each product's Supabase project health, advisor findings, disk, backups, edge functions, and API traffic in one place.

All connectors Supabase health next to everything else.
See each product's Supabase project health, security and performance advisor findings, disk, backups, edge functions, and API traffic.
Connect Supabase free A Supabase access token. LopeBase only ever reads with it.
What LopeBase reads
Project healthStatus, services that are down, disk used, the last backup, and point-in-time recovery.
Advisor findingsSecurity and performance findings from Supabase's advisors, with how to fix each.
Edge functionsEach function with its status and version.
BackupsRecent backups and whether each one finished.
API trafficRequests over the last 7 days to the database, auth, storage, and realtime.
How to connect it
01In Supabase, create an access token and name it LopeBase.
02Paste it, then pick each product's project from the list.
03Problems show under needs attention on Overview.
What LopeBase does with it
Supabase tokens cannot be limited to reading, so LopeBase limits itself: it only reads, and never changes a project, its settings, or its data.
Database healthA project that is not healthy, or a service that is down, is flagged. Disk 80% full warns, and 90% is flagged. So is a failed backup.
Advisor findingsSupabase advisor errors are flagged, and so are security warnings, with the first one named.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Supabase questions
Something else? Contact us.
01Can LopeBase change my database?
No. It reads project health and settings, never your data, and never writes.
02One token for every project?
Yes. A Supabase token reaches every project in your account, so connect it once and match each product to its project.
03Why does one token reach every project?
Supabase access tokens cover the whole account and cannot be limited to one project or to reading. LopeBase only ever reads with it.
Cloudflare See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.Sentry See unresolved issues, error volume, and the loudest problems across all of your Sentry projects, on the same screen as the rest of each product.Uptime checks LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering. Put Supabase next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Uptime checks

URL: https://lopebase.com/connectors/uptime

LopeBase checks each product's address every 15 minutes, records the status and response time, and flags any site that stops answering.

All connectors Know a product is down before a customer tells you.
LopeBase checks each product's address, records the status and response time, and flags any site that stops answering.
Start checking free No account or key needed. Just the addresses to check.
What LopeBase reads
StatusWhether the site answered, its HTTP status, and its response time.
Needs attentionA site that is down, or answers with an error, shows on the Overview.
How to connect it
01Add the address for each product. A health endpoint works best.
02LopeBase checks it every 15 minutes and keeps 30 days of history.
03A down site shows under needs attention with the error it returned.
What LopeBase does with it
Nothing to create and no key to share. LopeBase only requests the addresses you give it.
Down or slowA site that stops answering or returns an error is flagged. Slower than 3 seconds counts as degraded.
A year of historyStatus and response time for every check for 35 days, and uptime for each day for a year.
A public status pageFree on every plan, with your notes, an RSS feed, and a badge for your site.
AlertsAnything under Needs attention can reach you by email or browser push, so you hear about it without opening the console.
Uptime checks questions
Something else? Contact us.
01How often does it check?
Every 15 minutes, with a year of uptime history. It is not a paging service, so keep one if you need alerts at 3am.
02Can it check a private address?
No. LopeBase only checks public addresses.
03How long does a check wait?
Up to 10 seconds. A site that has not answered by then counts as down.
Sentry See unresolved issues, error volume, and the loudest problems across all of your Sentry projects, on the same screen as the rest of each product.Cloudflare See requests and errors for every Worker, the latest deploy for each, and your D1 databases, next to the products they run.Supabase See each product's Supabase project health, advisor findings, disk, backups, edge functions, and API traffic in one place. Put uptime next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Wise

URL: https://lopebase.com/connectors/wise

See every Wise currency balance, money in and out over the last 30 days, and recent transactions, next to what each product earns.

All connectors Wise balances next to your revenue.
See every Wise currency balance, money in and out over the last 30 days, and recent transactions, next to what each product earns.
Connect Wise free A read-only personal token from your Wise business account. It cannot send money.
What LopeBase reads
Cash summaryWhat is available, in each currency you hold.
BalancesEvery currency balance on the account.
TransactionsRecent money in and out, with who it was with.
How to connect it
01In your Wise business account, open API tokens and create a Read only personal token.
02Paste it once for the workspace.
03Cash shows on Revenue and Overview, beside MRR. Money in other currencies is listed beside your total, never added in.
What LopeBase does with it
LopeBase only reads balances and statements. A read-only token cannot send money.
Every currencyEach currency balance shows on its own. Money in other currencies is listed beside your total, never added in.
No account numbersAccount and routing numbers never show in the console.
A broken connectionIf a key is revoked or expires, the connector shows under Needs attention, so a gap in the numbers never goes unnoticed.
Wise questions
Something else? Contact us.
01Does it work for accounts based in the EU or UK?
Partly. Wise does not allow statements with a personal token for accounts based there, so transactions may not show.
02Can LopeBase move money?
No. The token is read only.
03Where do I create the token?
In your Wise business account, under Integrations and tools, API tokens. Choose Read only.
Mercury See your Mercury balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.Brex See your Brex cash balances, money in and out over the last 30 days, and recent transactions, next to what each product earns.Stripe Connect each product's Stripe account with a restricted, read-only key. LopeBase adds them up into portfolio MRR and shows each product on its own row. Put Wise next to everything else.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free All connectors

---

## Contact

URL: https://lopebase.com/contact

Send LopeBase a message about a question, a bug, billing, security, or a partnership. We read every one and reply by email, usually within a few days.

Get in touch.
A question, a bug, a billing issue, a security report, or a partnership idea. Send it below and a person reads it, not a bot.
Send us a message
We reply by email, usually within a few days.
Name
Email
Topic Choose one Question Bug report Billing Security Partnership Other
Message 0 / 5000 characters
Company
Send message Message sent
Send another message Questions
Getting in touch with LopeBase, in plain terms.
Something else? Contact us.
01Who reads these messages?
Someone on the LopeBase team, not a ticket queue. We reply from the email you wrote to.
02Is this the right place to report a security issue?
Yes. Choose "Security" as the topic and include enough detail to reproduce it. We reply by email once we have looked at it.
03I have a billing question. Will this reach the right person?
Yes. Choose "Billing" and mention your workspace name or the email on the account, so we can find it quickly.
04Can I email you directly instead of using the form?
The form is the fastest way to reach us, and it sorts your message by topic before anyone reads it.
Or just start free and see for yourself.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Content autopilot

URL: https://lopebase.com/content-autopilot

Plan articles on a calendar, draft them days ahead in your voice, check every one, and publish on schedule. Edit before or after it goes live.

A blog for every product, on a calendar you run.
Plan topics onto dates. LopeBase drafts each article days ahead in your voice, checks it, and publishes it on time to your site. Review every post first, or let it run.
Start free See the workflow Set up per product. Uses the AI credits in your plan, or your own AI key.
The whole workflow, in six steps
Set it up once per product. After that, the calendar fills itself and you step in where you want to.
01Pick where articles go. A blog LopeBase hosts for you, your app through a signed webhook, WordPress, Ghost, Webflow, Shopify, Contentful, Sanity, Strapi, Hashnode, an EmDash blog, a GitHub pull request, or copy and paste.
02Describe the voice. LopeBase drafts it from your site and imports your existing posts so it never repeats them. You edit anything that is off.
03Gather topics. From Search Console, search suggestions, and your own keywords. Plan any of them onto a date.
04Set the schedule. How many posts a week, which days, what hour, your time zone, and how many days ahead to draft.
05Review or let it run. Drafts wait for you, or publish on their own when every check passes.
06Watch the results. Clicks, impressions, and rankings come back per article from Search Console.
Calendar
See the month. Plan the month.
Every product gets a calendar of what went out, what is scheduled, and the open slots ahead.
OctoberPublishedScheduledNeeds reviewOpen MonTueWedThuFriSatSun 28 29Keeping docs in step with code 30 1How to review a docs pull request 2 3 4 5 6Docs drift: 7 signs and fixes 7 8Changelogs people actually read 9 10 11 12 13Planned: api reference templatesDrafted Sun, Oct 11 14 15Open: best topic ideaDrafted Tue, Oct 13 16 17 18 Slots from your schedulePosts a week, on which days, at what hour, in your time zone. One slot a day at most.
Drafts written aheadEach article is drafted up to 14 days before its date, so there is time to read it.
Plan a topic for a datePut a topic idea on any open slot. Otherwise the best idea is used when the draft is due.
Write a slot nowDraft any open slot straight away instead of waiting for its day.
Move an articleShift it to another open slot, or clear its date so it goes out as soon as it is approved.
Nothing runs awayOne draft at a time per product, and a slot that fails twice is skipped instead of retried forever.
Voice
It writes like your site, because it reads your site first.
LopeBase drafts the voice from your homepage and posts. Every setting stays yours to change.
AudienceEngineers who maintain docs TonePractical, specific, plain House rulesNever invent statistics.Mention the product in one section only. Never write aboutNews roundups, release notes Length1,200 to 2,200 words FAQ sectionLink your postsEditor passNo dashesYouTube video ImagesDiagrams, made and placed in the article Audience and toneWho the articles are for and how they should sound.
House rules and off-limits topicsRules every draft follows, and subjects it never touches.
Length and FAQA word range, and an FAQ section at the end if you want one.
Example posts and extra instructionsYour best posts to match, and anything else in your own words.
Internal linksLinks to your existing posts, checked to be real pages.
ImagesUp to three per article in the style you pick: photo, illustration, diagram, or screenshot ideas, with alt text.
A relevant videoOne real YouTube video where it helps, found for the topic and checked.
An editor passA short AI review: does it sound like your site, and does it answer the search.
Where topics come from
Ideas are scored and checked against everything already written, so two articles never chase the same search.
Search ConsoleSearches your site already shows up for but rarely gets clicked on.
Search suggestionsWhat people type around your keywords.
Your keywordsThe terms you give it, drafted from your site to start.
Your coding agentTopics and full drafts from an agent working in your product's repo.
The checks before anything goes out
On autopilot, only a draft that passes all of them publishes. Anything else waits for you.
The basicsLength within your range
Title 20 to 70 characters
Meta description 70 to 160 characters
Clean URL slug
Not already published
StructureAt least 4 sections
No top-level heading in the body
Has an FAQ section, when asked for
Plain Markdown, no raw HTML
Honesty and styleNo filler phrasing
Every statistic has a source link
Not an off-limits topic
No em or en dashes, when asked for
Links and fitEvery link opens
Links to your site go to real pages
Links to at least one of your posts
Videos are real ones found for the topic
Sounds like your site, and answers the search well
Review and edit
Read it first. Fix it after.
Every draft opens as an editable preview, with its checks beside it. Publishing is not the end of editing.
Docs drift: 7 signs and fixes Length 1,200 to 2,200 words
Every statistic has a source link
Links to at least one of your posts
Approve for Tue, Oct 13, 9:00 AMOr publish nowApprove Edit, then approve for its date
Change the title, description, or body in place. Saving re-runs the checks. Approve early and it waits for its slot, or send it now.
POST /api/lopebase/articles{  "event": "article.update",  "article": { "slug": "keeping-docs-in-step", ... }} Save and update the live postSame address, new textUpdate Edit after it is live
Fix a published article in LopeBase and the change goes to your site. Its address stays the same, so links keep working.
Where it publishes, and how edits follow
Hosted by LopeBaseA blog for each product with nothing to set up: themed pages, RSS, a sitemap, and a JSON feed your own site can show. It can also send each article to your app.Edits are live at once WebhookA signed webhook to an endpoint in your product. LopeBase gives your coding agent the prompt that builds it, for any stack.Edits arrive as article.update GitHubA pull request adding the article as Markdown, for blogs kept in the repo. Merging publishes it.Edits open a pull request Your CMSWordPress, Ghost, Webflow, Shopify, Contentful, Sanity, Strapi, or Hashnode, through each one's own API with your token. Test the connection before anything publishes.Edits update the same post EmDashStraight to a blog in your own Cloudflare account, with images as image blocks.Edits update the same post Copy and pasteApproved articles wait as Markdown, ready for any CMS.Copy again What you see afterwards
Faster indexingWhen your app takes articles by webhook and serves an IndexNow key, search engines hear about each new post as it goes live.
Per articleClicks, impressions, and average rank from Search Console, refreshed daily once a post has been live a couple of days.
Per productThe calendar and a library of everything written, with its status and where it went.
Who signed offEach article keeps who approved it, when it went out, and where it lives.
Questions
How the content autopilot behaves, in plain terms.
Something else? Contact us.
01Do I have to publish what it writes?
No. In review mode every draft waits for you. You can edit it, approve it, or reject it. Autopilot mode publishes drafts that pass every check on the schedule you set; anything that fails a check waits for you.
02How far ahead does it write?
As far ahead as you choose, from the same day up to 14 days. A draft written three days early gives you three days to read it before its slot.
03Can I choose the topic for a specific day?
Yes. On the calendar, plan any topic idea onto an open slot. When that slot's draft is due, it is written about that topic. Slots without a plan get the best idea at the time.
04Can I edit an article after it is published?
Yes. Edit the title, description, or body and save. A webhook site receives the change as article.update with the same id and slug, a CMS or EmDash blog gets the same post updated, and GitHub gets a pull request that edits the file. The address stays fixed so existing links keep working.
05Where do the topics come from?
From Search Console queries your site already shows up for but gets few clicks on, from what people type into search around your keywords, and from the keywords you give it. Ideas that overlap an article you already have are dropped.
06Which AI model writes the drafts?
By default, LopeBase's own AI access, paid for with the AI credits included in your plan. You can add your own OpenAI-compatible key instead, and then drafts use no credits.
07Can my own coding agent write the articles?
Yes. Through the LopeBase MCP server, an agent can read a product's content profile, ask for the next topic, and submit a draft, with a date if it should go on the calendar. The draft goes through the same checks and review.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Agents and MCP Let your coding agent set up products and write drafts.Search Console Where the topics and results come from. What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 03 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 04 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 05 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Give every product a blog that keeps up.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Docs

URL: https://lopebase.com/docs

How to set up LopeBase, connect your tools, read every page, and fix what goes wrong. Step by step guides with links straight into the app.

How can we help?
Setup guides, what every page in LopeBase shows, and fixes for the things that go wrong. Each guide links straight to the right screen in the app.
Search the docs, like "reconnect Stripe" or "status page" / PopularGet started with LopeBaseConnect your toolsUptime checks and incidentsConnect an agent over MCPFix a connection that needs reconnecting
Get started
Your first product, your first connection, and what Overview tells you.
Get started with LopeBase
Set up from your terminal
Add and manage properties
Read Overview
Connections
Bring in the tools you already use, add the adapter, and count pageviews.
Connect your tools
Connect Search Console and Google Analytics
Connect Stripe and Polar
Install the LopeBase Adapter
Count pageviews with LopeBase
Grow
SEO, content, discussions, traffic, revenue, and users.
Use the SEO toolkit
Plan and publish with the content autopilot
Find discussions about your product
Read Analytics and traffic
Track MRR and revenue
See your users
Run
Uptime, status pages, alerts, pipelines, and dashboards.
Uptime checks and incidents
Publish a status page
Alerts and the weekly email
Automate with pipelines
Build dashboards
Agents and AI
Set up from a terminal, connect Claude over MCP, and AI credits.
Connect an agent over MCP
AI reviews and credits
Workspace and billing
Teammates, the audit log, plans, and how your data is handled.
Invite your team
Read the audit log
Plans, trial, and billing
How LopeBase handles your data
Troubleshooting
Fixes for the problems people hit most, in one place.
Fix a connection that needs reconnecting
Troubleshooting
Reading this with an AI agent?
Every article has a plain Markdown copy at the same address plus .md, and llms.txt lists them all. Point your agent at llms-full.txt to read the whole site in one fetch, or connect it to LopeBase itself over MCP.

---

## AI reviews and credits

URL: https://lopebase.com/docs/ai-credits

How AI credits work in LopeBase, what uses them, how to see where they went, buy more, and bring your own AI key instead.

Docs Agents and AI AI reviews and credits
How AI credits work in LopeBase, what uses them, how to see where they went, buy more, and bring your own AI key instead.
Updated October 8, 2026 3 min read Open AI credits Copy as Markdown Writing an article, running an SEO audit, reviewing your revenue, and a few other features in LopeBase use AI. Most plans pay for that with AI credits: a credit costs one cent, and each AI run uses credits based on how much work the AI model did. You can also connect your own AI provider key and skip credits entirely.
What uses credits
Anything that asks an AI model to read your numbers or write something uses credits. That includes:
Writing, rewriting, or improving an article draft (Content)
The SEO audit, and suggestions like competitor finding or keyword cleanup
The revenue, traffic, and incident reviews, and the weekly briefing
Discussions searches, which look for where people talk about your product
AI reports and pipeline steps that call AI
Reading your numbers on Overview, SEO, Analytics, Revenue, and Uptime never uses credits. Only the AI buttons do, and each one shows its estimated cost before you click it.
Runs keep going in the background
Once you start an AI run, an article draft, an audit, a review, or a pipeline, you can leave the page or close the tab. It keeps running and shows as running when you come back. When it finishes, a toast with a View button appears wherever you are in LopeBase, at the bottom right on a computer and above the tab bar on a phone, once per run. If you have LopeBase open in more than one tab, it shows once, in whichever tab you are looking at.
Your balance
Your plan includes a monthly allowance of credits that resets on the first of each month (UTC). See what is left any time:
Go to SettingsAI credits, or Open AI credits.
The page shows how many of your included credits are used this month, a daily chart of the last 30 days, and a breakdown of what each feature cost. For the full history, open Usage from the same page; it covers the last 90 days and links to what each run made.
Buying more
If you run out of included credits, buy a pack. Packs do not expire, and are spent only after your monthly allowance runs out.
On a trial? Subscribing to any paid plan before it ends adds 500 bonus credits once, automatically, on top of the plan's own allowance. See the trial for how it works.
Bring your own AI key
Connect your own OpenAI or Anthropic key and LopeBase stops using credits for your workspace entirely; every AI feature still works, billed straight to your own account instead.
Go to ManageConnections, or Connect your AI key.
Your key is stored encrypted and used only for your workspace's AI calls. See How LopeBase handles your data for how connection keys are stored.
Where to go next
Plans, trial, and billing for how many credits each plan includes.
Content for what an article actually costs to write.
Connect Claude and other agents over MCP: an agent's drafts and topic searches use credits the same way.
If something goes wrong
Something else? Contact us.
01Why did an AI button stop working
You are most likely out of credits for the month. The button's cost note says so, and Settings, AI credits shows your balance. Buy a pack, wait for next month's reset, or connect your own AI key.
02Why does my estimate not match what I was charged
The estimate is a range shown before you run something. What you are charged comes from what the AI model actually used for that specific run, which can land anywhere in that range.
03I connected my own key but credits are still being used
Check that the key is still connected and valid on Connections. If LopeBase cannot reach your key, it falls back to nothing rather than charging credits silently, so a run that used credits after you added a key usually means the key was not saved or was removed.
04Do unused credits roll over
Your monthly allowance does not roll over; it resets to the plan's amount each month. Purchased packs are different: they carry over and are only spent after the monthly allowance is gone.
PreviousConnect an agent over MCP NextInvite your team Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
What uses creditsRuns keep going in the backgroundYour balanceBring your own AI keyWhere to go nextIf something goes wrongView as Markdown

---

## Alerts and the weekly email

URL: https://lopebase.com/docs/alerts

Turn on browser and email alerts, choose what counts as serious, and set up the weekly summary email. How LopeBase decides when to tell you something.

Docs Run Alerts and the weekly email
Turn on browser and email alerts, choose what counts as serious, and set up the weekly summary email. How LopeBase decides when to tell you something.
Updated October 8, 2026 4 min read Open alert settings Copy as Markdown LopeBase checks your properties every 15 minutes and tells you once when something starts, once more only if it gets worse, and once when it is fixed, never on every check. Alerts can reach you in this browser, in any other browser you turn them on in, and by email. A separate weekly email sums up the numbers.
Turn on alerts
Open alert settings
Open alert settings
Turn on this browser
Click Turn on in this browser and allow notifications when your browser asks. Alerts then show even when LopeBase is closed. Turn on each other browser or device the same way, from inside it; there is no way to turn one on from another.
Check email alerts
Email is on by default, to the address you sign in with. Everything that changed goes in one email, at most every 15 minutes, not one email per problem.
On an iPhone or iPad, add LopeBase to your home screen first and open it from there. Safari in a regular tab cannot show alerts.
How serious, and about what
Choose Needs action to hear only about what is broken or blocking, like a site down or a failing build. Choose Also worth a look to add early signs too, like a bounce rate near Resend's limit or a subscription past due. Reviews waiting for you and status page updates always count, whichever you pick.
Then pick which kinds of problem you want to hear about:
KindCovers Sites and services downA site stops answering, a connection breaks, or a database is unhealthy. Builds and errorsA build failing on your main branch, Workers failing requests, database advisor errors. PaymentsSubscriptions going past due. Email deliveryBounces or spam complaints near Resend's limits. Traffic stoppedNo pageviews arriving for a week. Your app's own warningsWhat your app's LopeBase Adapter flags. Reviews waitingA pipeline or articles waiting for your OK. Status page updatesA teammate posts or edits a note on a public status page. Turn on "When it is fixed" to hear a short note once something that alerted is back to normal. If you run more than one property, pick which ones you want to hear about; a new property is included unless you choose a specific set.
Use Send a test alert at the bottom to see one land in every place you have turned on, without waiting for something to actually break.
The weekly summary email
A separate email, under SettingsEmail, sends your numbers once a week on the day and time you choose, in your own time zone.
Open weekly summary settings Pick what it includes: the numbers (MRR, signups, active users, pageviews, with change from last week), what needs attention, one row per property, traffic by source, and team activity. Click Send me a preview to see one right away.
The notification bell
The bell icon, in the sidebar and in the top bar on a phone, shows a small dot when anything is waiting. Click it to open Notifications, which lists two kinds of notice: a newer version of your LopeBase Adapter, and a connection that has stopped refreshing. Filter the list to one property, or leave it on all of them.
Mark a notice Done once you have dealt with it, or Dismiss it if it does not matter to you; either moves it out of the list. Show done brings back what you have cleared, with a Move back button on each one. What you clear is yours alone: a teammate sees their own list, not what you dismissed. This is separate from push and email alerts: it is always there, with no settings to turn on.
If something goes wrong
Something else? Contact us.
01I turned alerts on but never get a push notification
Check the browser you expect alerts in is still listed under alert settings as on; a browser can lose its subscription after it is reset or notifications are blocked. Site settings next to the address bar show whether LopeBase is allowed to notify.
02Why didn't I hear about something that was clearly down?
Check the category it falls under is turned on, and that the property it belongs to is in your picked list. A short blip under about an hour also never alerts, so it does not catch brief hiccups.
03I'm getting too many alerts
Switch from "Also worth a look" to "Needs action," or turn off a category you do not need. "Also worth a look" is meant to be noisier; most people leave it on "Needs action."
04The weekly email arrived at the wrong time
Check the time zone on the Email tab: it defaults to a fixed zone until you pick your own, and the day and hour apply to the zone shown there.
05Can someone else on my team get their own alerts?
Yes. Alerts and the weekly email are per operator, so each person signed into the workspace sets their own browsers, categories, and schedule.
PreviousPublish a status page NextAutomate with pipelines Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Turn on alertsHow serious, and about whatThe weekly summary emailThe notification bellIf something goes wrongView as Markdown

---

## Read Analytics and traffic

URL: https://lopebase.com/docs/analytics

Compare PostHog, GA4, Plausible, Cloudflare, and LopeBase's own pageviews side by side, see top pages, and get an AI review of conversion and funnels.

Docs Grow Read Analytics and traffic
Compare PostHog, GA4, Plausible, Cloudflare, and LopeBase's own pageviews side by side, see top pages, and get an AI review of conversion and funnels.
Updated October 8, 2026 3 min read Open Analytics Copy as Markdown Analytics reads visitors and pageviews from whichever tool each property uses, plus the users and signups each app reports about itself. Connect more than one traffic source and they sit side by side, never added together, since each one counts differently.
Go to GrowAnalytics, or Open Analytics.
Compare your traffic sources
Connect any of PostHog, Google Analytics (GA4), Plausible, or Cloudflare Web Analytics; each property can use a different one. With no property picked, every property's traffic shows as one row per source: pageviews for the last 7 and 28 days, weekly and monthly visitors, and a sparkline trend. A source that does not report a number, like Cloudflare Web Analytics counting visits rather than unique visitors, shows "Not reported" for it instead of a wrong zero.
Pick one property to see its totals, the trend against the days before, top pages for each connected source, and, further down, two counters LopeBase reports on its own:
Pageviews counted by LopeBase. The property's own cookieless counter: no cookies, no visitor IDs, and most ad blockers that hide other tools leave it running. If no tag is installed yet, a snippet and a ready-to-paste agent prompt are right there to add it.
From the LopeBase Adapter. Users, signups in the last 7 days, and active users in the last 28, read straight from the property's own database.
AI review of conversion and funnels
Two AI reviews sit under the traffic numbers once at least one source has data, each for the whole workspace or one property:
ReviewWhat it does Traffic reviewReads visitors this week against last, top pages, search clicks, and signups, then says what is driving traffic, what is slipping, and which pages to work on. Conversion and retentionLines up every connected source with Search Console, billing, and the app's own numbers: where visitors come from, which pages they land on, how many sign up or buy, how many come back, and where tracking breaks. Each finding shows the numbers behind it, each step names the number it should move, and you can track a step to see on the next review whether that number moved. Both use AI credits, or your own AI key, and the button shows the cost before you run it.
Where to go next
Set up LopeBase's own pageview counter for the cookieless numbers shown here.
Connect Google Analytics or Search Console.
Track MRR and revenue for what those visitors turn into.
If something goes wrong
Something else? Contact us.
01Why don't my visitor numbers from two tools match?
They are never added together on purpose. PostHog counts people across every event, Cloudflare Web Analytics counts visits rather than unique visitors, and GA4 and Plausible each have their own rules. Each row names its service so you know whose numbers you are reading.
02Why does a source show "Not reported" for visitors?
Some tools do not report that number at all, most commonly Cloudflare Web Analytics for weekly and monthly visitors. "Not reported" means the source never sends it, not that it is zero.
03Why are there no numbers from the LopeBase Adapter?
That section reads users, signups, and active users straight from the property's own database through its LopeBase Adapter connection. Connect it on the property's page if you have not yet.
04Why hasn't LopeBase's own pageview counter shown anything?
It needs its tag added to the site first; copy the snippet or the agent prompt under Pageviews counted by LopeBase. Numbers show up about a minute after the first real visit.
05Why does the Conversion and retention review need credits or a key?
It runs on AI to compare every connected source and write its findings. Connect your own AI key to use that instead of credits; either way the cost shows before you run it.
PreviousFind discussions about your product NextTrack MRR and revenue Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Compare your traffic sourcesAI review of conversion and funnelsWhere to go nextIf something goes wrongView as Markdown

---

## Read the audit log

URL: https://lopebase.com/docs/audit-log

Every change made in your workspace, with its before and after, who made it, and how to filter and export the audit log.

Docs Workspace and billing Read the audit log
Every change made in your workspace, with its before and after, who made it, and how to filter and export the audit log.
Updated October 8, 2026 2 min read Open Audit Copy as Markdown Every change made through LopeBase, connecting or removing a source, inviting a teammate, writing and publishing an article, running an SEO audit, and more, lands on the audit log with its before and after. It is the record of who did what, and when.
Open the audit log
Go to ManageAudit, or Open Audit.
With a property picked in the sidebar, the feed narrows to that property's events plus workspace-wide ones, like connecting an app or changing an operator's role. Clear the property focus to see everything.
Filter and export
Filter by connector, action, actor, or a date range, then press Filter. The Connector, Action, and Actor lists only show values that actually appear in your log, so you are never filtering against something that was never recorded.
Export the current filter as CSV or JSON from the buttons above the list, for your own records or to hand to an accountant or auditor.
How far back you can see
Your plan sets how much history the audit feed shows:
PlanAudit history shown FreeLast 30 days StudioLast 365 days PortfolioFull history AgencyFull history Older events are never deleted by a shorter plan. They are kept and come back into view the moment you move to a plan with a longer window.
Where to go next
Invite your team to see what each role is allowed to do.
Plans, trial, and billing for every plan's audit retention.
If something goes wrong
Something else? Contact us.
01I can't find an old event
Your plan may only show a limited window of history. The audit page says how many days your plan shows, with a link to see plans if you need more.
02The audit log is empty
Nothing has changed yet, or your property focus in the sidebar is hiding everything. Clear the focus, or connect a property if you have not yet.
03An event shows a connector name I don't recognize
Connector names in the log use the pattern service@product, like stripe@acme. The part after the @ is the property it belongs to.
PreviousInvite your team NextPlans, trial, and billing Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Open the audit logFilter and exportHow far back you can seeWhere to go nextIf something goes wrongView as Markdown

---

## Plans, trial, and billing

URL: https://lopebase.com/docs/billing

What each LopeBase plan includes, monthly or yearly billing, how the free trial works, what happens when it ends, and how invite rewards work.

Docs Workspace and billing Plans, trial, and billing
What each LopeBase plan includes, monthly or yearly billing, how the free trial works, what happens when it ends, and how invite rewards work.
Updated October 8, 2026 5 min read Open Billing Copy as Markdown LopeBase prices by how many products you connect, not by seat or by feature. A new workspace starts on a 14 day trial of the Portfolio plan, no card needed, then settles onto whichever plan fits.
The plans
PlanMonthlyYearlyProductsOperatorsAudit historyAI credits a month Free$0$01130 days50 Studio$29/mo$290/yr33365 days500 Portfolio$99/mo$990/yr1010Full history2,000 Agency$299/mo$2,990/yrUnlimitedUnlimitedFull history8,000 A product counts once no matter how many sources it has connected. Workspace-wide connections, like your own AI key or a shared bank account, never count against the product limit. Need more credits than your plan includes? Buy a pack or bring your own AI key; see AI reviews and credits.
Pay yearly and get two months free
Every paid plan can be billed monthly or yearly. Yearly costs ten months' worth, so Studio is $290 a year (about $24 a month), Portfolio $990 (about $83 a month), and Agency $2,990 (about $249 a month). The plan is the same either way: same products, operators, audit history, and AI credits, and credits still reset on the first of each month.
Open Billing
Go to Billing, or Open Billing.
Pick Yearly
Use the Monthly and Yearly switch above the plans. Each plan shows its yearly price and what that comes to per month.
Choose a plan
Checkout opens with the yearly price. Once payment goes through, the plan applies within a minute.
Your current plan shows how it is billed and when it renews. If a plan has no Yearly option on the switch yet, it is available monthly only for now.
The trial
A new workspace gets every Portfolio feature for 14 days with no card on file. If you choose a plan before the trial ends, that plan takes over right away. Otherwise the workspace moves to Free automatically.
Pick Studio, Portfolio, or Agency from the pricing page before you even sign up, and your workspace opens Billing already set to that plan once it is ready.
Partway through the trial, and always in its final week, admins see a short summary on Overview: what the workspace has connected and used so far, and which of that would actually be affected by moving to Free, with a button to upgrade and how many days are left. Closing it brings it back after a few days rather than for good.
Subscribe to any paid plan, monthly or yearly, before your trial ends and you get 500 bonus AI credits, once, on top of what the plan includes. Billing shows the offer while your trial is running, and confirms it after you upgrade.
When a plan does not have room
If your trial ends, or you move to a smaller plan, and you have more products connected than the plan allows, LopeBase does not delete anything. The products you connected first, up to the plan's limit, keep updating. The rest pause: their settings and history are kept, but their numbers stop refreshing until you choose a plan with room for them, which turns them all back on at once.
Go to Billing, or Open Billing.
Billing lists exactly which products are paused, if any.
If a payment fails
A past-due invoice does not lock you out: everything you already have keeps working, but adding a new connector, operator, or dashboard is paused until the invoice is settled. If it stays unpaid, the workspace is suspended: reads still work, but every change is blocked until billing is restored.
Changing or cancelling a plan
Paid plans renew at the end of each month or year, depending on how you pay. To move to another plan, or to switch between monthly and yearly billing, open Manage subscription on the Billing page; the change is handled there on the secure billing portal.
You can cancel any time from Manage subscription. A cancelled plan runs to the end of the period you already paid for, a month or a year, then the workspace moves to Free; nothing you connected is deleted.
Invite a friend, get a free month
Share your invite link and the workspace that joins through it gets its own trial, then its first paid month free. Once they make their first payment, your next month is free too, with no cap on how many times this can happen.
Go to Invite, or Open Invite.
Where to go next
AI reviews and credits for what is included and how to add more.
Read the audit log for how retention changes by plan.
Invite your team for how the operator limit works.
If something goes wrong
Something else? Contact us.
01My product stopped updating after my trial ended
It is most likely paused because your plan does not have room for every product you connected. Billing lists which ones are paused; choose a plan with enough room and they turn back on right away.
02I can't connect a new source or add a teammate
Check Billing for a past-due or suspended notice. Existing connections keep working during a past-due invoice, but adding anything new is paused until it is settled.
03I don't see a Yearly option
The Monthly and Yearly switch only appears when yearly billing is available for at least one plan, and a plan without a yearly price shows "Monthly billing only for now". If you already pay, switch to yearly from Manage subscription on Billing instead of starting a new checkout.
04I upgraded but don't see my 500 bonus credits
They are added once your payment is confirmed, which can take up to a minute after checkout, and only when you subscribed before your trial ended. Check Settings, AI credits for your balance; if your trial had already ended when you subscribed, the bonus does not apply.
05I cancelled but I'm still being charged
A cancelled plan runs through the end of the month or year you already paid for, then moves to Free. If a charge lands after that, check Manage subscription on Billing, or reach out from the docs page's contact link.
06My referral reward never showed up
The free month applies once the workspace you referred makes its first payment, not when they sign up. Check their status on your Invite page; it says Signed up until they convert.
PreviousRead the audit log NextHow LopeBase handles your data Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
The plansPay yearly and get two months freeThe trialWhen a plan does not have roomIf a payment failsChanging or cancelling a planInvite a friend, get a free monthWhere to go nextIf something goes wrongView as Markdown

---

## Connect Search Console and Google Analytics

URL: https://lopebase.com/docs/connect-google

Connect with Google in one click for Search Console and Google Analytics: which account to use, how LopeBase picks the right property, and common errors.

Docs Connections Connect Search Console and Google Analytics
Connect with Google in one click for Search Console and Google Analytics: which account to use, how LopeBase picks the right property, and common errors.
Updated October 8, 2026 3 min read Open Connections Copy as Markdown Search Console and Google Analytics both connect the same way: one Google sign-in, read-only, with the property picked for you when there is an obvious match. This covers both, since the steps and the problems are the same.
Connect with Google
Open the connection
From a property's page or Connections, open Google Search Console or Google Analytics and choose Connect with Google.
Open Connections
Pick the Google account
Use whichever Google account already has access in Search Console or Google Analytics for that site. If you manage several products with different Google accounts, make sure you are signed in to the one that owns this property's data when Google's sign-in screen appears.
Grant read-only access
Google shows exactly one scope: read Search Console data, or read Google Analytics data. As a Restricted user (Search Console) or Viewer (Analytics), LopeBase can only read; it never changes your settings.
Pick the property
LopeBase lists properties under two headings: "Matches this product" (its address matches what the property is set up with) and "Other properties on this Google account". Pick one and press Use this property.
Which Google account to use
LopeBase connects by account, not by property on Google's side, so the account you sign in with has to be one that already has access to the right Search Console property or Analytics property. If you are not sure, check in Search Console or Google Analytics directly before connecting; adding the service account there first, under a different flow, is only needed for the older key-based setup, not for Connect with Google.
Common errors
No properties listed
This means the Google account you signed in with has no verified Search Console property, or no Google Analytics property with a web stream, for that site yet. For Search Console, add a Domain property for the site's domain; if its DNS is on Cloudflare, Search Console can verify it in one step, otherwise add the TXT record it shows, then come back and check again. For Analytics, make sure the property has a web data stream on that domain.
Connected, but it's the wrong account's data
Sign out of Google (or use a private window) and connect again, choosing the correct account when Google asks which one to use. There is a direct link to connect a different account right from the page that shows no matching properties.
Google access was not granted
If you close Google's consent screen, or untick the Search Console or Analytics permission on it, nothing is connected and LopeBase says access was not granted. Start the connection again and leave the one permission it asks for checked.
The sign-in did not finish, or took too long
Both show as plain errors on the property's page. Just start the connection again; nothing from a failed attempt is saved.
Where to go next
Connect your tools for every other kind of connection.
SEO for what Search Console feeds once it is connected.
Reconnect a connection if Google later revokes access.
If something goes wrong
Something else? Contact us.
01Search Console or Analytics says "no properties listed"
Verify a Domain property for the site in Search Console, or add a web data stream to the Analytics property, with the Google account you are connecting. Then reconnect; LopeBase checks again each time.
02It connected, but shows another site's numbers
You were signed in to the wrong Google account, or picked the wrong property from the "Other properties" list. Open the connection and connect a different account, or pick the right property from the list.
03It says Google access was not granted
You likely closed Google's permission screen, or unchecked the one permission it asked for. Start the connection again and allow it.
04Only a workspace admin can connect Google
That's by design: connecting any source is an admin-only action. Ask a workspace admin to connect it.
PreviousConnect your tools NextConnect Stripe and Polar Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Connect with GoogleWhich Google account to useCommon errorsWhere to go nextIf something goes wrongView as Markdown

---

## Connect Stripe and Polar

URL: https://lopebase.com/docs/connect-stripe

Connect Stripe or Polar with a restricted, read-only key, for one property or several accounts, and see where MRR comes from when a property reports none.

Docs Connections Connect Stripe and Polar
Connect Stripe or Polar with a restricted, read-only key, for one property or several accounts, and see where MRR comes from when a property reports none.
Updated October 8, 2026 2 min read Open Connections Copy as Markdown Stripe and Polar both feed MRR, subscriptions, and revenue onto Revenue and Overview. Stripe connects with a restricted key you create yourself; Polar with an organization access token. Neither can move money, refund a charge, or change anything in your account.
Connect Stripe
Create a restricted key
Open the connection and use the link to Stripe's key creation page. It pre-fills the key's name and sets Charges, Customers, Subscriptions, and Balance to Read for you.
Open the Stripe connection
Create the key and copy it
Press Create key in Stripe, then copy the key. It starts with rk_live_, never sk_live_; a secret key can do anything in your account, a restricted key only what you set to Read.
Paste it in and pick the property
Paste the key, then connect it for the right property, or choose All my properties if one Stripe account covers more than one.
Not sure which permissions a dashboard like this needs from Stripe? The Stripe read-only key builder lists the exact ones to set to Read for LopeBase, or for any other tool you connect.
Connect Polar
Create an organization access token
In Polar, open Settings and create an access token with the subscriptions:read and orders:read scopes.
Paste it in
Paste the token and connect it for the right property, the same way as Stripe.
Several accounts
If you run more than one product on separate Stripe or Polar accounts, connect each account for the property it belongs to. If you later add a key for a Stripe account that lists a different property's website or business name, LopeBase warns you before saving, with a one-click way to move it to the right property instead.
Where MRR comes from
When a property's own app does not report MRR itself (through the LopeBase Adapter), Overview, dashboards, the weekly email, and your AI agent all take it from that property's connected Stripe or Polar account instead, in its own currency. One-time payments from the last 30 days show on their own, separate from recurring MRR, so neither one hides inside the other.
Where to go next
Revenue for what Stripe and Polar feed once connected.
Connect your tools for every other kind of connection.
Reconnect a connection if a key is later revoked.
If something goes wrong
Something else? Contact us.
01Revenue shows n/a even though Stripe is connected
Check that the key's permissions include Invoices if you expect one-time revenue; a key missing a permission LopeBase needs shows that one number as not reported rather than guessing.
02It warns that this Stripe account belongs to another property
LopeBase checks whose account a key belongs to by its website, business name, or statement descriptor. If it is actually right for this property, confirm that on the warning; if not, use the one-click option to move it to the correct property.
03I pasted a secret key instead of a restricted one
Create a restricted key instead and connect that. Never paste a key starting sk_live_ into any tool, LopeBase included.
04One Stripe account covers several of my products
Connect it once, then choose All my properties so every product on that account is covered without pasting the key again.
PreviousConnect Search Console and Google Analytics NextInstall the LopeBase Adapter Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Connect StripeConnect PolarSeveral accountsWhere MRR comes fromWhere to go nextIf something goes wrongView as Markdown

---

## Connect your tools

URL: https://lopebase.com/docs/connections

Every kind of connection LopeBase reads, grouped by what it does, how each one connects, and what its health states mean once it is running.

Docs Connections Connect your tools
Every kind of connection LopeBase reads, grouped by what it does, how each one connects, and what its health states mean once it is running.
Updated October 8, 2026 4 min read Open Connections Copy as Markdown Connections are how LopeBase learns about a property: its traffic, its search performance, its money, its errors, and more. Every connection reads, and nothing it reads can change anything in the tool itself unless this page says otherwise for that one.
Open Connections Pick what to connect
Connections groups every tool by what it is for. Open a tile to connect it: most either open a one-click sign-in, or show the steps to create a read-only key in that service, with a link that pre-fills the right name and permissions where the service supports it.
GroupToolsWhat it reads LopeBase AdapterYour own appUsers, signups, plans, and anything else you declare. See Install the LopeBase Adapter. ContentEmDash CMSYour blog, so LopeBase can draft, review, and publish posts. AnalyticsPostHog, Google Analytics, Plausible, Cloudflare Web AnalyticsPageviews, visitors, traffic sources, and (PostHog and Google Analytics) funnels and retention. SearchGoogle Search Console, Bing Webmaster ToolsOrganic impressions, clicks, and the queries bringing people to your site. MoneyStripe, Polar, Mercury, Brex, Rho, WiseMRR, subscriptions, and revenue (Stripe, Polar), or balances and transactions (the banks). MonitoringSentry, Rollbar, Honeybadger, Bugsnag, Better Stack, plus uptime checksOpen errors, daily error counts, and whether a site or monitor is up. EmailResend, SequenzyBounce and complaint rates (Resend), audience size and running sequences (Sequenzy). InfrastructureGitHub, Cloudflare, SupabasePull requests and Actions runs, Workers and deploys, project and database health. AIYour AI providerNot read from; it is the key LopeBase uses to draft content and run reviews. A few also show up under Monitoring for what they report there too: GitHub's failing Actions runs, Cloudflare's Worker error rates, PostHog's own error tracking, and Supabase's service health.
Read-only, with the few exceptions said plainly
Almost everything here only reads. Where a key or sign-in could also change something, the connect dialog says so: Sequenzy can turn a sequence on or pause it when you press that button yourself, and EmDash only creates or publishes the posts you approve. Nothing connects with write access by accident; where a service's own keys cannot be limited to reading, like Resend or Supabase, LopeBase still never uses the extra access.
Linking a connection to your properties
Most tools are connected once per property, since each property usually has its own PostHog project, Stripe account, or GitHub repo. When a tool's key can see more than one project or site, like PostHog, Sentry, GitHub, and Supabase, LopeBase lists what it can see and lets you match each one to a property, or connect All my properties at once from a single key. Reusing an existing key for a second property, rather than pasting it again, is offered automatically.
Connection health states
Once connected, a tool shows one of a few states, wherever its status appears:
StateWhat it means Working / Updated recentlyIts last read succeeded and the numbers are current. Last refreshed a while agoNothing has failed, but the numbers are older than usual, often because nothing new has happened yet. FailingA real error, not just a slow or busy service. LopeBase waits before showing this, so a brief blip never shows as failing. Needs reconnectingThe service itself confirmed the key or sign-in no longer works. A Reconnect link appears next to its numbers. A service that is simply busy or rate-limiting LopeBase is never reported as failing; LopeBase waits and reads it again on the next pass.
Don't see a tool you use
Every group on Connections ends with a card to ask for a tool LopeBase does not connect yet. Name it, its website, and what you would want from it, and it comes straight to the team building LopeBase.
Where to go next
Connect Search Console and Google Analytics for the most common first connections.
Connect Stripe and Polar for revenue.
Reconnect a connection if one needs it.
If something goes wrong
Something else? Contact us.
01A connection shows as failing but the service is up
LopeBase only reports a connection as failing after a real error, and waits out brief blips before alerting you. If it is still failing after a while, the key or sign-in itself may no longer have the access it needs; open the connection and check its permissions.
02It says a connection needs reconnecting
The service itself told LopeBase the key or sign-in no longer works, often because it was revoked or expired on the service's side. Press Reconnect next to it and go through the same steps again.
03I connected a tool for the wrong property
Open that connection from the property it is wrongly attached to and connect it again for the right one. For a tool whose key covers several projects or sites, you can also just add the missing property under the same key instead of starting over.
04A key my provider calls "read-only" still shows a write warning
A small number of services, like Resend and Supabase, have no way to limit a key to reading. LopeBase still only ever reads with those keys; the note is just saying the key itself is capable of more than LopeBase uses.
05I don't see the tool I want to connect
Use the "Missing a tool" card at the end of any group on Connections to ask for it directly.
06There is a small icon on the LopeBase Adapter card
It means at least one property is running an older @lopebase/adapter than the latest release. Open the card for a list of which properties, what the newer version adds, and buttons to copy the update command and a prompt for your coding agent. See Install the LopeBase Adapter.
PreviousRead Overview NextConnect Search Console and Google Analytics Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Pick what to connectRead-only, with the few exceptions said plainlyLinking a connection to your propertiesConnection health statesDon't see a tool you useWhere to go nextIf something goes wrongView as Markdown

---

## Plan and publish with the content autopilot

URL: https://lopebase.com/docs/content

Set up voice and schedule once, let LopeBase draft, check, and publish articles, and review what is waiting on the calendar.

Docs Grow Plan and publish with the content autopilot
Set up voice and schedule once, let LopeBase draft, check, and publish articles, and review what is waiting on the calendar.
Updated October 8, 2026 5 min read Open Content Copy as Markdown Content writes articles for a property on a schedule, in its own voice, and checks each one before it goes out. You stay in control: nothing publishes until you approve it, unless you turn autopilot on.
No property set up yet? Open Content and pick a property to see both setup paths.
Set up a property
Open GrowContent, pick the property, and choose where its articles go first: hosted by LopeBase, an EmDash blog, a webhook to your own endpoint, a GitHub pull request, a CMS (WordPress, Ghost, Webflow, Shopify, Contentful, Sanity, Strapi, or Hashnode), or copy and paste. Then pick how to finish setup:
Set it all up with AI (recommended)
Reads the site and its existing posts, fills in the voice, audience, and house rules, picks keywords and topics, sets a schedule that matches the blog's pace, and writes a first article, fixing it against the checks until it passes. You end on a summary with that article ready to review.
Set it up yourself
Go through Voice, Topics, and Schedule one step at a time. Each step can still fill itself in with AI (for example, "Fill in from yoursite.com" on Voice) if you want the help without the full run.
Voice, rules, and checks
Voice has five tabs, all saved together:
TabCovers VoiceWho it is for, its tone, and one plain sentence on what the product does. RulesHouse rules, one per line, every draft follows them; topics to never write about; an optional no em or en dash rule. Each articleWord count range, whether it ends with an FAQ, whether it links to your own posts, cites other sites, or suggests a YouTube video, and anything else the writer should know. ImagesStyle (none, photo, illustration, diagram, or screenshot), how many per article, and shape. Images never carry text or logos and use AI credits unless you supply your own key. ChecksWhether an editor check runs before publishing, and how many rounds of automatic fixing a failing draft gets. Every article, with or without the editor check, is checked for: length inside your range, a title 20 to 70 characters, a meta description 70 to 160 characters, a clean URL slug that is not already published, at least 4 sections, no top-level heading in the body, clean Markdown with no broken links or unclosed code fences, no filler phrasing, a source link on every statistic, and nothing from your avoid list. Turning on the editor check adds whether it sounds like the site, reads like a person wrote it, makes no invented claims, and answers the search it targets, using a few AI credits. A draft that fails a check is fixed automatically up to the rounds you set, then goes to review either way if it still fails.
Schedule and review mode
Set how many articles a week and on which days, the hour and time zone to publish, and how many days ahead to write the draft so there is time to review it. Pick one of two modes:
You review each one. Drafts wait on the Content page; nothing goes out until you approve it.
Autopilot. Articles that pass every check publish on their own. Anything that fails waits for you.
Turn on email alerts for a draft ready for review, an article published, or something that failed, sent to every admin by default or to addresses you choose.
The calendar
Each property's calendar shows the month with its scheduled slots, drafted articles, and open slots still needing a topic. Open Content, pick the property, then Calendar.
An open slot can be planned with a topic idea, written right away with Write now, or left for its scheduled day.
A scheduled or drafted article can move to another open slot, or be cleared to publish as soon as it is approved instead of on a fixed date.
Review and publish
Articles waiting on you show under Needs your review on the Content page, with how many of their checks pass. Open one to read it, see each check, and approve, reject, or ask for a rewrite. An approved article publishes to the destination you set up: a hosted LopeBase blog with its own RSS, JSON feed, and sitemap; an EmDash blog post, with an IndexNow ping to tell search engines right away; a signed webhook call to your own endpoint; a GitHub pull request; or your CMS of choice. A published article's clicks, impressions, and position from Search Console show on the Content page once it has been live a few days, and you can read every post across your sites on Posts on your sites.
The library
Posts on your sites (under Content) lists what is on the blog for every connected content destination, whatever its status: draft, in review, scheduled, or published, with word count, reading time, and author where the connector reports them.
Where to go next
Use the SEO toolkit turns a search opportunity straight into a topic here.
Connect the LopeBase Adapter if you chose the webhook destination and need the receiving endpoint.
Automate multi-step work covers running content tasks as part of a larger pipeline.
If something goes wrong
Something else? Contact us.
01Why is my draft stuck in review when autopilot is on?
Autopilot only publishes an article once every check passes. If one still fails after the fixing rounds you allowed, it waits for you instead, so nothing broken goes out on its own.
02Why can't I turn on "Set it all up with AI"?
AI setup reads the property's site, so it needs the site's address added on the property's page first. Add it there, then come back to Content.
03Why does writing an article need an AI key or credits?
Drafting, the editor check, and images all use AI. Connect your own OpenAI key or a Cloudflare AI Gateway to use that, or spend LopeBase AI credits; either way, the credit estimate shows before you write.
04Why did my article fail the "statistic needs a source" check?
Any percentage, multiplier (like "3x"), or "N times more/less" phrase needs a link to its source in the same paragraph. Add the link, or remove the figure if you cannot source it.
05Why didn't my article publish to EmDash or my CMS?
Use Test connection on the destination step after saving its settings. A common cause is a credential that changed on the other end, like an expired CMS token or a GitHub app no longer installed on that repository.
06Can I write about a specific topic right now instead of waiting for the schedule?
Yes. Use Write now on the Content page or from an open slot on the calendar, with or without a topic in mind.
PreviousUse the SEO toolkit NextFind discussions about your product Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Set up a propertyVoice, rules, and checksSchedule and review modeThe calendarReview and publishThe libraryWhere to go nextIf something goes wrongView as Markdown

---

## Build dashboards

URL: https://lopebase.com/docs/dashboards

Read the four ready-made dashboards, switch between properties, and compose your own from any chart LopeBase can build. How the numbers stay fresh.

Docs Run Build dashboards
Read the four ready-made dashboards, switch between properties, and compose your own from any chart LopeBase can build. How the numbers stay fresh.
Updated October 8, 2026 3 min read Open Dashboards Copy as Markdown A dashboard is a set of charts for one property, or combined across all of them. LopeBase ships four, and you can compose your own from any chart it knows how to build.
Open Dashboards The four built-in dashboards
DashboardNeedsShows OverviewAny propertyMRR, one-time revenue, active users, content queue, signups, and subscription mix. RevenueA subscription or MRR sourceMRR, one-time revenue, and subscription status. Content & SEOA connected blog or posts sourcePublished posts, the content queue, articles by status, and target SEO keywords. AnalyticsA web analytics connectionPageviews, weekly active users, the daily pageviews trend, traffic sources, devices, and top pages. A dashboard nothing feeds yet sits under Waiting on a source on the index page, saying what it needs. Open it anyway and LopeBase shows you how to connect that source.
Reading one
Each dashboard's card on the index already shows its headline numbers and a trend or status breakdown, so you can read the important ones without opening anything. Open a card for the full board.
With more than one property connected to the same dashboard, a switcher at the top lets you look at one property or combine them all; combining counts each property once even if two of its connections measure the same thing. A property measured by two services, like PostHog and Google Analytics, gets its own small switch between them.
Every page says when its numbers were last updated, with a Refresh button beside it. Dashboards read numbers LopeBase already keeps rather than asking every connected service on every page load, so a service is only asked again when you actually ask it to refresh.
Build your own
Start a new dashboard
New dashboard, at the top of the Dashboards page, walks you through three steps.
Pick where the numbers come from
Choose a property, or an analytics source if the charts you want are analytics-only.
Pick the charts and their order
Add any chart from the full list and arrange them in the order you want them to read.
Name it
Give it a name and save. It shows on Dashboards with a Custom badge, and you can edit or remove it later.
Composing and saving a custom dashboard needs the capability to edit dashboards and a database to save it to. Without a database, the four built-in dashboards still work.
If something goes wrong
Something else? Contact us.
01Why does a dashboard say it needs a source I think I already connected?
Check the connection is attached to the right property, not just present in the workspace. A connection with no property, like a bank account, can still feed a dashboard that combines every property, but not one scoped to a single property.
02A number on my dashboard looks stale
Dashboards show stored numbers, updated on their own schedule, not a live read on every visit. Click Refresh to ask the services behind it again; the "Updated" line under the charts shows how old what you are looking at is.
03Can I delete one of the four built-in dashboards?
No, but you can build a custom one next to it with just the charts you want, and ignore the built-in one.
04Why is "Combine" missing from the property switcher?
It only shows when more than one property feeds that dashboard. With just one connected, there is nothing to combine yet.
PreviousAutomate with pipelines NextConnect an agent over MCP Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
The four built-in dashboardsReading oneBuild your ownIf something goes wrongView as Markdown

---

## How LopeBase handles your data

URL: https://lopebase.com/docs/data-and-privacy

How connection keys are encrypted, why most connections are read-only, and how to export or delete your workspace's data.

Docs Workspace and billing How LopeBase handles your data
How connection keys are encrypted, why most connections are read-only, and how to export or delete your workspace's data.
Updated October 8, 2026 3 min read Open Your data Copy as Markdown LopeBase holds the keys that let it read your other tools: Stripe, Search Console, your database, and more. Here is how those keys are protected, what LopeBase actually does with them, and how to export or delete your data whenever you want.
How connection keys are stored
Every key or token you connect is encrypted before it is saved, with its own one-time encryption key, which is itself wrapped under a key specific to your workspace. Nobody reads a stored key back to you, in the app or over the MCP server; LopeBase only uses it to call the service you connected it to.
Read-only by default
Connecting a tool to LopeBase is read-only unless a page says otherwise. LopeBase fetches your numbers; it does not change anything in Stripe, Search Console, your database, or any other connected tool. The few actions that do write somewhere, like publishing an article to your CMS, say so plainly before you turn them on, and an MCP agent cannot use a tool that writes without you approving a token for it (see Connect Claude and other agents over MCP).
Sign out everywhere
Sign out everywhere, in the account menu, asks you to confirm and then ends your session on every device and browser, including the one you are using. Anywhere still signed in lands on the sign-in page the next time it loads a page, and needs a fresh sign-in to get back in.
Export your data
Download everything in your workspace as one JSON file: the workspace itself, its operators, every connector by name (never the keys), dashboards, saved views, pipeline runs, and the full audit log.
Go to SettingsYour data, or Open Your data.
Delete your data
Three different things can be deleted, and they are not the same:
Delete a property. Removes one product and everything LopeBase keeps for it: its connections and keys, uptime history, status page, and SEO and content data. The rest of the workspace is untouched. See Delete a property.
Delete your account. Removes you from every workspace, ends all your sessions, and deletes your sign-in. Workspaces you belonged to keep their audit history of what you did, but your account itself is gone.
Delete the workspace. Closes it right away: nobody can sign in, and any paid plan is cancelled. After 14 days it is removed for good, along with every operator who belongs only to it, every stored connector key, dashboards, and the audit log. Until then, every admin gets an email with a link to undo it.
Deleting a workspace cannot be undone after the 14 day window closes. Export your data first if you want to keep a copy.
Send feedback or write a review
Click Feedback at the bottom of the sidebar to tell us how LopeBase is working for you. A person on our team reads every note.
To leave a review, open Feedback and click Write a review. Pick a star rating, write a sentence or two, and add your name, role, and company if you want them shown. LopeBase may also ask for a review after you do something like publish a status page or approve an article. It asks at most once every 14 days, and never again once you write one or click Don't ask again.
We only use a review on our website if you tick OK to share this publicly. Otherwise only our team reads it.
The legal details
For the full privacy policy, see app.lopebase.com/legal/privacy.
Where to go next
AI reviews and credits for bringing your own AI key instead of using LopeBase's.
Invite your team for who in your workspace can see what.
If something goes wrong
Something else? Contact us.
01Can LopeBase staff see my connection keys
No. Keys are encrypted at the moment you save them and are never shown back to anyone, in the app or through the API. LopeBase uses them only to call the service you connected.
02I deleted my workspace by mistake
Check your email for the undo link sent to every admin when the workspace was closed. It works for 14 days after deletion; after that the workspace and everything in it is gone for good.
03My export is missing my connector keys
That is expected. The export lists each connector by name so you know what was connected, but never includes the stored key or token itself.
PreviousPlans, trial, and billing NextFix a connection that needs reconnecting Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
How connection keys are storedRead-only by defaultSign out everywhereExport your dataDelete your dataSend feedback or write a reviewThe legal detailsWhere to go nextIf something goes wrongView as Markdown

---

## Find discussions about your product

URL: https://lopebase.com/docs/discussions

Search Reddit, X, Hacker News, and other forums for threads about the problem your product solves, and track what you have replied to.

Docs Grow Find discussions about your product
Search Reddit, X, Hacker News, and other forums for threads about the problem your product solves, and track what you have replied to.
Updated October 8, 2026 2 min read Open Discussions Copy as Markdown Discussions searches public forums for recent threads about the problem your property solves, even ones that never mention it by name, so you have somewhere to reply. It is new and still being tuned: which threads it finds, and how well they fit, will keep improving. Nothing is ever posted from here; you follow the link and reply yourself.
Go to GrowDiscussions, or Open Discussions.
Find threads
Pick a property, then press Find threads (or Find more threads on a later run). It searches Reddit, X, Indie Hackers, Hacker News, Product Hunt, and Stack Overflow for threads from the last year that fit what the property does, picked by a cheap AI model so you only see ones worth your time. A thread already found is never shown twice. The button shows its credit cost before you run it; it needs an AI key or LopeBase AI credits.
What to look for
Under the thread list, What to look for holds the phrases the search looks for, like the problem your product solves or the category it is in. Add or edit these yourself, or have AI suggest some from the property's site.
Work through what it finds
Threads sort into three views:
ViewWhat it means NewFound and not yet acted on. RespondedYou replied, or plan to; marked by you. Not relevantMarked by you as not worth a reply. Later searches steer away from threads like it. Each thread shows where it was posted and when, with an Open on [platform] button that takes you straight to it to reply in your own voice. Mark it responded or not relevant once you have decided; marking it moves it immediately and saves in the background.
Where to go next
Use the SEO toolkit, whose Links tab shows posts that already mention your site by name; Discussions finds the ones that do not yet.
Manage your properties to add a property before searching for its discussions.
If something goes wrong
Something else? Contact us.
01Why didn't Find threads find anything?
Discussions is still being tuned, and a narrow or unusual product space can come up short. Try adding a few more phrases under What to look for, closer to how people actually describe the problem, then search again.
02Why do some threads not seem relevant to my product?
Threads are picked by an AI model matching your topics, so fit varies. Mark a bad match as not relevant; later searches learn to steer away from threads like it.
03Why does finding threads need an AI key or credits?
The search and the matching both run on AI. Connect your own key to use that, or spend a few LopeBase AI credits; the button shows the cost first.
04Can I undo marking a thread not relevant or responded?
Yes. Open that view and use the button to move it back to New.
PreviousPlan and publish with the content autopilot NextRead Analytics and traffic Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Find threadsWhat to look forWork through what it findsWhere to go nextIf something goes wrongView as Markdown

---

## Get started with LopeBase

URL: https://lopebase.com/docs/getting-started

Create your workspace, add your first property, connect a tool, and turn on alerts. The first ten minutes in LopeBase, step by step.

Docs Get started Get started with LopeBase
Create your workspace, add your first property, connect a tool, and turn on alerts. The first ten minutes in LopeBase, step by step.
Updated October 8, 2026 2 min read Open LopeBase Copy as Markdown LopeBase reads the tools each of your products already uses, like Search Console, Stripe, and your analytics, and shows them together. This guide gets your first product on Overview. It takes about ten minutes, and nothing you connect can change anything in those tools: connections are read-only unless a page says otherwise.
Have a coding agent like Claude Code or Cursor? Run npx lopebase in your project folder and the agent does most of this for you. See Set up from your terminal.
Your first ten minutes
Create your workspace
Sign up at app.lopebase.com/signup with Google, GitHub, or your email. You get every feature free for 14 days with no card, then the Free plan keeps one product running.
Add your first property
A property is one product or site you run. Give it a name and its web address. LopeBase uses the address to fetch the icon and to match the connections you add later to the right property.
Open Properties
Connect your first tool
Go to ManageConnections and pick a tool. Search Console and Stripe are good first choices: one shows how people find you, the other what they pay. Most connect with a sign-in or a read-only key in a couple of minutes.
Open Connections
Turn on alerts in this browser
In SettingsAlerts, allow browser alerts so you hear when a site goes down or a payment fails. Email alerts are on by default.
Open alert settings
Read Overview
Numbers start landing on Overview within a few minutes. The setup checklist at the top ticks itself off as you go, so you always know what is left.
Words you will see
WordWhat it means WorkspaceYour account. It holds your properties, connections, and teammates. You can belong to more than one. PropertyOne product or site you run. Every number in LopeBase belongs to a property. ConnectionA tool LopeBase reads from, like Stripe or Search Console, linked to one or more properties. OperatorA person in your workspace. Every change an operator makes is on the audit log. Where to go next
Connect your tools covers every kind of connection and how to pick the right one.
Uptime checks starts watching your site every 15 minutes, with no key needed.
Invite your team when you want someone else to see the numbers.
NextSet up from your terminal Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Your first ten minutesWords you will seeWhere to go nextView as Markdown

---

## Install the LopeBase Adapter

URL: https://lopebase.com/docs/lopebase-adapter

Mount the LopeBase Adapter at /api/lopebase to share your own app's users and numbers, watch the services it depends on, and keep it updated.

Docs Connections Install the LopeBase Adapter
Mount the LopeBase Adapter at /api/lopebase to share your own app's users and numbers, watch the services it depends on, and keep it updated.
Updated October 8, 2026 4 min read Open Properties Copy as Markdown Every other connection reads a tool around your product. The LopeBase Adapter is the one piece that reads your own app: its users, its own dashboard numbers, and the services it depends on. It is a small handler you add at /api/lopebase, published as @lopebase/adapter, and it answers only with what you declare. LopeBase never touches your database directly.
Add it
Copy the agent prompt
On the property's page, the LopeBase Adapter card has a Copy agent prompt button. Paste it into your coding agent in that product's repo.
Let your agent install it
It adds @lopebase/adapter, declares the resources you want visible (users, subscriptions, whatever fits), and creates a signing secret. It runs on Cloudflare Workers, Node 18 and up, Vercel, Netlify, Deno, and Convex, with no dependencies.
Deploy, then connect it
After deploying, enter the adapter's URL (usually your site's address followed by /api/lopebase) and the signing secret on the property's page. LopeBase tests it before saving.
Running npx lopebase in the product's repo does all of this for you. See Set up from your terminal.
Watching the services it depends on
The adapter can also list what your app cannot work without: a database, a job queue, a second API, an email sender. Each one is a check your app runs with its own credentials and the cheapest authenticated call available, like a database's select 1, Stripe's balance.retrieve, a GET /app to GitHub with the app's own JWT, or an AI provider's GET /models, never a ping to the vendor's own status page or root address. Point the product's uptime check at /api/lopebase/health and the Uptime page shows every service on its own, with alerts that name the one that failed.
A service you mark critical: false shows as degraded, still answering 200, instead of reporting the whole product down when it fails, useful for something your app can run without for a while, like an AI provider.
For a second host your own app runs, like a worker or an internal API, httpCheck makes this easy: give it the URL and it is healthy whenever that host answers below 500, sending a User-Agent header some hosts require. It is only for hosts you own; a third-party vendor's address still needs a real credentialed call.
cachedCheck, for services with a rate limit
Wrapping a service check in cachedCheck keeps a successful result for 60 seconds and a failed one for only 10, so frequent uptime polls do not use up that service's API limit, while a service that comes back up still shows that within seconds rather than waiting out the full minute.
The health endpoint
GET /api/lopebase/health is the one unauthenticated path: it answers with each declared service's name and whether it is up, never an error message or anything from your data. It answers 503 when a critical service is down, and 200 with status: "degraded" when only non-critical ones are.
Keeping it updated
When a newer version of the adapter is out, LopeBase shows it in your notifications, and the LopeBase Adapter card on Connections carries a small icon for the same reason. Open that card to see which properties are behind, what the newer version adds, and copy buttons for the update command and a prompt for your coding agent. Run npx lopebase update in the product's folder: it finds the adapter, shows what changed since your version, and hands the upgrade to your coding agent, which asks before each change.
Where to go next
Set up from your terminal to install it with your coding agent, end to end.
Uptime checks and alerts for how service checks feed Uptime.
Count pageviews with LopeBase for the separate tag that counts visitors, with or without the adapter.
If something goes wrong
Something else? Contact us.
01Connecting the adapter fails the test
Check that the URL ends in /api/lopebase and that the deployment is live, and that the signing secret pasted in matches the one your agent generated. The adapter is tested before anything is saved, so nothing half-connects.
02A service shows as down but I know it is fine
Check what the service's check actually calls: it should use your app's own credentials for a cheap authenticated call, not a vendor's root address or status page, which can fail or rate-limit for reasons that have nothing to do with your integration.
03One flaky service keeps marking the whole product down
Mark that service critical: false in the adapter's config, so its failure shows as degraded instead of reporting the product itself as down.
04Uptime checks are using up my API's rate limit
Wrap that service's check in cachedCheck, which keeps a result for a short while instead of calling the API on every poll.
PreviousConnect Stripe and Polar NextCount pageviews with LopeBase Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Add itWatching the services it depends oncachedCheck, for services with a rate limitThe health endpointKeeping it updatedWhere to go nextIf something goes wrongView as Markdown

---

## Connect an agent over MCP

URL: https://lopebase.com/docs/mcp-server

Add LopeBase to Claude, Cursor, or any MCP client at one address. Sign in, pick a workspace, and read health, metrics, and search data.

Docs Agents and AI Connect an agent over MCP
Add LopeBase to Claude, Cursor, or any MCP client at one address. Sign in, pick a workspace, and read health, metrics, and search data.
Updated October 8, 2026 5 min read Open Agent setup Copy as Markdown LopeBase runs an MCP server at app.lopebase.com/api/mcp. Point Claude, Cursor, or any other MCP client at it and the agent can see how your products are doing, read your search and analytics data, and help set up new connections, all while it works in your code.
Connect an agent
Most agents, including Claude.ai, Claude Code, and Cursor, can sign in to a remote MCP server on their own. Add the address and they open a LopeBase page to approve it.
Using Claude? LopeBase is listed in Claude's connector directory. Find it there and connect in a couple of clicks, no address to copy.
Find LopeBase in the Claude directory
Add the address
For Claude Code, run this in a terminal:
claude mcp add --transport http lopebase https://app.lopebase.com/api/mcp For Claude.ai, Cursor, or another client with a remote MCP setting, add this as an HTTP server:
https://app.lopebase.com/api/mcp
Approve the sign-in
The agent opens an "Allow access" page in your browser. Sign in if you are not already, and press Approve. Only a workspace admin can approve. If you belong to more than one workspace, LopeBase asks which one before it opens the approval; if you were partway through creating an account, it picks up this step once you finish.
Start working
The agent now has its own token for this workspace, good for 30 days. Ask it something like "what needs attention across my products" to try it.
Already run npx lopebase in a product's folder? It adds the MCP server to your agent and signs it in for you, no separate setup needed. See Set up from your terminal.
For agents that only take a token
Some agents cannot open a browser to sign in. For those, create an agent token instead.
Open Agent access
SettingsAgent access Open Agent access
Name it, set how long it lasts, and what it can do
Give it a label like "Claude Code", an expiry of 1, 7, 30, or 90 days, and the scopes it needs (see below). Press Create agent access.
Copy the command or the token
LopeBase shows a ready-to-run command for Claude Code, and the raw token for anything else: add it as an HTTP MCP server with the header Authorization: Bearer  token . The token is shown once; copy it before you close the dialog.
Every call acts as the admin who created the token, and LopeBase checks again each time that they are still an admin of the workspace. If that person loses admin rights, the token stops working. Revoke a token from the same screen at any time.
What a token can do
A token carries one or more scopes, and only sees the tools its scopes allow.
ScopeLets the agent SetupAdd products, connect sources and the adapter, run onboarding, write and submit content drafts. ReadRead health, metrics, the weekly digest, and search and analytics data. Never changes anything. ManageDisconnect a source. The most sensitive scope; grant it only if the agent needs to remove connections. list_products works on any scope, since knowing what exists is harmless on its own.
What an agent can do
Setup tools act for you: adding a product, connecting a source, or handing you a step only you can do.
ToolWhat it does list_products, get_productList your products and what each has connected. add_productAdd a product by name and site address. connect_sourceConnect an SEO, analytics, revenue, or uptime source to a product, tested live before it is saved. connect_adapterConnect the product's own LopeBase Adapter once it has been added. detect_stack, get_onboarding_statusWork out what a project uses, and what to set up next for it. get_setup_guideThe full setup guide for one product, including which services deserve an uptime check. get_pageview_snippet, get_pageviewsTurn on LopeBase's own cookieless pageview counter, and confirm it is working. get_content_profile, next_article_topic, submit_draftWrite an article in a product's voice and send it through the same checks and review as LopeBase's own drafts. request_human_action, list_human_actions, resolve_human_actionHand you a step it cannot do itself, like a sign-in or a payment, and track it until it is done. disconnect_sourceRemove a product's connection to a source. Needs the manage scope. Read tools only ever return numbers, never a stored key or personal data.
ToolWhat it does get_healthWhat needs attention right now across every product: failing checks, missing connections, open handoffs. list_metrics, query_metricThe same numbers your dashboards show, like MRR, pageviews, and signups, for one connection at a time. get_digestThis week's numbers against last week, workspace-wide. list_sources, read_sourceSearch Console, Bing, GA4, Plausible, PostHog, and Cloudflare Web Analytics data: queries, pages, traffic sources, and funnels, as totals, never visitor or customer records. An example setup
For an MCP client that takes raw JSON configuration (used by some clients instead of a sign-in flow):
{ "mcpServers": { "lopebase": { "url": "https://app.lopebase.com/api/mcp", "headers": { "Authorization": "Bearer lb_agent_..." } } } } Replace the token with one from Agent access. Clients that support the OAuth sign-in flow do not need this; adding the bare URL is enough.
Where to go next
Set up from your terminal wires up the MCP server, the CLI, and the adapter in one step.
AI reviews and credits covers what an agent's content tools cost.
Fix a connection that needs reconnecting if a source an agent connected stops working.
If something goes wrong
Something else? Contact us.
01My agent can't find the approval page
Some terminals cannot open a browser automatically. Copy the link your agent prints and open it yourself, or run npx lopebase mcp, which forwards to the same server using your saved sign-in.
02The agent says the token needs a scope it does not have
Create a new agent token with the scope the tool needs, from SettingsAgent access, and point the agent at that one instead.
03A tool call fails with "Invalid or expired agent token"
The token was revoked, passed its expiry, or the admin who created it is no longer an admin of the workspace. Issue a new one from Agent access.
04I approved the wrong workspace
Revoke that token from Agent access, then reconnect the agent and pick the right workspace when it asks.
05Can my agent see stored connection keys?
No. No MCP tool returns a stored secret, including the ones that connect a new source. The agent sends the value in; it never reads one back out.
PreviousBuild dashboards NextAI reviews and credits Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Connect an agentFor agents that only take a tokenWhat a token can doWhat an agent can doAn example setupWhere to go nextIf something goes wrongView as Markdown

---

## Set up from your terminal

URL: https://lopebase.com/docs/npx-lopebase

Run npx lopebase in a product's folder to scan its stack, connect your workspace, and hand the rest of setup to your coding agent.

Docs Get started Set up from your terminal
Run npx lopebase in a product's folder to scan its stack, connect your workspace, and hand the rest of setup to your coding agent.
Updated October 8, 2026 4 min read Open Properties Copy as Markdown If you use a coding agent like Claude Code or Codex, npx lopebase is the fastest way to add a product to LopeBase. Run it in the product's folder. It reads your stack, connects this computer to your workspace, and then hands the rest of setup to your agent, which does the clicking and asks you for anything it needs.
What it reads
Before anything else, it asks to scan the current folder. It reads dependency names from package.json and from Python, Ruby, PHP, Go, and Rust manifests, which config files exist (things like wrangler.toml or a Dockerfile), your public site address, and the variable names in your example env files, like .env.example. It never opens a real .env file and never reads your source code, so nothing secret leaves your machine during the scan.
From that, it works out what is already wired up and worth connecting, such as PostHog, Sentry, Stripe, or GitHub, and what is worth watching for uptime: the site itself, plus any database, job queue, or email sender your app depends on. If your project is a website with no analytics or error tracking yet, it points that out too.
Sign in
Next it connects this computer to your workspace. A code appears in your terminal and your browser opens to approve it; sign in or create a free account there, check the code matches, and press Connect. If your terminal cannot open a browser, it falls back to asking you to paste an agent token instead, which you create under SettingsAgent access.
Open Agent access The connection is saved on this computer, so npx lopebase in another project's folder reuses it without asking again. Run npx lopebase login on its own any time you only want to connect or reconnect this computer.
Handing setup to your coding agent
After you name the product and pick what to connect, it looks for a coding agent on your computer (Claude Code, Codex, and others), adds the LopeBase tools to it, and starts it with a prompt describing the work. From there your agent:
Adds the product to your workspace.
Connects the sources you picked, stopping to ask you for any sign-in or key it needs.
Sets up an uptime check on the site and anything else worth watching.
You can follow along in your workspace as each step turns green. If no coding agent is found on your computer, or you run with --print, it prints the same prompt for you to paste into whichever agent you use instead.
If your project depends on a database, a queue, or another service your app itself talks to, your agent can add the LopeBase Adapter so Uptime watches those too, not just the site.
Keeping it up to date
Run npx lopebase update in a product's folder to check whether the LopeBase Adapter it installed is behind. It shows what changed since your version and, if you agree, hands the upgrade to your coding agent the same way, asking before each change. If the product has no adapter installed, it says there is nothing to update there, since connections, uptime, and pageviews already update themselves in the console.
When a newer npx lopebase itself is out, it tells you at the start of a run and on Overview, with the command to copy.
Other commands
CommandWhat it does npx lopebaseScan, connect, and hand off to your agent. npx lopebase loginConnect this computer on its own. npx lopebase updateCheck the LopeBase Adapter here for updates. npx lopebase scanPrint what the scan found, without connecting anything. Add --json for a machine-readable version. npx lopebase promptPrint the setup prompt instead of starting an agent. npx lopebase mcpRun the LopeBase tools as a stdio MCP server, for a computer that is already signed in. You need Node 18 or newer. --url points the command at a specific workspace address instead of the shared sign-in page, which is useful on a second computer or a custom domain.
Where to go next
Add and manage properties covers the same setup from inside the console.
Install the LopeBase Adapter for the piece that shares your own app's users and service health.
Connect your tools covers everything your agent can connect for you.
If something goes wrong
Something else? Contact us.
01npx lopebase says command not found
You need Node 18 or newer on your computer. Check with node -v, and install a current version if it is missing or older.
02It says no coding agent was found on this computer
Install Claude Code, Codex, or another supported agent, then run it again. In the meantime, run with --print, or just answer "None, print the prompt" when it asks, and paste the result into whichever agent you use by hand.
03Nothing happens after I approve the code in the browser
The code expires after a while, so if you waited too long between seeing it and approving it, run npx lopebase again for a fresh one. If your terminal could not open a browser window at all, it should have fallen back to asking for a pasted token; if it did not, run npx lopebase login --paste.
04It says my saved connection no longer works
This happens if an admin revoked this computer's access, or the workspace itself changed. Let it sign you in again; nothing you already connected is affected.
05It connected the wrong workspace
Run npx lopebase login --url https://yourteam.lopebase.com with the workspace you meant, or sign out of the other one in your browser first and run npx lopebase again.
06npx lopebase update says there is nothing to update
That means this product has no LopeBase Adapter installed yet. Connections, uptime checks, and pageviews update themselves in the console, with nothing to run locally. Run npx lopebase (not update) if you want to add the adapter.
PreviousGet started with LopeBase NextAdd and manage properties Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
What it readsSign inHanding setup to your coding agentKeeping it up to dateOther commandsWhere to go nextIf something goes wrongView as Markdown

---

## Invite your team

URL: https://lopebase.com/docs/operators

Add teammates to your workspace, pick their role, set a different role on one connection, and see how many seats your plan allows.

Docs Workspace and billing Invite your team
Add teammates to your workspace, pick their role, set a different role on one connection, and see how many seats your plan allows.
Updated October 8, 2026 2 min read Open Operators Copy as Markdown Everyone who signs in to your workspace is an operator. Add teammates, choose what each one can do, and narrow that down to a single connection when you need to.
Add a teammate
Open Operators
ManageOperators Open Operators
Enter their email and a role
Pick Admin, Support, or Viewer (see below), then press Send invite. If email is not set up on your workspace, you get a link to send them by hand instead.
They sign in
With Google, GitHub, or an email link, using the address you invited. They show as invite pending until their first sign-in.
What each role can do
RoleCan do AdminEverything: connect and remove sources, manage billing, invite and remove operators, change roles. SupportWork with connections and run day-to-day tasks, but cannot manage billing or other operators. ViewerSee dashboards, analytics, uptime, and content. Cannot change anything. Operators lists every permission against the three roles, so you can check exactly what a role grants before you assign it.
A different role on one connection
Sometimes you want someone to manage one property's Stripe connection without touching anything else. On a teammate's row, press Access to set a per-connector role: Admin, Support, Viewer, or None, which removes that connection entirely for them. Leaving it on Default uses their normal workspace role.
Changing someone's access, their role or a per-connector override, ends their current sessions. They sign back in under the new access right away.
How many operators you can add
Each plan caps how many operators a workspace can have. Operators shows your count against the limit, and an admin sees a note on the page once you reach it: remove someone, or move to a plan with more room, from Billing.
Where to go next
Read the audit log to see what each operator changed.
Plans, trial, and billing for operator limits by plan.
If something goes wrong
Something else? Contact us.
01My teammate never got the invite email
Check they used the exact address you invited. If your workspace has no email set up, Operators gives you a link to send them yourself instead of emailing it.
02Someone still shows as invite pending after they signed in
They most likely signed in with a different address or sign-in method than the one you invited. Remove the pending invite and send a fresh one to the address they actually use.
03I can't add another teammate
Your workspace is at its plan's operator limit. Remove someone no longer active, or choose a larger plan on Billing.
04I changed someone's role and now they are signed out
That is expected. A role or access change ends that person's current sessions so the new access takes effect right away; they just need to sign in again.
PreviousAI reviews and credits NextRead the audit log Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Add a teammateWhat each role can doA different role on one connectionHow many operators you can addWhere to go nextIf something goes wrongView as Markdown

---

## Read Overview

URL: https://lopebase.com/docs/overview

What each part of Overview shows: the setup checklist, what needs attention now, your numbers across every property, and the weekly summary email.

Docs Get started Read Overview
What each part of Overview shows: the setup checklist, what needs attention now, your numbers across every property, and the weekly summary email.
Updated October 8, 2026 3 min read Open LopeBase Copy as Markdown Overview is the first thing you see in LopeBase. With every property in view, it is the one page that shows all of them together: what needs a look right now, and the numbers that matter, side by side.
Get set up
For your first week, Overview shows a short setup checklist: add a property with its website, connect your first tool, connect three tools, turn on alerts in this browser, run your first AI review, and invite a teammate. Each step ticks itself off as you do it, however you do it, and the whole list hides itself once every step is done or a week has passed. You can hide it sooner with the button in its corner, and skip any step that does not apply to you, like inviting a teammate when you work alone.
Now: what needs a look
Under "Now", Overview lists anything that needs you: a failing check, a review waiting for your approval, or a connection whose data has stopped arriving. Each line says what is wrong and links straight to it. When nothing needs attention, it says so plainly instead of showing an empty section.
Trial reminder
If your workspace is still on its trial, admins see a short card here partway through it: what you have connected and used so far, and what moving to Free would change for your workspace, with a button to upgrade and how many days are left. It can be dismissed for a few days at a time. See Plans, trial, and billing for what each plan includes.
Your numbers, across every property
Once at least one property has numbers to show, Overview adds a strip of totals: MRR, one-time revenue from the last 30 days where you have any, active users, your content queue, signups in the last 7 days, and cash on hand once a bank account is connected. Each one links to the dashboard behind it.
Below that, each property gets its own card: MRR up top, then one-time revenue, active users, queue, and signups, with the logos of the tools connected to it. Hover a logo for its name. A second set of cards shows each property's pageviews and weekly visitors from its analytics tool, and a card opens the dashboard behind it. A weekly briefing button reads every property's numbers against last week, uptime, and what needs you, then writes up what changed and what to do this week.
Looking at one property instead of all of them
Pick a property from the switcher at the top of the sidebar and Overview narrows to just that one: its own setup, its own numbers, nothing from the rest of your workspace. A Show all properties button takes you back, and Browse data opens that property's own page in full.
The weekly summary email
Settings has its own weekly email, separate from the in-app briefing: your properties' numbers and what changed from last week, sent on whichever day and time you choose. Pick what it includes (the numbers, what needs attention, a row per property, traffic, or team activity), and which properties it covers if you run more than one.
Open Email settings Where to go next
Add and manage properties if Overview is still empty.
Connect your tools for what feeds these numbers.
Alerts to hear about problems as they happen, not just when you open Overview.
PreviousAdd and manage properties NextConnect your tools Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Get set upNow: what needs a lookTrial reminderYour numbers, across every propertyLooking at one property instead of all of themThe weekly summary emailWhere to go nextView as Markdown

---

## Count pageviews with LopeBase

URL: https://lopebase.com/docs/pageviews

Add one tag to a site and LopeBase counts its pageviews, visits, pages, and sources itself, with no cookies and no visitor ids.

Docs Connections Count pageviews with LopeBase
Add one tag to a site and LopeBase counts its pageviews, visits, pages, and sources itself, with no cookies and no visitor ids.
Updated October 8, 2026 2 min read Open Analytics Copy as Markdown You do not need PostHog, Google Analytics, or Plausible to see pageviews in LopeBase. One tag, and LopeBase counts them itself: pages, visit sources, and visits, with no cookies and no visitor id, working alongside anything else you already have connected.
Add the tag
Open Analytics
Under "Pageviews counted by LopeBase" for a property with no hits yet, copy its tag.
Open Analytics
Add it to your site
Put the tag once in the layout every page shares, inside  head , however your framework does that: app/layout.tsx for Next.js's app router, pages/_document.tsx for its pages router, the shared layout for Astro, src/app.html for SvelteKit, and so on. There is also a ready-made prompt for your coding agent to do this for you.
Deploy and check
Numbers show on Analytics within a minute of the first visit after you deploy.
The tag looks like this, with your property's own key:  script defer src="https://app.lopebase.com/lb.js" data-site="your-site-key"  /script
How it counts
Each page load sends one hit, and so does every page change inside a single-page app, without a full reload. The visit's source (a search engine, a link, or a UTM parameter) is kept only in that browser tab's sessionStorage for the rest of the visit, never in a cookie, and no visitor id is ever set. Hits are only accepted from the property's own site address, using a key that names the property but carries no secret.
Because there is no cookie and nothing to consent to, pageviews counted this way need no cookie banner, and the ad blockers that hide other analytics tools rarely block it.
What you see
Once hits arrive, Analytics shows pageviews and visits over the last 30 days, pages per visit, your top traffic source, a daily chart, and breakdowns of top pages and sources, the same shape as any other analytics source LopeBase reads.
With or without the adapter
Pageviews work whether or not a property has the LopeBase Adapter installed. With both, LopeBase can show which pages and sources bring in the signups your adapter reports from your own database.
Where to go next
Connect your tools for PostHog, Google Analytics, or Plausible if you already use one of them.
Analytics for everything else the page shows.
Install the LopeBase Adapter to pair pageviews with your own signups.
If something goes wrong
Something else? Contact us.
01No numbers show up after adding the tag
Check that the tag is on every page, inside the shared layout rather than just one page, and that you deployed after adding it. It can take a minute after the first real visit for numbers to appear.
02Add LopeBase's site address on the property first
The property needs a site address before LopeBase can issue it a tag. Add one on the property's own page, then come back to Analytics.
03Will this need a cookie banner?
No. It sets no cookie and no visitor id, so there is nothing that needs consent.
04Can I use this alongside PostHog or Google Analytics?
Yes. It runs independently of any other analytics connection; Analytics shows each source's numbers in its own row.
PreviousInstall the LopeBase Adapter NextUse the SEO toolkit Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Add the tagHow it countsWhat you seeWith or without the adapterWhere to go nextIf something goes wrongView as Markdown

---

## Automate with pipelines

URL: https://lopebase.com/docs/pipelines

Chain steps like writing an article, auditing your site, or finding customers who are leaving, with a check by you wherever you want one.

Docs Run Automate with pipelines
Chain steps like writing an article, auditing your site, or finding customers who are leaving, with a check by you wherever you want one.
Updated October 8, 2026 3 min read Open Pipelines Copy as Markdown A pipeline is a job of several steps that runs on its own and stops for your OK where you put a check. Steps can write with AI, read your numbers, or wait for you to look something over before the next step runs. Start from a template, or build your own from the step list.
The ready-made templates
TemplateSteps Write, review, and publish an articleWrites on your best topic idea, or one you name, waits for you to read it, then publishes it where your articles go. SEO checkup, then write the top fixAudits your pages and search results, shows you what to fix, and once you agree writes an article on the best quick win it found. Plan next month's articlesFinds fresh topic ideas from your keywords and Search Console, shows you the best ones, and puts them on the open dates of your content calendar. Free. Win back cancelling customersFinds customers whose payment failed or who are cancelling, shows you who, then drafts a short personal note for you to send. Run one
Open Pipelines
Open Pipelines
Pick a template and a property
Each template card shows its steps as a flow and what it costs in AI credits before you run it. Templates with no AI step, like planning next month's articles, are free.
Let it run, or come back to it
A run keeps going in the background even if you close the tab or move to another page. A step marked "You check it" stops the run and shows under Waiting on you until you review it.
Review what it found
Open the run to read what the earlier step produced, then approve to continue or stop the run there.
Open Pipelines
Build your own
New pipeline chains steps from a short list, each one grouped by what it does:
GroupSteps ContentWrite an article, publish the article, find topic ideas, put ideas on the calendar. SearchAudit the site, write on the top search opportunity. CustomersFind who is leaving, draft a note to them. AIWrite with AI: anything you ask for, using the property and what earlier steps found. YouYou check it: pauses the run until you look and approve, or stop it. A step that needs something an earlier step made, like an article or a list of people, can only follow a step that makes one. Put a "You check it" step wherever you want a chance to stop the run before it goes further. Copy any template and change it rather than starting from nothing.
Building and saving your own pipelines needs an admin and a database. Without one, you can still run the ready-made templates.
Recent runs
Every run, from a template or one you built, shows on Pipelines with how far it got: running, waiting on you, done, or stopped. A stopped run's page says what went wrong, and you can retry it from where it stopped rather than starting over.
If something goes wrong
Something else? Contact us.
01Why is my pipeline waiting and not finishing?
A "You check it" step always pauses until someone with the capability to review approves it. It shows under Waiting on you on Pipelines until then; nothing times it out.
02A run says "Stopped." What now?
Open the run to read what failed. Fixing the cause, like connecting a tool a step needed, usually lets you retry from that step rather than running the whole pipeline again.
03Can I close the tab while a pipeline runs?
Yes. It keeps running in the background and shows as running when you come back. If it finishes while you are elsewhere in LopeBase, a toast with a View button lets you jump straight to it.
04Why can't I build a custom pipeline?
New pipeline needs the capability to manage pipelines and a database to save them to. Without a database you can still run every template.
05What does a pipeline cost?
Only its AI steps cost credits; a pipeline with none, like planning next month's articles, is free. Each template card shows its estimated cost before you run it.
PreviousAlerts and the weekly email NextBuild dashboards Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
The ready-made templatesRun oneBuild your ownRecent runsIf something goes wrongView as Markdown

---

## Add and manage properties

URL: https://lopebase.com/docs/properties

A property is one product or site you run. Add one with its name and address, see it at a glance, and understand what happens when a plan runs out of room.

Docs Get started Add and manage properties
A property is one product or site you run. Add one with its name and address, see it at a glance, and understand what happens when a plan runs out of room.
Updated October 8, 2026 4 min read Open Properties Copy as Markdown A property is one product or site you run. Every connection, every number, and every alert in LopeBase belongs to a property. Properties live on their own page, where you can see every one you watch at a glance.
Open Properties Add a property
Open Add property
On Properties, press Add property. The first property you add shows this same form the moment you sign up.
Name it, and give it an address
The name is whatever you call the product. The address is optional, but worth adding: LopeBase uses it to fetch the property's icon and to match the connections you add later (Search Console, analytics, and so on) to the right property automatically.
Add and connect
Press Add and connect and you land straight on that property's page, ready to connect its first tool.
The same dialog has a terminal command you can copy and run in the product's own repo instead: it scans the project and hands setup to your coding agent. See Set up from your terminal.
Its icon and address
With an address, LopeBase shows the site's own favicon next to the property's name everywhere it appears. A property with no address, or whose site has no usable favicon, gets a plain icon instead; you can pick a different one from the property's own page if you want.
The address also does quiet work behind the scenes: when you connect Search Console, Google Analytics, or another source, LopeBase prefers the property whose address matches, so you are rarely asked to pick the right one by hand.
See every property at a glance
Each card on Properties shows:
Its icon, name, and address.
Whether its site is up right now, and how fast it answered, once an uptime check is running.
Its Domain Rating, once SEO has read it.
The tools connected to it, as logos, with anything past the first few rolled into a "+N more" you can hover.
A property with nothing connected yet says so plainly, so it is obvious which ones still need attention.
When a plan runs out of room
Every plan caps how many properties it covers at once: Free covers 1, Studio 3, Portfolio 10, and Agency has no limit. If your trial ends or you move to a smaller plan, LopeBase does not delete anything. The properties connected first, up to the new plan's limit, keep updating as usual. Any beyond that pause: their settings and history stay exactly as they were, but their numbers stop refreshing until the workspace moves to a plan with enough room, at which point every paused property turns back on at once.
Open Billing Delete a property
When you stop running a product, delete it so it stops counting toward your plan and its numbers leave Overview. Only a workspace admin can delete a property, and only one the workspace added itself.
Open the property
Go to Properties and open the one you want to delete. You can also start from SettingsYour data, which lists every property you can delete.
Open Your data
Type its name to confirm
At the bottom of the property's page, under Delete this property, type the property's name and press Delete property.
This removes the property for good, along with its connections and their saved keys, its uptime history, its status page, and its SEO, content, and discussion data. Nothing changes in the tools it was connected to, like Stripe or Search Console. The audit log keeps a record of who deleted it and when.
Deleting a property cannot be undone. If you only want it to stop updating for a while, leave it in place: on a smaller plan the extra properties pause instead.
Where to go next
Connect your tools for what to connect once a property exists.
Read Overview to see every property's numbers together.
Set up from your terminal to add a property from its own repo instead.
If something goes wrong
Something else? Contact us.
01I don't see an Add property button
Only a workspace admin can add or manage properties. Ask whoever set up your workspace to add you as an admin, or to add the property for you.
02A property's numbers stopped updating
Check Billing: if your workspace is over its plan's limit, the properties connected most recently are the ones paused first. Choosing a plan with enough room turns them all back on right away.
03The wrong icon is showing
LopeBase fetches the icon from the property's address. If the address is missing, wrong, or the site has no usable favicon, open the property and pick a different icon from its header.
04A connection I added isn't matched to the right property
This usually means the property's address does not match that tool's site exactly, or the property has no address yet. Add or fix the address on the property, then connect the tool again.
PreviousSet up from your terminal NextRead Overview Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Add a propertyIts icon and addressSee every property at a glanceWhen a plan runs out of roomDelete a propertyWhere to go nextIf something goes wrongView as Markdown

---

## Fix a connection that needs reconnecting

URL: https://lopebase.com/docs/reconnect-a-connection

What the Needs reconnecting state means, why LopeBase waits before showing it, and how to fix a revoked key, expired sign-in, or rate limit.

Docs Troubleshooting Fix a connection that needs reconnecting
What the Needs reconnecting state means, why LopeBase waits before showing it, and how to fix a revoked key, expired sign-in, or rate limit.
Updated October 8, 2026 3 min read Open Connections Copy as Markdown A connection can stop working for a few different reasons: a key got revoked, a sign-in expired, or the service is just busy for a moment. LopeBase tells these apart so a brief hiccup never looks like a broken connection, and only asks you to act when something really needs it.
What the different states mean
What you seeWhat it means Needs reconnectingLopeBase confirmed the key or sign-in no longer works, by checking it directly, not from one failed read. Your stored numbers stay on screen, marked with when they last refreshed. Limiting requestsThe service asked LopeBase to slow down. Numbers fill back in on their own within a few minutes; nothing to do. Did not answerA one-off timeout or network hiccup. This usually clears itself on the next check. FailingSomething else went wrong reading this connection. Try again in a few minutes; if it continues, it is worth a look. Only "Needs reconnecting" needs you to do something. LopeBase checks a connection's credentials directly before showing this state, so a service that briefly turns away a good key does not get flagged by mistake.
Fix it
Find the connection
Open Connections, or follow the Reconnect link next to the numbers on the page where you noticed it, or in the bell at the top of the sidebar.
Open Connections
Reconnect it
For a connection that signs in (Google, GitHub, Cloudflare, Bing), press its Connect button again and approve the sign-in. For one that uses a pasted key, open it and paste a fresh key from the service.
Confirm it worked
LopeBase tests the new key or sign-in immediately. If it works, the connection clears and its numbers start catching up. Reconnecting one sign-in clears the "needs reconnecting" flag for every other connection using that same sign-in too.
Why a key stops working
The most common reasons, by kind of connection:
OAuth sign-ins (Google, GitHub, Cloudflare, Bing): the access you approved was removed on the service's side, or your account there lost permission to the project or site.
Pasted API keys (PostHog, Sentry, and others that take a key): the key was deleted or rotated on that service.
The LopeBase Adapter: its signing secret changed in your app's environment without updating it here, or the adapter was removed from a deploy.
Where to go next
Connect your tools for how each kind of connection is set up.
Troubleshooting for other problems, like numbers that look missing or stale.
If something goes wrong
Something else? Contact us.
01I reconnected it but it still says needs reconnecting
Give it a minute; LopeBase tests the new key before clearing the flag. If it still shows after that, the new key likely does not have the access this connection needs, such as read access to the right project.
02A connection keeps needing reconnecting every few days
That usually means the key or token the service issued is short-lived by design. Check whether that service offers a key that does not expire, or reconnect the OAuth sign-in instead of a pasted key where that option exists.
03My numbers look stale but nothing says needs reconnecting
A connection can be slow to refresh without being broken. Check Troubleshooting for numbers that are missing or look wrong.
04Do I lose history while a connection needs reconnecting
No. Nothing is deleted. The last good numbers stay on screen, marked with when they were last refreshed, until the connection is fixed.
PreviousHow LopeBase handles your data NextTroubleshooting Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
What the different states meanFix itWhy a key stops workingWhere to go nextIf something goes wrongView as Markdown

---

## Track MRR and revenue

URL: https://lopebase.com/docs/revenue

See MRR, one-time payments, past due and cancelling subscriptions, and your bank balances and runway, from Stripe, Polar, Mercury, Wise, Rho, and Brex.

Docs Grow Track MRR and revenue
See MRR, one-time payments, past due and cancelling subscriptions, and your bank balances and runway, from Stripe, Polar, Mercury, Wise, Rho, and Brex.
Updated October 8, 2026 3 min read Open Revenue Copy as Markdown Revenue reads MRR, subscriptions, and payments from your billing accounts, plus cash in the bank, for the whole workspace or one property at a time.
Go to GrowRevenue, or Open Revenue.
Connect billing and banks
Connect Stripe or Polar, read-only, for each property's MRR, subscriptions, and payments. Open Connections. If a property's own app reports its MRR through the LopeBase Adapter instead, and no billing account covers it, Revenue shows that number labeled "reported by the app."
Banks are connected once for the whole workspace, not per property: Mercury, Wise, Rho, or Brex. Connecting any of them adds a Cash section to Revenue.
MRR, one-time revenue, and totals
With every billing source in the same currency, the top strip shows MRR from active subscriptions, how many are active (and how many are past due), gross and net payments in the last 30 days, and, when reported, one-time payments outside subscriptions. Sources in more than one currency are never added into one total; pick a property to see its own numbers, or read each property's row under By property instead.
One property in detail also shows its live subscriptions, worst first: past due, then cancelling, then active, with each customer's plan and monthly amount; and its most recent payments across every connected source.
Past due and cancelling subscriptions
A subscription shows past due the moment a charge fails, and cancelling once the customer has set it to end at the period's close. Both are called out on the By property summary (as counts) and in detail on one property's subscription list, so you can follow up before the money is actually lost.
Cash and runway
With a bank connected, Cash shows what is available now and money in and out over the last 30 days, added up in your main currency; balances held in another currency are listed beside it, not folded in. Runway is cash divided by the last 30 days' net outflow, so it moves every month: if more came in than went out, it reads "Growing" instead of a number.
AI revenue review
Review my revenue reads MRR, cancellations, past-due subscriptions, and recent payments, then says where revenue stands, what is at risk, and what to do about it. Customer names and emails are never sent to the AI. It uses AI credits or your own key, with the cost shown before you run it.
Where to go next
Connect Stripe for MRR and subscriptions.
See your users to find who is behind a past-due or cancelling subscription.
Build a dashboard to put revenue and cash on one screen with everything else.
If something goes wrong
Something else? Contact us.
01Why don't my revenue totals add up across properties?
Totals only add sources reporting in the same currency. A property billing in euros next to ones billing in dollars shows its own row instead of folding into the combined total; look at By property for each one's own numbers.
02Why is "Cancelling" blank or "Not reported" for a property?
Not every billing source reports whether a subscription is set to cancel at period end. When it reports nothing, Revenue says "Not reported" rather than showing zero.
03Why does a property show no live subscriptions when I know it has customers?
Check that the connected key belongs to that property's own billing account; a key pointed at the wrong account reads as empty rather than wrong, since there is nothing to show.
04Why does Runway say "Growing" instead of a number?
Runway is only shown when more money went out than came in over the last 30 days. If the workspace took in more than it spent, there is no burn to divide by, so it reads "Growing."
05Why is a bank balance listed separately instead of added to Cash?
Cash only sums balances in your main currency (US dollars, if any account uses it). A balance in another currency is listed beside the total, not folded in, so the number stays accurate.
PreviousRead Analytics and traffic NextSee your users Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Connect billing and banksMRR, one-time revenue, and totalsPast due and cancelling subscriptionsCash and runwayAI revenue reviewWhere to go nextIf something goes wrongView as Markdown

---

## Use the SEO toolkit

URL: https://lopebase.com/docs/seo

Read your Search Console and Bing numbers, find pages close to ranking, check indexing and page speed, run the SEO audit, and track competitors.

Docs Grow Use the SEO toolkit
Read your Search Console and Bing numbers, find pages close to ranking, check indexing and page speed, run the SEO audit, and track competitors.
Updated October 8, 2026 6 min read Open SEO Copy as Markdown SEO reads how people find each property in search and tells you what to do about it. Nothing here is estimated: the numbers come straight from Google Search Console and Bing Webmaster Tools, both read-only connections.
Connect Search Console first. Go to GrowSEO, or Open Connections and pick Search Console or Bing.
The five tabs
Pick a property at the top of SEO and its data splits into five tabs. Add ?tab= to the address to land on one directly, for example /seo?tab=health.
Tab?tab=What it shows OverviewoverviewClicks, impressions, click rate, and average position for the last 28 days, with the change against the period before. An opportunity map of every search you show up for, where to rank in each stretch of the results, click rate by position, and your name versus everything else people found you for. HealthhealthIs Google listing your pages, how fast the site is for real visitors, and when the domain runs out. KeywordskeywordsThe searches you track, where each ranks week by week. PagespagesClicks by section of the site, pages seen often but rarely clicked, and searches split between two of your own pages. LinkslinksDomain Rating against your competitors, who links to you, where to get more links, what competitors published, and where people talk about you. Health, Keywords, Pages, and Links need the property's site address added on its Properties page; Pages and parts of Overview need Search Console connected.
Find what to write or fix next
Overview's opportunity map plots every search you show up for: further right ranks lower, higher up means more people see it, and a bigger dot earns more clicks. The ones worth acting on sit under What to do next, most seen first:
Just off page one. Ranking 11 to 20, where almost no clicks happen. A stronger page, or a new one, can push it onto page one.
Seen but rarely clicked. On page one already, but clicked below your site's own average. A clearer title and description usually fixes it.
Each one has a Copy prompt button that hands your coding agent the search, its numbers from Search Console, and what to do, so you can paste it straight into Claude Code or Cursor. If the content autopilot is set up for the property, you can also write about it in one click.
Check indexing, speed, and your domain
The Health tab runs three weekly checks. Press Check now to run them early if you can edit the property.
Is Google listing your pages?
This is a spot check of up to 40 pages, your newest articles and the pages in your sitemap, against Search Console. It is not a count of your whole site; beside it you also see how many of your pages showed up in Google search over the last 28 days, which is site-wide. A page marked not indexed shows Google's reason in plain words: not found yet, read but not listed, told not to index it, and so on. See all checked pages opens the full list, filterable by indexed, not indexed, or not checked yet.
How fast is it for real visitors?
Core Web Vitals from real Chrome visits over the last 28 days: the three numbers Google uses in ranking. A new or low-traffic site may not have enough visitors yet for Google to report this.
When does the domain run out?
Read from the public domain registry. If it lapses, the site and its rankings go with it, so the badge turns orange with 30 days left.
Run the SEO audit
On the Health tab, SEO audit is a one-button baseline: it checks your home page and blog posts for problems, finds your competitors and starts tracking their Domain Rating beside yours, and, if Search Console is connected, reviews your search results for pages to rewrite. Open the SEO audit.
The page checks themselves are free. Finding competitors and reviewing search results use AI, so they need an AI key or spend a few credits; the button shows the cost before you run it. Each checked page lists what to fix (hurts how you show up) separately from what to improve, with a Copy prompt for each page or for every fix at once.
The audit also tidies tracked keywords: it stops tracking ones that are not worth it, like spam or unrelated terms, and says why. Track any of them again from the Keywords tab.
Track rank over time
On the Keywords tab, add the searches that matter most to the property, like its category or the problem it solves. Each tracked search shows its current position (1 is the top, weighted by how often it was seen), how it moved over about four weeks, and its 12-week shape as a sparkline. Search Console reports about two days behind. Suggest searches worth tracking with AI, or clear the ones that are not worth it; both show their credit cost first.
Competitors and links
The Links tab holds everything about where you stand against other sites:
Domain Rating, 0 to 100, shows how strong the property's backlinks are next to up to 5 competitors you add or AI finds. Checked weekly, each competitor is confirmed to live at that address and name a real product before it is tracked.
Who links to you reads Bing's inbound links, checked weekly, with what changed since the last check.
Where to get links lists directories, review sites, communities, and newsletters where the property could earn a mention, found by AI and checked to be real.
New on competitor sites watches their sitemaps for what they just published.
Where people talk about it searches Hacker News, Lobsters, GitHub, and Stack Overflow for posts that already mention the site. Discussions finds threads about the problem your product solves even when they do not mention you yet.
Where to go next
Plan and publish with the content autopilot turns a search opportunity into a drafted article.
Connect your tools covers adding Search Console and Bing.
Find discussions about your product for threads that do not mention you by name yet.
If something goes wrong
Something else? Contact us.
01Why is my Search Console data missing or stuck?
Search Console reports about two days behind, so very recent days will always look thin. If numbers stopped updating entirely, open the property's Overview tab; a read problem there links straight to reconnecting Google.
02Why does a page show as not indexed when I know it exists?
The indexing check is a spot check of up to 40 pages, not your whole site, and Google's own reasons vary: it may have read the page but chosen not to list it yet, not have crawled it at all, or be pointed elsewhere by a redirect or canonical tag. Open the page in the list on the Health tab for Google's exact reason and when it last crawled it.
03Why can't I see page speed (Core Web Vitals)?
Those numbers come from real Chrome visitors over the last 28 days. A new or low-traffic site will not have enough visits yet for Google to report them; they fill in once traffic picks up.
04Why does the SEO audit or AI review ask for an AI key or credits?
The page checks in the audit are free. Finding competitors, writing link ideas, and reviewing search results use AI, so they need your own AI key connected or a few LopeBase AI credits. Every button that spends either shows the cost before you run it.
05Why did a competitor I added disappear or never show Domain Rating?
LopeBase only tracks a competitor once it confirms the domain is live and names a real product; a parked or for-sale domain is skipped. You can track up to 5 competitors per property; remove one to add another.
06Why does Bing show no position for my searches?
Bing Webmaster Tools does not report average position the way Search Console does, so SEO shows "Not reported" for it on Bing's rows. Everything else, clicks and impressions, reports normally.
PreviousCount pageviews with LopeBase NextPlan and publish with the content autopilot Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
The five tabsFind what to write or fix nextCheck indexing, speed, and your domainRun the SEO auditTrack rank over timeCompetitors and linksWhere to go nextIf something goes wrongView as Markdown

---

## Publish a status page

URL: https://lopebase.com/docs/status-pages

Turn on a public status page for any property, choose what it shows, post updates, and share its badge or RSS feed. Free on every plan.

Docs Run Publish a status page
Turn on a public status page for any property, choose what it shows, post updates, and share its badge or RSS feed. Free on every plan.
Updated October 8, 2026 3 min read Open Uptime Copy as Markdown A status page is a public page your customers can check: live status, a year of uptime, and any updates you post. It reads from the checks LopeBase already keeps, never from the site itself, so even a status page getting a lot of traffic during an outage cannot add load to the site it reports on. It is free on every plan.
Turn it on
Open Uptime
Open the Status pages tab. Every checked property has a row there with a switch and a link.
Open status pages
Turn on the switch
The page is live the moment you turn it on, at a link under your workspace's own address. Nobody can see it while it is off.
Edit it
Click Edit on that row to open the editor, with five tabs: Page, Components, Updates, Share, and Branding.
What each tab does
TabWhat it covers PageThe title, a line under it, and the page's address to copy or open. ComponentsWhat shows on the page: the site itself, and any service your health address lists. Rename a part or hide it. UpdatesPost a note: an update, maintenance, an incident, or resolved, about the whole page or one part. Edit or delete a note after posting it. ShareThe live status badge for a site or README, and the RSS feed address for your notes. BrandingYour own logo, an accent color, light or dark, and leaving off the LopeBase footer. Needs a paid plan. A part that is degraded rather than fully down shows amber and labeled "Degraded" on the page, in its badge, and on its 90-day bars. It still counts as up in the uptime percentages the page shows.
Posting an update
On Updates, pick a kind, write the note (500 characters), and optionally say which part it is about if the page shows more than one. Posted notes show newest first on the page and in the RSS feed. Edit a note any time; LopeBase marks it "edited" on the public page.
Turn on "Status page updates" in your alert settings and you hear about a teammate's note by email or browser push, the same as any other alert.
Badge and feed
The Share tab gives you a live SVG badge, ready to paste into a site or a GitHub README, that shows "up", "degraded", or "down" and links to the page. The RSS feed at /feed.xml on your status page's address lets customers follow your notes without checking the page.
Paid branding
The status page itself, its uptime history, and its notes are free on every plan, including Free. The Studio plan and above add your own logo, an accent color, choosing light or dark instead of following the visitor's system, and leaving off the "Status page by LopeBase" footer.
If something goes wrong
Something else? Contact us.
01Why is my status page showing "No data yet" for a part?
A component needs its own checks before it has a percentage. The site itself fills in as soon as the next 15-minute check runs; a service only appears once your health address has reported it at least once.
02A service I don't want on the page keeps reappearing
LopeBase adds any service your health address reports that is not already listed, shown by default. Hide it on the Components tab; it stays hidden even if the health address keeps reporting it.
03Can I stop a status page from showing at all without deleting its notes?
Yes. Turning the switch off takes the page down immediately but keeps every note and setting, so turning it back on later picks up right where you left it.
04My logo or colors are not showing
Branding needs a paid plan. On Free, the Branding tab is locked with an Upgrade button, and the page uses the default look even if you saved a logo earlier.
PreviousUptime checks and incidents NextAlerts and the weekly email Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Turn it onWhat each tab doesPosting an updateBadge and feedPaid brandingIf something goes wrongView as Markdown

---

## Troubleshooting

URL: https://lopebase.com/docs/troubleshooting

Quick fixes for the problems people hit most: signing in, numbers that look wrong, uptime false alarms, missing alerts, billing, and agents.

Docs Troubleshooting Troubleshooting
Quick fixes for the problems people hit most: signing in, numbers that look wrong, uptime false alarms, missing alerts, billing, and agents.
Updated October 8, 2026 4 min read Open LopeBase Copy as Markdown Short answers to the problems people run into most, grouped by what you were trying to do. If yours is not here, see Fix a connection that needs reconnecting, or email us from the link at the bottom of this page.
Signing in and workspaces
Something else? Contact us.
01I signed in but I'm in the wrong workspace
Switch workspaces from the menu next to your name at the bottom of the sidebar. If a workspace you expect is missing, you may have been invited under a different email than the one you signed in with.
02My coding agent's sign-in link never opens an approval page
See Connect Claude and other agents over MCP: some terminals cannot open a browser on their own, so copy the printed link and open it yourself.
03I signed out everywhere and my phone app still shows me signed in
Open the app again; it lands on the sign-in page instead of reloading. If it does not, close and reopen it once.
Numbers missing, wrong, or stale
Something else? Contact us.
01A number says n/a
LopeBase has not read that number yet, or the connection behind it cannot report it at all, which is different from a connection that is failing. Open the connection to see which.
02A page shows an old number after I know it changed
Pages read from numbers LopeBase already has, not live on every page load, so there is always a short lag. The "Updated" note under a page's numbers says how old they are, and a Refresh button asks for a fresh read right now.
03A connection shows "Needs reconnecting"
See Fix a connection that needs reconnecting.
04Two analytics tools show different pageview counts for the same property
Each one counts differently (cookies, bots, single-page apps). LopeBase shows each source separately rather than blending them, so pick one as your source of truth per property.
Uptime false alarms
Something else? Contact us.
01Uptime said a service was down but it was fine
A single failed check is tried again before it counts as down, and a check against a vendor's status page or a shared endpoint can misfire. If your adapter's service checks use your own app's credentials, as the setup guide walks through, this is rare; mark a non-critical service as such so its failure shows as degraded instead of taking down the whole product.
02I get an alert the moment a service blips
Site-down alerts fire right away on purpose. A connected tool that stops answering waits about an hour of continuous failure before it alerts, so a short blip does not page you; it still shows on Overview sooner than that.
03A service I added shows as degraded, not down
That is the point of marking it non-critical: its failure is visible without reporting your whole product as down. Uptime still shows it under Needs attention.
Alerts not arriving
Something else? Contact us.
01I turned on browser alerts but never get one
Check Settings, Alerts says the state for this browser. If notifications are blocked, allow them in your browser's site settings next to the address bar, then reload. Send yourself a test alert from the same page to confirm.
02I'm not getting email alerts
Confirm the Email checkbox is on in Settings, Alerts, and that email is enabled on your deployment; the page says if it is not.
03I only want to hear about serious problems
Set "How serious" to Needs action in Settings, Alerts. That drops early warnings like a bounce rate approaching a limit, and keeps things that are actually broken or blocking.
Billing
Something else? Contact us.
01My product stopped updating
See Plans, trial, and billing: it is most likely paused because your plan does not have room for every product you connected.
02I can't connect anything new
Check Billing for a past-due or suspended notice; new connections, operators, and dashboards pause until an unpaid invoice is settled.
03An AI feature stopped working
You are most likely out of AI credits for the month. See AI reviews and credits for buying a pack or bringing your own key.
Agents and MCP
Something else? Contact us.
01My coding agent's token stopped working
It expired, was revoked, or the admin who created it is no longer an admin of the workspace. Issue a fresh one from Connect Claude and other agents over MCP.
02My agent says a tool needs a scope it does not have
Create a new agent token with that scope (setup, read, or manage) from Settings, Agent access, and point the agent at it.
03npx lopebase can't find my coding agent
It looks for Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent on your machine. If yours is not one of those, add the MCP server by hand; see Connect Claude and other agents over MCP.
PreviousFix a connection that needs reconnecting Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Signing in and workspacesNumbers missing, wrong, or staleUptime false alarmsAlerts not arrivingBillingAgents and MCPView as Markdown

---

## Uptime checks and incidents

URL: https://lopebase.com/docs/uptime

How LopeBase checks your sites every 15 minutes, watches the services behind them, and reviews outages for you. Set up a check and read what it shows.

Docs Run Uptime checks and incidents
How LopeBase checks your sites every 15 minutes, watches the services behind them, and reviews outages for you. Set up a check and read what it shows.
Updated October 8, 2026 4 min read Open Uptime Copy as Markdown Uptime checks every site you add every 15 minutes, with no account or key needed, and keeps a year of history. On RunUptime the Overview tab opens with one line saying whether everything is up. Anything down or degraded is pinned right under it with buttons to open the property, post a status note, or see the outage. Below that are your uptime over 30 days, outages this month, and average response time across sites, then a card for each site with problems first. The Outages, Monitors, and Status pages tabs hold the rest, and a tab with nothing in it is left out.
Add a check
A new property has no check until you add one. Properties with no check yet are listed in a short panel at the bottom of the Overview tab, each with an Add check button.
Add the address
Give the site's own address, or a health address if it has one. LopeBase fetches it every 15 minutes and marks it down if it does not answer, answers slowly, or returns an error.
Add an uptime check
Or get it from the adapter
If the property already runs the LopeBase Adapter, connecting it adds its health address as the uptime check automatically, unless that property already has one.
Watching the services behind the site
If your app runs the LopeBase Adapter, point the check at its health address (/api/lopebase/health by default) instead of the home page. The adapter answers with each service you declared there, like your database, a queue, or a second API, and each one shows as its own row on Uptime.
Each service is checked with the app's own credentials, like a select 1 or a Stripe balance.retrieve, so it proves the integration works rather than just that the vendor's servers are up.
A service you mark non-critical shows the whole site as degraded if it fails, not down. A critical service failing answers 503 and the site shows as down. Degraded still counts as up in your uptime percentages, but it shows amber and labeled "Degraded" apart from a real outage everywhere it appears: the day strip, a status page's badge and 90-day bars, and the alert you get.
Reading the numbers
Each site's card shows its 30-day uptime and average response time up front, then a 30-day strip colored per day: green for a clean day, orange for degraded, red for any failed check. Hover a day for its tally. The line under the strip has 24 hours and 7 days from individual checks, plus 90 days and 12 months from daily totals once you have history. A window with no checks yet in it says "Collecting" rather than a number. The uptime figure at the top of the page is the plain average of every site's 30-day figure.
Outages and the incident review
On the Outages tab, every outage in the last 30 days lists when it started, how long it lasted, and what the check saw, with the response-time chart for the last 24 hours under it. Below that, Review incidents reads those 30 days together with your top errors when Sentry, Bugsnag, Rollbar, Honeybadger, or PostHog's error tracking is connected, and says what went wrong and what to fix first.
After real downtime, the review drafts a status note for your customers. If you run a status page for that property, a button posts the note straight to it, in the wording the review drafted.
Error trackers and Better Stack
Uptime checks sit next to error trackers under Monitoring on ManageConnections. Connecting Sentry, Bugsnag, Rollbar, or Honeybadger adds that property's open errors and daily error counts to its timeline and to the incident review, read-only.
If you already run monitors in Better Stack, connect it with one team API token and LopeBase reads the monitors you pick. They show on the Uptime page's Monitors tab, with each one's status and 30-day availability, and a monitor that is down counts in the summary at the top like a failed check and is pinned there with a button to see it. It also shows under Needs attention on Overview and alerts you right away. Better Stack monitors sit beside LopeBase's own 15-minute checks; a property can have both.
If something goes wrong
Something else? Contact us.
01Why does Uptime say "Collecting" instead of a percentage?
A window needs at least one check inside it. A brand-new check has none yet for the shorter windows and takes 90 or 365 days to fill the longer ones. The live status at the top is accurate right away.
02LopeBase says a site is down but it loads fine for me
Check the address you gave it: a page behind a login, a redirect to a different host, or a firewall that blocks LopeBase's requests all read as down. The outage's "What we saw" column shows the HTTP status or error LopeBase got.
03Why does it say degraded instead of down?
One of the services your health address lists failed, but you marked it non-critical, or the site itself still answered while a critical service failed partway. The error message names which service.
04Can I watch something other than a web address?
Only through a health address that answers over HTTP. There is no check for a database or queue you cannot reach from the public internet, except through your own LopeBase Adapter's health endpoint.
05I don't want LopeBase pinging a vendor's status page
It never does. A service check always uses the app's own credentials and a cheap authenticated call, never a vendor's status page or home address.
06Why did I get an alert for something that recovered in a minute?
A short blip still shows on the day strip and in the outage list, but alerts wait until something has failed for about an hour before emailing or pushing, so a brief hiccup does not page you. See Alerts.
PreviousSee your users NextPublish a status page Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Add a checkWatching the services behind the siteReading the numbersOutages and the incident reviewError trackers and Better StackIf something goes wrongView as Markdown

---

## See your users

URL: https://lopebase.com/docs/users

See your app's users, paying customers, and newsletter subscribers matched into one list, with what is worth acting on, like failed payments.

Docs Grow See your users
See your app's users, paying customers, and newsletter subscribers matched into one list, with what is worth acting on, like failed payments.
Updated October 8, 2026 2 min read Open Users Copy as Markdown Users brings together who uses each property: its app's own accounts, its paying customers, and its newsletter subscribers, matched into one list by email address. Every read here is live and checked against your permissions, since these are people's details, not stored numbers.
Go to GrowUsers, or Open Users.
Three sources, matched by email
Users reads from up to three places per property, and shows each as connected or not at the top:
SourceWhat it gives Your app's usersSignups and accounts, read from your app by the LopeBase Adapter. Paying customersPlans, status, and who is cancelling, from your billing accounts (Stripe or Polar). NewsletterSubscribers, tags, and unsubscribes, from your connected email tool. A person who shows up in more than one source becomes one row, with whichever facts each source has: in the app or not, their plan and billing status if they pay, and their newsletter status and tags if they subscribe. With more than one property shown, each row also lists which properties that person belongs to.
Worth acting on
Above the full list, LopeBase calls out groups worth a direct action, each one only shown when its sources are connected:
Payments failed. Their card was declined; a short personal note usually gets it fixed before the subscription ends.
Cancelling at the end of the period. Still has access; worth asking what made them leave while there is still a chance to fix it.
New this week. A welcome from a real person in the first days is the cheapest way to keep them.
Paying customers not on the newsletter. Worth inviting in a receipt or onboarding email so they do not miss product news.
Subscribers who have not signed up. They like what you write but have not tried the product; worth a newsletter issue with a clear way to start.
Each card lists a few of the people it covers and a Copy button for every email address in the group, ready to paste into your mail tool.
Where to go next
Connect the LopeBase Adapter for your app's own users.
Connect Stripe for paying customers and cancellations.
Track MRR and revenue for the numbers behind who is paying.
If something goes wrong
Something else? Contact us.
01Why does the people list say "No one with an email yet" when my app has users?
The LopeBase Adapter needs a users resource that reports an email for each account. Until it does, the app's user count still shows at the top; only the row-by-row list needs email addresses.
02Why is the same person showing twice?
Rows are matched by email address, so the same person under two different addresses (a work email on billing, a personal one on the newsletter) will show as two rows until one source uses the matching address.
03Why don't I see a "Worth acting on" card I expected, like cancellations?
Each card only appears once the sources behind it are connected. Cancelling and past-due cards need a billing connection; the newsletter cards need both the app and the newsletter connected.
04Why does a paying customer show as "Free" here?
Only a subscription whose status counts as active, trialing, or past due counts as paying. A canceled or incomplete subscription shows as Free even if that person paid in the past.
PreviousTrack MRR and revenue NextUptime checks and incidents Still stuck?Send us a message with what you tried. A person who builds LopeBase answers. You can also send feedback from the Feedback button inside the app.
Open LopeBase On this page
Three sources, matched by emailWorth acting onWhere to go nextIf something goes wrongView as Markdown

---

## Features: SEO, uptime, revenue, and more

URL: https://lopebase.com/features

LopeBase features: dashboards across products, SEO checks, uptime, revenue, AI reviews of your numbers, a content autopilot, setup over MCP, and an audit log.

Everything you need to run more than one product.
Dashboards, SEO checks, uptime, revenue, a weekly digest, AI reviews of your own numbers, a content autopilot, and agent setup over MCP. One console, every product.
Features
MRR, all productsProduct oneProduct twoProduct three Dashboards you put together
Pick charts from every connected source and pin them to one board. Numbers, bars, lines, areas, and tables.
A live map of what is wired
Every source and its health at a glance. A broken token turns its line red before a customer notices.
Draft
SEO check
Review
Publish
Index
Waiting on youPost: "Pricing guide", Product three Approve Pipelines with a review gate
Multi-step work runs on its own and stops for a person before anything goes live. Start from a template, or build your own from steps like writing an article, auditing the site, or finding customers who are leaving.
Product two2 subscriptions past dueRevenue
Product oneSearch Console stopped answeringSource
Product three2 drafts waiting for reviewContent
What needs you, first
The Overview opens on what to look at: a broken connection, past-due subscriptions, analytics that stopped arriving, drafts waiting on you.
Ownerreadwriteadmin Operatorreadwriteadmin Viewerreadwriteadmin Share the console, not the keys
Give a contractor a view of one product's numbers and nothing else. Your keys stay with you.
Purple Aurora
Five palettes, light and dark
Pick the console's color. Go on, try one. This page follows along.
SEO
The checks you mean to do. Done every week.
Search Console, Bing, Google's speed data, and Ahrefs' Domain Rating, read for every product and turned into a short list of what to fix.
Checked your home page and blog posts
Found 3 competitors and started tracking them
Reviewed your search results for pages to rewrite
Run the SEO audit againShows the cost in credits first Run audit A baseline in one button
One run checks your pages, finds your competitors and starts tracking them, and reviews your search results. Run it again whenever you like.
Seen, rarely clicked Pricing | Product two Product two pricing: plans from free to teamMatches the searches this page already shows up for Titles that earn the click
An AI review finds the pages people see in search but skip, and suggests a better title and description for each.
32of 40 indexed Is Google listing your pages?
A page that is not indexed cannot show up at all. Your newest articles and your sitemap's pages, checked with Search Console.
Loading1.9 sGood Responsiveness140 msGood Visual stability0.18Needs work Speed for real visitors
Google's Core Web Vitals from real Chrome visits, against Google's good and poor bands.
yourproduct.com34 competitor-a.com41 competitor-b.com22 You against the competition
Your Domain Rating beside your competitors', checked weekly, and how it has moved.
competitor-a.com/blog/churn-benchmarksNew
competitor-b.com/pricingNew
news.ycombinator.comLinks to youLink
Links and rivals, watched
Who links to you, from Bing. What competitors published, from their sitemaps. Where Hacker News mentions you.
See the whole SEO suite
Every day
Is it up? Is it growing? Already answered.
The tabs you open every morning, for every product, on one screen.
Product oneUp Product twoUp Product threeUp Uptime, every 15 minutes
Add the address of any site or health page. No account or key needed. A year of uptime, every outage, and a free public status page.
MRR, all products$4,2102 past due Revenue
MRR, active and past-due subscriptions, and recent payments from Stripe or Polar.
Visitors, 7 days Analytics side by side
Visitors and pageviews from PostHog or Google Analytics, plus each product's own signups.
Your workspace this weekMonday, 8:00 Numbers Needs attention Each product A weekly digest
One email with each product's numbers, the change from last week, and what needs you. You pick the day and hour.
Type a command or search...Ctrl K Write an article Launch SEO pipeline Export audit log (CSV) Everything is one keystroke away
The command palette jumps to any page or starts a task without touching the mouse.
AI reviews
Your numbers, read for you.
One button on the page you already use. Each review opens with what matters most, then what stands out and what to do next, using only your own numbers.
Weekly briefingOverview, every product Signups on Product one up on last week
Product two traffic down after a quiet week of posts
Product three was down for 40 minutes on Tuesday
A weekly briefing
Every product against last week, uptime, and what needs you, read into what changed and what to do this week.
Revenue at risk$1803 past due Revenue review
Cancellations, past-due subscriptions, and failed payments, and what to do about each.
This week vs last Traffic review
What is driving visits, what is slipping, and which pages to work on next.
Status page noteDrafted from Tuesday's outagePost Incident review
Outages and top Sentry errors, what to fix first, and a note for your customers after downtime, ready to post to your status page.
AI reviews All five reviews, including posts to share any article, and what each one will never do. Built for how products get run now
Content autopilot Topics from your search data, drafts in your voice, checked, then reviewed by you or published on a schedule. Clicks and impressions come back per article. AI reviews A weekly briefing and reviews of revenue, traffic, and outages, written from your own numbers, plus posts to share each article. Agents and MCP Give your coding agent a token and let it add products, connect sources, and wire up your app's admin adapter. An audit log where every change has a name and a diff.
Someone asks who let an article go live last Tuesday. You search the log, find who approved it, and see the exact before and after. That is the whole conversation.
Audit 14:31 UTCeditor@ pipeline.approveProduct three / Publish a post - "status": "awaiting_review"+ "status": "running" 14:32 UTCcontent-autopilot emdash.publish_postProduct three / pricing-guide - "status": "draft"+ "status": "published" Capabilities gate every write
Roles map to a short list of capabilities, and a person can be narrowed to one product. No blanket admin.
A person signs off on what ships
Multi-step work, like a post to publish or a newsletter to send, pauses for review before the step that goes live.
Export the log
Filter the audit feed by date, person, or product and download it as CSV or JSON.
Connectors Stripe, PostHog, Search Console, and more, plus your own app. Pricing Free for one product. Start from what you want to get done
Each goal has its own page with the details.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 06 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free See every product in one place.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Connect one product for free. Add the rest when you are ready.
Start free Sign in

---

## Growth analytics

URL: https://lopebase.com/growth

Visitors from PostHog, Google Analytics, Plausible, or Cloudflare side by side, with each product's signups and a review of where people drop off.

Turn more visitors into signups.
LopeBase puts each product's traffic, search clicks, and signups on one page, whatever analytics tool it uses. Then one button lines it all up and tells you where people drop off and what to change first.
Start free See the conversion review Read-only keys. Free for one product.
The Analytics page
Every product's traffic, whichever tool it uses.
One product on PostHog, another on Google Analytics, a third on Plausible. They all land on the same page.
Pageviews per day Visitors and pageviews, side by side
Weekly and monthly visitors, pageviews, and top pages from PostHog, Google Analytics, Plausible, or Cloudflare Web Analytics.
Signups, 7 days90Across 3 products Your app's own signups
Signups and active users come straight from your product through the LopeBase Adapter, not from a guess in a tag.
One tag, no cookiesPages, sources, and visitsCopy Pageviews counted by LopeBase
No analytics tool yet, or tired of the cookie banner? Add one tag and LopeBase counts pages, sources, and visits itself, with no visitor ids. Your adapter or your coding agent can add it for you.
Traffic reviewThis week vs last Search clicks up on Product one
Product two lost visits from one referrer
Work on the pricing page next
A traffic review
What is driving visits, what is slipping, and which pages to work on next, with search clicks from the SEO suite alongside.
Conversion and retention
Where people drop off, and what to change first
The conversion and retention review lines up every source you connected: where visitors come from, which pages they land on, which of them sign up or buy, how many come back, and where tracking breaks.
Sources and landing pagesWhich channels and first pages bring people who stay, from your analytics tool and Search Console.
Signups and purchasesGoals and funnels from analytics, with payments from Stripe or Polar and your app's own numbers.
RetentionHow many people come back, where your analytics tool reports it.
Broken trackingWhere a visit and a signup are recorded under different identities, so the funnel cannot be trusted.
The numbers behind each findingEvery finding shows the figures it came from and lists the sources it read.
Track a stepMark a change you made and see whether its number moved the next time you run the review.
Questions
Growth analytics in LopeBase, in plain terms.
Something else? Contact us.
01Can I compare products that use different analytics tools?
Yes. Each product shows its own tool's numbers on the same page. Visits from two different tools are never added together, since they count differently.
02Does LopeBase add its own tracking script to my site?
Only if you choose to. By default it reads the analytics tools you already run, with read-only access. You can also add LopeBase's own one-line tag, which counts pages, sources, and visits with no cookies and no visitor ids.
03Why would I use LopeBase's pageview counter?
It needs no cookie banner, it is served from LopeBase rather than a well-known analytics domain, so fewer visits are lost to blockers, and its sources sit right next to your signups. It works on its own or beside the tools you already run.
04Where do signup numbers come from?
From your own app, through the LopeBase Adapter, a small handler you mount in your product. It shares only the numbers you declare.
05Can my AI agent read the same traffic data?
Yes. The MCP server lets an agent read search and analytics data for every connected site, as aggregates only.
What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 05 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Find the one change worth making this week.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Pricing: free for one product, from $29/month

URL: https://lopebase.com/pricing

LopeBase pricing: Free for one product, Studio $29 a month for 3, Portfolio $99 for 10, Agency $299 with no limit. Two months free on yearly billing.

Pay for products, not seats.
Every plan gets the whole console and a monthly allowance of AI credits. You pay more when you connect more products, add more people, or want the audit log to reach further back.
Plans
Monthly Yearly 2 months free Free
$0 One product, one operator. No time limit.
1 connected product
1 operator
30 days of audit history
50 AI credits a month
Start free Studio
$29 /month$290 /year About $24 a month, billed yearly A few products and a small team.
Up to 3 products
Up to 3 operators
1 year of audit history
500 AI credits a month
Choose Studio Portfolio
$99 /month$990 /year About $83 a month, billed yearly A real portfolio, run day to day.
Up to 10 products
Up to 10 operators
Full audit history
2,000 AI credits a month
Choose Portfolio Agency
$299 /month$2,990 /year About $249 a month, billed yearly Products run for clients, each kept separate.
Unlimited products
Unlimited operators
Full audit history
8,000 AI credits a month
Choose Agency Prices in USD. Yearly billing gives two months free: Studio $290, Portfolio $990, and Agency $2,990 a year, with the same limits as monthly. Every new workspace gets 14 days of Portfolio with no card, then stays on Free unless you choose a plan.
Pricing questions
Something else? Contact us.
01What counts as a product?
Each product you add counts once, however many tools you connect to it. Its admin adapter, Stripe, PostHog, Search Console, and the rest all count as that one product. Your own AI key does not count.
02What is an operator?
A person who can sign in to your console. Each plan sets how many you can add, and each person gets a role.
03What happens to older audit events on a smaller plan?
They are kept. The feed only shows as far back as your plan allows, and the rest comes back into view when you move to a longer plan.
04Can I change plans later?
Yes. Every new workspace gets 14 days of Portfolio, then stays on Free unless you choose a plan. You can move up or down from the billing screen in the console at any time.
05Can I pay yearly?
Yes. Every paid plan can be billed yearly for the price of ten months: Studio is $290 a year, Portfolio $990, and Agency $2,990. You get the same products, operators, and AI credits as monthly, and credits still reset each month. Pick Yearly when you choose a plan, or switch an existing plan between monthly and yearly from Manage subscription on the Billing screen.
06What happens when the trial ends, or I move to a smaller plan?
Nothing is deleted. The products you connected first keep updating, up to your plan's limit, and the rest are paused with their settings and history kept. Choosing a plan with room turns them back on right away. Each person gets one trial.
07Do you need a card to start?
No. The trial and the Free plan need no card, and Free has no time limit.
08What are AI credits?
AI features like drafting articles use credits. A credit costs one cent. Each plan includes a monthly allowance that resets on the first of the month: 50 on Free, 500 on Studio, 2,000 on Portfolio, and 8,000 on Agency.
09What if I run out of AI credits?
Buy a pack of 2,000 credits for $20 from the Billing screen. Purchased credits are used after the monthly ones and do not expire. LopeBase checks the balance before each AI call and caps the call at what is left, so there are no surprise charges.
10Can I use my own AI key instead?
Yes. Add an OpenAI-compatible key under Connections, and AI features use your key and no credits.
11Is there a referral program?
Yes. Every workspace has an invite link. Someone who signs up from yours gets their first paid month free, and when they start paying, you get a free month too. There is no cap.
See every product in one place.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Connect one product for free. Add the rest when you are ready.
Start free Sign in

---

## Revenue

URL: https://lopebase.com/revenue

MRR, active, cancelling, and past-due subscriptions for every product, from Stripe and Polar, with cash and runway from your bank. Read-only keys.

Every product's revenue, and how long the cash lasts.
LopeBase reads each product's Stripe or Polar account with a restricted, read-only key and shows MRR, subscriptions, and the last 30 days of payments for all of them on one page. Connect your bank and the same page shows cash and runway.
Start free See the Revenue page Read-only keys. Free for one product. No card.
The Revenue page
One page instead of one dashboard per account.
Pick one product or all of them. The numbers you check every morning are at the top, each product is a row underneath.
MRR, all products$4,210186 active, 2 past due MRR for every product at once
Monthly recurring revenue and active subscriptions from every Stripe and Polar account you connect, side by side and added up.
Needs attentionRevenue 2 subscriptions past due on Product two
1 subscription set to cancel on Product one
No failed payments on Product three
Past due and cancelling
Subscriptions set to cancel and payments that failed, per product, so you can reach out before they are gone.
Net, last 30 days Payments, gross and net
Gross, net, and one-time payments over the last 30 days, so a lifetime deal or a refund shows up next to the recurring number.
Cash$38,400Runway at the last 30 days' pace Cash and runway
Connect Mercury, Brex, Rho, or Wise to see cash, money in and out, and how many months the cash lasts at the last 30 days' pace.
Revenue reviewAll products MRR up on last month for Product one
Two cancellations on Product two after the price change
Retry the 2 failed payments before they lapse
A review that says what to do
One button reads cancellations, past-due subscriptions, and failed payments and says what to do about each. It reads totals, never customer names or emails. More on the AI reviews page.
Set up in a few minutes
No webhooks to wire and no database access.
01Make a read-only key. A restricted Stripe key that can only read. The Stripe read-only key guide walks through it.
02Connect it to a product. One key per product, so each account stays separate.
03Add your bank, if you like. Banks connect once for the whole workspace and add cash and runway.
04Get told when it matters. Past-due subscriptions show on Overview, in alerts, and in the weekly digest.
How it counts
Revenue numbers are only useful if you can trust them.
Currencies stay apartAmounts in different currencies are never added together. The main currency is summed and the others are listed beside it.
Runway only when cash is fallingRunway is worked out from the last 30 days, and only when more went out than came in.
Read-onlyLopeBase cannot refund, cancel, or change a subscription. It only reads.
Your own MRR, tooA product that bills outside Stripe or Polar can report its MRR through the LopeBase Adapter.
Questions
Revenue in LopeBase, in plain terms.
Something else? Contact us.
01Can I track MRR across several Stripe accounts?
Yes. Connect one restricted key per product and the Revenue page adds them up, with each product on its own row. The guide on tracking MRR across Stripe accounts goes into detail.
02Does it work with Polar?
Yes. Polar accounts show the same numbers as Stripe, and a workspace can mix both.
03Can LopeBase change anything in Stripe?
No. It asks for a restricted key with read access only, so it cannot refund, cancel, or edit anything.
04How is runway worked out?
From your connected bank's cash and the last 30 days of money in and out. When cash grew or held, there is no runway number, because nothing is burning.
05Is there a free way to try the math first?
Yes. The MRR calculator runs in your browser with no signup.
What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 04 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 05 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free See every product's MRR before breakfast.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## SEO suite

URL: https://lopebase.com/seo

Rank tracking, an opportunity map, site audits, Core Web Vitals, index checks, backlinks, and pages competing for one search, from Search Console and Bing.

SEO for every product you run, from data you already own.
LopeBase reads Google Search Console, Bing Webmaster Tools, and Google's real-visitor speed data for each of your sites, then tells you the few things worth doing this week. No estimated traffic, no borrowed keyword volumes. Your numbers, measured against your own site.
Start free Tour the SEO tab Read-only access. Free for one product.
An SEO dashboard that starts with what changed
Most SEO tools open on a wall of numbers. The SEO tab opens on four: clicks, impressions, click rate, and average position for the last 28 days, each with which way it moved against the 14 days before.
Search performanceGoogle, last 28 days 1,284Clicks+18% vs prior 14d 61.2kImpressions+9% vs prior 14d 2.1%Click rate 14.6Avg position+6% vs prior 14d Clicks as the solid line, impressions dashed on their own scale
Every number from Search ConsoleClicks, impressions, click rate, and position exactly as Google defines them. Average position is weighted by impressions, the same way Google computes it.
Which way it is movingThe newer half of the period against the older half, so a slow slide shows up before it costs you a month.
Every product on one listWith several sites, the SEO page starts as one row per product: last week's clicks and a trend line. Click a row to open that product.
Bing beside Google, never added to itA product with both sources shows them as separate rows, because the two count differently.
Opportunities
See every search you show up for, and the ones you are closest to winning.
Pages 11 to 20 of Google are where a site has already earned some trust for a search but gets almost none of the clicks. SEO people call these striking distance keywords. LopeBase draws them so you can spot them in a second.
The opportunity map
Every search as a dot: further right ranks lower, higher up is seen more, and a bigger dot earns more clicks. The page-two band is shaded, so the big dots inside it are next week's work.
141 to 3 384 to 10 4611 to 20 6121 to 50 2251+ Where you rank
How many of your searches land in each stretch of the results. A tall page-two bar means a lot of work is one push away from paying off.
12345678 Your click rate at each position
Built from your own searches, not an industry chart. When position 6 earns less than position 7, the page sitting at 6 has a title problem.
What to do nextSearches on page two, and page-one searches clicked less than your site's own average, sorted by how often they are seen.
A prompt for eachCopy any item as a ready prompt for the coding agent that works on your site, with the numbers attached.
Or write it hereSend a search straight to the content autopilot to plan an article for it.
Your name versus the restClicks from people who searched your product by name, split from everything else, so brand searches do not hide how discovery is going.
Rank tracking without a separate rank tracker
Add the searches that matter to you and LopeBase follows them week by week. Because it reads Search Console's own history, a keyword you add today already has 12 weeks of trend.
Tracked searchesPosition, 12 weeks saas admin panel 7.2 stripe mrr dashboard 11.4 uptime for side projects 5.9 search console for agencies 18.3 Up or down over four weeks, beside each search
Positions Google measuredNot a scraped results page from one data center. Search Console reports where you appeared for real searchers.
Suggestions from your own searchesThe searches that already bring people in, one click to track.
Idea lists, with an AI assistAsk for more searches to track, or tidy a long list into the ones worth keeping. It shows the credit cost first.
Free toolTry the same page-two logic on any Search Console export with the striking distance keyword finder.
Pages
Page by page: what earns search, and what gets in its own way.
The Pages tab turns Search Console's page report into three answers: which parts of your site bring people in, which pages are seen and skipped, and where two of your pages fight over one search.
/blog612 /331 /tools224 /compare117 Clicks by section
Your top folders by clicks from Google, and how many pages each one has in search. Useful when you are deciding where the next month of writing goes.
stripe mrr dashboard /blog/track-mrr pos 9.1 · 54% /features/revenue pos 12.4 · 41% Pages competing for the same search
Often called keyword cannibalization. When two of your pages each take a real share of one search, Google tends to swap between them. Merge them, or make one the clear answer, as Google's guide to consolidating URLs describes.
Seen, rarely clickedPages on page one, seen at least 100 times, and clicked at under half your site's rate. Google writes the result's title link mostly from your title, so that is usually the fix.
Better titles, written for youAn AI review reads each of those pages and suggests a title and description using only the searches the page already shows up for.
Top pagesYour 20 best pages by clicks, with impressions, click rate, and position.
A site audit you will actually rerun
The Health tab answers the questions that decide whether a page can rank at all, and only flags what you can fix.
One-button auditEach finding says why it matters No meta description, so Google writes its own snippet
No canonical link, so copies can compete with it
Tells search engines not to list it (noindex)
Copy every fix as one prompt for your agent
Is Google listing your pages?Checked with Search Console 34of 40 indexed Your newest articles and sitemap pages, up to 40
Speed for real visitorsCore Web Vitals, 75th percentile Loading1.9 sGood Responsiveness140 msGood Visual stability0.18Needs work Trend lines with Google's good and poor bands shaded
The audit reads each page's HTML and checks the basics Google documents: a title, a meta description, a single main heading, a canonical link, a declared language, social preview tags, and no stray noindex. There is no made-up health score out of 100. A finding is either a fix, which hurts search directly, or an improvement, which is worth doing.
Index status comes from the URL Inspection API, the same check as the Inspect URL box in Search Console. Speed comes from the Chrome UX Report: real visits, not a lab test. LopeBase uses Google's published thresholds: loading under 2.5 seconds, responding under 200 milliseconds, and layout shift under 0.1 count as good, measured at the 75th percentile of visits. Google recommends good Core Web Vitals for success in Search.
Health also shows when your domain registration runs out, read from the public registry over RDAP. A lapsed domain takes every ranking with it.
Links
Backlinks, competitors, and where people already talk about you.
Google uses links to find pages and judge how relevant they are. The Links tab shows who links to you, how you stack up, and where a new link could come from.
Who links to youFrom Bing, checked weekly Linking sites flowing into your pages, new and lost each week
Domain RatingYou against your competitors yourproduct.com34 competitor-a.com41 competitor-b.com22 Domain Rating by Ahrefs, by week
Where people talk about itLive, nothing stored Hacker News threads
Lobsters posts
GitHub issues and pull requests
Stack Overflow questions
Places you already have a reason to reply
Competitors found for youSuggested from what your site says and what people search to find it. Only sites whose home page actually answers are kept.
New on competitor sitesPages your competitors published, read from their sitemaps each week, so you see the topics they are going after.
Where to get linksAsk for places that fit your product to earn a link, kept as a list beside your backlinks. It shows the credit cost first.
Honest about the sampleBing's link index is smaller than Google's, and the page says so. Google does not offer a full backlink API.
Hand the work to your coding agent
Every finding in the SEO tab can be copied as a prompt with the numbers attached. Or connect Claude, Cursor, or any MCP client to LopeBase and let the agent read the same data itself.
Which of our searches are on page two, and which page should answer each?read_source search_queriesread_source page_queries"saas admin panel" sits at 13.2 with 2,410 impressions. /features is the closest page; it never says "admin panel" in a heading... Search Console over MCPQueries, pages, daily trends, and index checks. See what an agent can read.
The whole SEO toolkitAudits, tracked searches, and links through one server. See SEO over MCP.
Read-only search accessThe agent reads the same Search Console and Bing data you see. It cannot change your Search Console settings.
Where the data comes from
Every number in the SEO tab has a source you can open yourself. Nothing is estimated from a third-party clickstream.
Google Search ConsoleClicks, impressions, click rate, position, pages, and index status, through Google's own APIs with read-only access. See the Performance report help.Runs a couple of days behind Bing Webmaster ToolsBing search traffic and inbound links. About Bing Webmaster Tools.Links checked weekly Chrome UX ReportCore Web Vitals from real Chrome visits, 25 weeks of history. About CrUX.Updated weekly by Google AhrefsDomain Rating for you and your competitors. What Domain Rating means.Checked weekly Public sourcesDomain expiry over RDAP; mentions from the Hacker News API, Lobsters, GitHub search, and the Stack Exchange API.Read live Faster indexingNew articles from the content autopilot can be announced through IndexNow to the search engines that support it.On publish Questions
How the SEO tools work, in plain terms.
Something else? Contact us.
01Do I need a paid SEO tool to use this?
No. The core of it runs on Google Search Console and Bing Webmaster Tools, which are free, and on Google's public Chrome UX Report. Domain Rating comes from Ahrefs through LopeBase's own key; you do not need an Ahrefs account.
02Why no search volume or keyword difficulty?
Those figures are estimates from third-party data, and they often disagree with each other. LopeBase sticks to what search engines report about your own site: how often you were seen, clicked, and where you ranked. That is what the next decision should rest on.
03How is this different from opening Search Console?
Search Console shows the raw report for one site. LopeBase reads it for every product you run, compares each period with the one before, picks out page-two searches and pages that are seen but skipped, finds pages competing for the same search, and turns each into a next step or an article.
04What is keyword cannibalization, and does it matter?
It is when two pages on your site both show up for the same search. Google usually picks one at a time and can switch between them, so neither ranks as well as one strong page would. LopeBase only flags it when each page takes at least a tenth of the search's impressions, so a stray result does not count.
05Can LopeBase change my site?
No. Search access is read-only. Fixes come to you as findings and prompts; your site only changes when you or your agent make the change, or when you publish an article through the content autopilot.
06Which parts use AI credits?
The AI review of titles and descriptions, competitor discovery, keyword suggestions, and finding places to get links. Each shows its cost before it runs. Everything else, including the charts, audits, index checks, and speed data, uses none.
Sources
The documentation behind the definitions and thresholds on this page. Checked October 2026.
What are impressions, position, and clicks? Search Console Help.
Performance report (Search results). Search Console Help.
URL Inspection API. Google for Developers.
Web Vitals. web.dev.
Understanding Core Web Vitals and Google search results. Google Search Central.
Chrome UX Report overview. Chrome for Developers.
Influencing your title links. Google Search Central.
Control your snippets in search results. Google Search Central.
How to specify a canonical URL. Google Search Central.
Block search indexing with noindex. Google Search Central.
Link best practices for Google. Google Search Central.
What is Domain Rating (DR)? Ahrefs Help Center.
IndexNow.
Registration Data Access Protocol (RDAP). ICANN.
A weekly SEO routine for several products The checks in this page, as a 20 minute routine.Search Console What LopeBase reads, and how to connect it.Content autopilot Turn page-two searches into articles on a calendar. What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 02 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 03 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 04 / Reliability Hear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
15 minute checksAlertsIncident review See how it works 05 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Know what to fix in search, for every product, every week.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing

---

## Free tools

URL: https://lopebase.com/tools

Free tools for people who run SaaS products: an MRR calculator, a Search Console analyzer, a striking distance finder, and a Stripe read-only key builder.

Free tools for people who run SaaS products.
Each one runs in your browser, needs no account, and never uploads what you type.
The tools
Revenue Portfolio MRR calculator
Add up MRR and ARR across every product, with yearly plans and discounts handled.
For founders with more than one product Open Search Search Console analyzer
Drop in a Search Console export to see searches seen but not clicked, and pages losing clicks.
For anyone who looks after a site's SEO Open Search Striking distance finder
Find the searches you rank for on page two, sorted by the clicks a move up could bring.
For writers and founders planning page edits Open Stripe Stripe read-only key
Pick what a tool needs to see and get the exact restricted key permissions to set to Read.
For anyone sharing Stripe access with a tool Open Want these numbers kept current for every product?
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic LopeBase reads Stripe, Search Console, and the rest for you. Free for one product. No card.
Try LopeBase free See features

---

## MRR calculator

URL: https://lopebase.com/tools/mrr-calculator

Free MRR calculator for more than one SaaS product. Add plans per product, normalize yearly and quarterly billing, apply discounts, and see total MRR and ARR.

More free tools Portfolio MRR calculator.
Add up monthly recurring revenue across every product you run. Yearly and quarterly plans are normalized to a month and discounts are applied. Everything runs in your browser; nothing you type is sent anywhere.
How to use it
Add each productOne card per product you run. Name it so the totals by product are easy to read.
Add its plansPrice, how often it bills, how many subscribers, and any ongoing discount. Yearly and quarterly plans are turned into a monthly figure.
Monthly›Quarterly›Yearly
Read your totalsPortfolio MRR, ARR, and ARPU update as you type. Copy the summary to share it.
Portfolio MRR$0 ARR$0Subscribers0ARPU$0 Copy summary Want this updating itself?LopeBase reads each Stripe account with a read-only key and keeps portfolio MRR current.Start free Add a product How the numbers are worked out
Each plan's MRR is its price, divided by the months in its billing period, times the number of subscribers, minus any ongoing discount. Products are summed into portfolio MRR. ARR is MRR times twelve, and ARPU is MRR divided by paying subscribers.
Leave out one-off charges, setup fees, and free trials. If your products charge in different currencies, convert to one currency first. More detail in how to track MRR across multiple Stripe accounts.
The numbers, defined
The same definitions apply whether you run one product or ten. The only extra rule with several products is to add them up after each one is normalized to a month.
MRRMonthly recurring revenue: what active subscriptions bring in each month, after ongoing discounts. One-off charges are left out.
ARRAnnual recurring revenue: MRR times twelve. A yearly plan's price is not ARR on its own until it is spread across the year.
ARPUAverage revenue per user: MRR divided by paying subscribers. Free users and trials are left out.
Portfolio MRREach product's MRR, added together. Keep each product on its own row too, so a dip in one is not hidden by growth in another.
A worked example
Take the two products the calculator starts with. Product one has 40 subscribers on a $19 monthly plan, which is $760, and 12 on a $190 yearly plan, which is $190 divided by 12, times 12 subscribers: $190. Its MRR is $950.
Product two has 25 subscribers on a $29 monthly plan with a 10% ongoing discount: $29 times 25 is $725, less 10%, which is $652.50.
Portfolio MRR is $950 plus $652.50, or $1,602.50. ARR is that times twelve, $19,230. With 77 paying subscribers, ARPU is about $20.81.
The figures are only the calculator's starting values. Change them, and it updates as you type.
MRR questions
Something else? Contact us.
01How do you count a yearly plan in MRR?
Divide the yearly price by twelve. A quarterly plan is divided by three.
02Do discounts reduce MRR?
Ongoing discounts do. Use what customers actually pay each month. A discount that ends only counts while it lasts.
03Should free trials count toward MRR?
Most teams leave trials out until the first paid invoice. Whatever you choose, apply it the same way every month.
04Is MRR the same as monthly revenue?
No. Monthly revenue is what was charged in a month, including one-off sales and yearly plans billed that month. MRR spreads recurring plans evenly across months and leaves one-off charges out, so it moves only when subscriptions change.
05How do I add up MRR across products in different currencies?
Convert each product's MRR to one currency first, at a rate you keep the same from month to month, then add them. Otherwise exchange rates move your total even when nothing else changed.
06Is anything I type saved or sent?
Nothing is sent anywhere. Your products are kept only in your own browser, so they are still there when you come back.
07What is the MRR formula?
MRR is the sum of what every active subscription pays per month. For each plan: price divided by the months in its billing period, times its subscribers, minus any ongoing discount. Add the plans up for one product, then the products up for your portfolio.
08What is the difference between MRR and ARR?
ARR is MRR times twelve. Both measure recurring revenue only; ARR is the yearly view, common once yearly plans make up much of revenue.
09How do I calculate MRR from Stripe?
Add up active subscriptions, each normalized to a month, and leave out one-off charges, trials, and canceled subscriptions. LopeBase does this from a read-only Stripe key for every product you run.
10Do one-time payments count toward MRR?
No. One-time payments are real revenue but not recurring, so keep them separate. Tracking them next to MRR, rather than inside it, shows growth without blurring the two.

---

## Search Console analyzer

URL: https://lopebase.com/tools/search-console-analyzer

Free Search Console export analyzer. Find searches with many impressions and few clicks, and the queries or pages losing clicks, from your own CSV.

More free tools Search Console export analyzer.
Drop in a Google Search Console export and see what to fix first: searches that get seen but not clicked for where they rank, and the queries or pages losing clicks since the period before. It runs in your browser; your data is never uploaded.
How to use it
Export from Search ConsoleFor the Losing clicks view, turn on Compare in the date filter first, for example the last 3 months against the 3 before.
Performance›Date›Compare›Export›Download CSV
Drop in Queries.csv or Pages.csvUnzip the download and drop one file below. The impressions floor sets itself to fit your site.
Fix what it findsRewrite titles for searches seen but not clicked. Check pages losing clicks: lower impressions means less demand, a lower position means a ranking drop.
Drop Queries.csv or Pages.csv here or click to choose it. For losing clicks, export with Compare dates turned on in Search Console. At least impressions Try sample data
Rows0 Clicks0 Impressions0 Click rate0 This export covers one period, so Losing clicks has nothing to compare. Export again with Compare turned on, then drop the new Queries.csv or Pages.csv here.
Performance›Date›Compare›Last 3 months vs previous›Export Seen, not clicked Losing clicks
Download this view as CSV Find striking distance keywords Watch this every week What the analyzer finds
Seen, not clickedSearches whose click rate is less than half of your own average for that position. The page ranks, but the title or description does not win the click. Rewriting them is often the quickest gain in Search Console.
Losing clicksWith a Compare export, the queries or pages that lost the most clicks between the two periods, with what happened to their impressions and position, so you can tell a ranking drop from a demand drop.
Measured against youClick rates are compared with your own site's rates at each position, from the same export, not with an industry chart that may not fit your searches.
Looking for searches just off page one instead? The striking distance keywords finder takes the same export.
Search Console analyzer questions
Something else? Contact us.
01How do I find keywords with high impressions and low clicks?
Drop your Queries.csv above. The Seen, not clicked view lists searches whose click rate is under half of your site's own average at that position, sorted by impressions. Those are the titles and descriptions to rewrite first.
02How do I find pages losing traffic in Search Console?
Export the Pages report with Compare dates turned on, then drop Pages.csv above. The Losing clicks view sorts pages by clicks lost, and shows whether impressions or position fell too.
03Why compare with my own click rates instead of a CTR curve?
Published CTR curves average many sites and many kinds of search. Your own rate at each position, from the same export, is a fairer bar for your pages.
04Is my Search Console data uploaded?
No. The file is read in your browser and never sent anywhere.
05Can I get this every week without exporting?
LopeBase reads Search Console and Bing for every site you run and shows the searches and pages to work on, with alerts when something drops. It is free for one product.
06What is a good click-through rate in Search Console?
It depends on position, the search, and what else is on the results page, so there is no single good number. Comparing each search with your own site's rate at the same position, as the analyzer does, is a fairer test.
07Why are my impressions high but clicks low?
Usually one of three things: you rank low on the page, your title and description do not match what people searched, or the results page answers the question itself. The Seen, not clicked view shows the ones where your position is not the reason.
08Why did my Search Console clicks drop?
Check impressions and position for the pages that lost clicks. Fewer impressions at the same position means fewer people searched. A lower position means the page lost ground. The Losing clicks view puts both side by side.
09How do I export Search Console data to CSV?
In Performance, Search results, choose Export at the top right, then Download CSV. The zip holds Queries.csv, Pages.csv, and more, each with up to 1,000 rows.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Striking distance finder Searches just off the top, sorted by the clicks a move up would bring.Search Console connector Clicks, searches, and positions for each site, read-only.Content autopilot Drafts for the searches worth winning, checked before they publish.

---

## Striking distance finder

URL: https://lopebase.com/tools/striking-distance-keywords

Free striking distance keyword finder. Drop in your Search Console export to find searches on page two, sorted by the clicks a move to the top would bring.

More free tools Striking distance keywords finder.
Find the searches you already rank for just off the top of Google, the low-hanging fruit on page two, where an edit to an existing page can move you up. Drop in your Search Console export and get them sorted by the clicks each one could bring. It runs in your browser; your data is never uploaded.
How to use it
Export from Search ConsoleOpen your property and set the date range. Three months smooths out day-to-day swings.
Performance›Search results›Export›Download CSV
Drop in Queries.csvUnzip the download and drop the Queries file below. Pages.csv works too, by page.
Work down the listPick a position range. The top rows are where moving up is worth the most clicks. Download the list as CSV.
Drop your Queries.csv here or click to choose it. From Search Console, Performance, Export, then the Queries file. Pages.csv works too. Or paste the rows
Find them Positions 11 to 20 (page two)4 to 20 (just off the top)4 to 10 (bottom of page one)11 to 30 (pages two and three) At least impressions Try sample data
Searches in range0 Their impressions0 Extra clicks at your top-3 rate0
SearchPositionImpressionsClicksCTRExtra clicks Download as CSV Track these every week How the finder works
A striking distance keyword is a search your site already ranks for, close enough to the top that improving an existing page can move it, rather than writing something new. The finder keeps the rows whose average position falls in the range you pick and that have at least the impressions you set, so one-off searches do not crowd the list.
The extra clicks column is an estimate from your own data, not an industry average. The finder takes the click-through rate of the searches in your export that already sit in positions 1 to 3, and asks: if this search reached that rate, how many more clicks would its impressions have brought? That is its impressions times your top-3 rate, minus the clicks it already gets. When your export has fewer than five searches in the top three, there is not enough to go on, so the list is sorted by impressions instead and the column is left blank.
Position in Search Console is an average across every time you appeared, so a 12 can mean you were sometimes 6 and sometimes 18. Treat the estimate as a way to rank the list, not a forecast.
What to do with the list
Find the page that ranksSearch the query in Search Console's Pages tab to see which page shows up. Work on that page, not a new one.
Answer the search directlyPut the answer near the top, and use the words people search in a heading where it reads naturally.
Fix the title and descriptionA search with many impressions and few clicks often has a title that does not match what people asked.
Link to it from your own pagesLinks from related posts, with words close to the search, help the page that should rank.
Then give it a few weeks before judging. Positions move slowly, and one week of data is mostly noise.
Striking distance questions
Something else? Contact us.
01What is a striking distance keyword?
A search your site already ranks for just below the top results, usually somewhere from position 4 to 20. It is close enough that improving the page that ranks can move it up, which is often faster than ranking a new page.
02Are striking distance keywords the same as low-hanging fruit keywords?
Mostly, yes. Both mean searches you already rank for but not quite at the top, where a small change to a page you have can bring more clicks. Some people use low-hanging fruit more loosely, for any search with many impressions and few clicks, which the finder also shows in its CTR column.
03How do I find keywords on page 2 of Google?
Export the Queries report from Search Console and keep the rows with an average position from 11 to 20. Pick "11 to 20 (page two)" above and the finder does it for you, sorted by what moving up is worth.
04Which position range should I use?
Page two, 11 to 20, is the classic choice: those searches get impressions but almost no clicks. 4 to 20 adds the bottom of page one, where moving up a few places still matters. Try both.
05Is my Search Console data uploaded?
No. The file is read by your browser and never sent anywhere. Close the tab and it is gone.
06Why are some searches missing from my export?
Search Console leaves out searches that only a few people made, to protect their privacy, and an export stops at 1,000 rows. Filtering the report before exporting gets you more of the long tail.
07How is this different from the Search Console report itself?
Search Console can filter by position, but it does not rank searches by what moving up is worth. The finder does that with your own click-through rate, and lets you download the list.
08Can I track this over time?
LopeBase reads Search Console and Bing for every site you run, lists the searches sitting on page two, and drafts content for them if you want. It is free for one product.
09Does this work with a Bing Webmaster Tools export?
Usually. Any CSV with a keyword or query column, impressions, and an average position works, and Bing's keyword export has those.
10How long does it take to move up from page two?
It varies with the search and the competition, so give a change a few weeks before judging. Search Console updates daily, but one week of positions is mostly noise.
11Should I write a new page or improve the one that ranks?
Improve the one that ranks first. Google already connects it with the search, so a better answer, title, and internal links on that page usually move it faster than a new page starting from nothing.
The SEO suite Every SEO tool in LopeBase, from rank tracking to pages competing for one search.Search Console analyzer Searches seen but not clicked, and what is losing clicks.Portfolio MRR calculator Add up MRR across every product you run.Content autopilot Drafts for the searches on page two, checked before they publish.Search Console connector Clicks, searches, and positions for each site, read-only.

---

## Stripe read-only key

URL: https://lopebase.com/tools/stripe-restricted-key

Make a read-only Stripe restricted key. Pick what a tool needs to see and get the exact permissions to set to Read, with everything else left at None.

More free tools Stripe read-only key builder.
When an analytics tool, a dashboard, or your bookkeeper asks for Stripe access, give it a restricted key that can only read what it needs, never your secret key. Pick what the tool needs to see and get the exact permissions to set to Read. Everything else stays at None.
How to use it
Pick what the tool needsTick what it has to see, or start from a preset. The list shows exactly which permissions to set to Read.
Create the key in StripeName it for the tool, set the listed permissions to Read, and leave everything else at None.
Developers›API keys›Create restricted key
Check it and hand it overIt should start with rk_live_. Type the first characters below to check, then give the tool that key only.
Start from: Revenue and MRR dashboard Bookkeeping Customer support LopeBase What does the tool need to see? Set these to Read0 Leave every other permission at None. Nothing needs Write.
Copy the list Open Stripe API keys Is this the right kind of key?
Type just the first few characters. You never need to paste a whole key here, and nothing you type leaves your browser.
Start typing the key's first characters.
Why a restricted key, not your secret key
A secret key can do anythingRefund payments, cancel subscriptions, change payout details, read every customer. If a tool you gave it to is breached, so is your Stripe account.
A restricted key does only what you choseSet to Read, it can look but not change. A leak shows numbers, it cannot move money.
One key per toolName each key for the tool using it. When you stop using the tool, revoke that one key and nothing else breaks.
Read only what it needsA revenue dashboard does not need disputes or payouts. Fewer permissions means less exposed if anything goes wrong.
Stripe's own guide to restricted keys is at docs.stripe.com/keys/restricted-api-keys. The permission names in the builder are the ones the Dashboard shows, from Stripe's permissions reference, checked October 2026.
Restricted key questions
Something else? Contact us.
01How do I make a read-only Stripe API key?
Create a restricted key in the Stripe Dashboard under Developers, API keys. Set the resources the tool needs to Read and leave everything else at None. The builder above lists which ones to set.
02What is the difference between rk_live and sk_live?
Keys starting sk_live_ are secret keys with full access to your account. Keys starting rk_live_ are restricted keys that can only do what you allowed when you created them. Share restricted keys with tools; keep secret keys to your own servers.
03Which permissions does a revenue or MRR dashboard need?
Usually Subscriptions, Customers, Charges and Refunds, and Invoices, all at Read. Some tools also read Prices and Products to name plans. Check the tool's own setup guide too, and start from the Revenue preset above.
04Can I change a restricted key's permissions later?
Yes. Edit the key in the Dashboard and change any permission. The key itself stays the same, so the tool keeps working with the new access.
05Does a restricted key work in test mode?
Yes. Create it while viewing test data and it starts with rk_test_. Test and live keys are separate, so make one of each if a tool needs both.
06Is anything I choose here saved or sent?
No. The builder and the key check run in your browser. Never paste a full secret key into any website, this one included.
07Is it safe to give a restricted key to a third-party app?
Much safer than a secret key. A read-only restricted key cannot move money or change your account, and you can revoke it on its own at any time. Give each app its own key so you can see and cut off each one separately.
08How do I revoke a Stripe API key?
In the Dashboard, open Developers, then API keys, open the menu next to the key, and delete it. The tool using it stops reaching Stripe right away; nothing else is affected.
09What happens if a tool's key is missing a permission?
Stripe refuses that request with a permissions error, and the tool usually shows the data as missing. Edit the key, set the missing resource to Read, and the same key works without changing it in the tool.
Stripe connector MRR, one-time revenue, and past-due payments for each product, from a read-only key.Portfolio MRR calculator Add up MRR across every product you run.Baremetrics vs ChartMogul Two subscription analytics tools, side by side.

---

## Uptime and incidents

URL: https://lopebase.com/uptime

Every site checked every 15 minutes, a year of uptime history, alerts by email or push, a free public status page, and an incident review.

Hear about an outage before your customers do.
Add the address of any site or health page. LopeBase checks it every 15 minutes, keeps a year of uptime history, and tells you the moment it stops answering. Give customers a public status page, free, and tell them what happened when it is over.
Start free See what you get No key or account needed for a site check. Free for one product.
Uptime and incidents
Is it up? For every product, already answered.
One page for every site you run, next to the revenue and traffic that depend on it.
Product oneUp Product twoUp Product threeUp Checked every 15 minutes
Each uptime check records the status and response time. You get uptime over 24 hours, 7 days, 30 days, 90 days, and 12 months, every outage in the last 30 days, and response times for the last 24 hours.
DatabaseUp Job queueUp Public APIUp Every service, not just the home page
A home page can load while checkout is broken. List the database, queue, workers, or second API your app needs in the LopeBase Adapter, and one check watches each of them. One service down marks the product degraded and alerts you.
Product three is downEmail and browser pushOpen Alerts where you are
A site that stops answering alerts on the first failed check, by email or browser push, the way each person chose.
Top errorsProduct two TypeError in checkout, 41 events
Timeout calling the email provider
No new errors on Product one
Errors beside uptime
Bring in Sentry, Bugsnag, Honeybadger, or Rollbar, or the Better Stack monitors you already run.
Status page noteDrafted from Tuesday's outage, ready to postPost An incident review and a note for customers
One button reads 30 days of checks and each outage, plus your top Sentry errors, then says what went wrong and what to fix first. After downtime it drafts a calm status note. Read it, then post it to your status page in one click or copy it anywhere.
All systems upProduct one status pageRSS WebsiteUp APIUp A public status page, free
Turn one on for any product with a single switch. Customers see live status, 90 days of history, a year of uptime, and the notes you post. Pick which parts show, follow it by RSS, and put a live status badge on your site. Paid plans can add their logo and colors and leave off the LopeBase footer.
How it works
The first check runs as soon as you add a site.
01Add an address. Your home page or a health endpoint. No key or account needed.
02Pick how to hear about it. Email, browser push, or both, per person.
03See it with everything else. Outages show on Overview and in the weekly digest.
04Close the loop. Run the incident review and post its note to your public status page.
Questions
Uptime in LopeBase, in plain terms.
Something else? Contact us.
01How often are sites checked?
Every 15 minutes. Each check records whether the site answered and how long it took.
02Do I need an account with another monitoring tool?
No. Uptime checks are built in and need only an address. If you already use Better Stack, you can connect it and see those monitors too.
03Can one product have several things checked?
Yes. Point the product's check at the adapter's health address and declare each service there: the database, a queue, workers, payments, or another host you run. Each check uses your app's own credentials, so it shows your integration works, and a service you mark non-critical shows as degraded instead of down. The Uptime page and alerts then name the service that failed.
04How do I know what is worth watching?
Run npx lopebase in the product's folder. It reads dependency names and lists the site, databases, queues, and email it finds, and your coding agent confirms the list against the code before adding anything.
05How do alerts reach me?
By email, by browser push, or both. Each person picks what they hear about, and only for the products they can see.
06Does LopeBase publish a status page?
Yes, if you want one. Turn it on from the Uptime page and you get a public link with live status, 90 days of history, a year of uptime, and your own notes. It shows your site's icon and is free on every plan. Paid plans can add their logo, pick colors and light or dark, and leave off the LopeBase footer.
07Can customers follow updates?
Yes. Every status page has an RSS feed of your notes, and a badge you can put on your site or README that shows live status and links to the page. Your own team can also get each new note by email or browser push from their alert settings.
08How long is uptime history kept?
Every single check for 35 days, and a total for each day for a year, so uptime over 90 days and 12 months stays on the page.
What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / Content Publish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / Revenue Know your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / Growth Turn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / Agents Let your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it works Not sure where to start? Connect one tool and Overview shows what needs you first.
Start free Sleep through the night, and know if you should not.
StripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubStripePostHogGoogle AnalyticsSearch ConsoleSentryGitHubCloudflareBingResendEmDashOpenAIAnthropicCloudflareBingResendEmDashOpenAIAnthropic Free for one product. No card.
Start free See pricing