Connect the tools you use. Read-only by default.
Stripe, PostHog, Search Console, Sentry, your bank, your blog, and the rest of your stack. Sign in with one click or paste a key, match it to a property, and its numbers show up next to everything else.
- Read-only keys, except to publish what you approve
- Keys encrypted, never shown back
- Free for one property
LopeBase reads Stripe, Polar, PostHog, Google Analytics, Search Console, Bing Webmaster Tools, Sentry, GitHub, Cloudflare, Supabase, Resend, Mercury, and more, and puts their numbers in one console.
Pick what to connect
Every connector, grouped by what it is for. Open one to see exactly what LopeBase reads, what it leaves alone, and how to connect it.
Payments
Recurring revenue and payments, added up across every account.
Analytics
Visitors and what they do, side by side for every product.
Search
How people find you on Google and Bing, and who links to you.
Uptime and errors
Whether each site is up, and what is breaking inside it.
CMS
Your blog's posts and their SEO health. Content can publish the articles you approve.
Banking
Cash, money in and out, and months of runway next to what each product earns.
Whether your email lands, and who is on your lists.
Infrastructure
Builds, deploys, and database health for the code behind each product.
AI
Bring your own model for drafting and reviews, or use LopeBase's monthly credits.
Your own app
Users, signups, plans, and the actions you choose, straight from your product.
Comparing dashboards before you connect anything? See how LopeBase compares with Baremetrics, ChartMogul, Databox, and others.
How connecting works
Each connector asks for the narrowest access the service offers, and the connect dialog walks you through it. Where a service lets a link fill in the key's name and permissions, the link does, so you only press Create.
Open Connections and choose a tile. Tools are grouped by job: money, analytics, search, monitoring, content, and more.
Google, GitHub, Cloudflare, and Bing connect with one sign-in. For the rest, the dialog links to the right page with read permissions filled in where the service allows it.
When a key can see several projects or sites, LopeBase lists them so you match each one, or connect all your products from the one key.
They land on Overview and the screen they belong to. If a key stops working, it shows under Needs attention with a Reconnect link.
The help center has the details: Connect your tools, Connect Search Console and Google Analytics, and Connect Stripe and Polar.
Read-only by design.
LopeBase fetches your numbers. It does not change anything in Stripe, Search Console, or any other tool you connect.
- The narrowest access each service offers. Google asks for one read scope. Stripe gets a restricted key set to Read, never a secret key. The Stripe read-only key builder lists the exact permissions.
- Every key encrypted before it is saved. Each one gets its own encryption key, which is itself wrapped under a key for your workspace.
- Never shown back. Not in the app, and not over the MCP server. LopeBase only uses a key to call the service it belongs to.
- The few exceptions, said plainly. Sequenzy can turn a sequence on or pause it when you press that button, and the CMS connectors publish only the articles you approve.
- Never your database. Your own records come through the LopeBase Adapter, which shares only the fields you declare.
Connect your first property today.
Every new workspace gets 14 days of Portfolio, no card. Then Free, unless you choose a plan. Plans count properties, not connections, so connect as many tools as each property uses.
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", }, },
Or let your coding agent connect it.
Run npx lopebase in a product's folder. It reads your stack without opening a real .env file, connects this computer to your workspace, and hands setup to Claude Code, Codex, or another agent. Your agent adds the product and connects its tools, and stops to ask you for any sign-in or key.
Already in an agent? The LopeBase MCP server gives it the same tools, with a token you create in Settings.
Connector questions
Something else? Contact us.
Can 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, WordPress, Ghost, Webflow, Shopify, Contentful, and Sanity publish only the articles you approve.
Does 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.
How are my keys stored?
Each key is encrypted before it is saved, with its own encryption key wrapped under a key for your workspace. Nobody reads a stored key back, in the app or over the MCP server. You can remove a connection at any time. See how LopeBase handles your data.
Which tools connect with one click?
Search Console and Google Analytics connect with a Google sign-in, and Bing, Cloudflare, Cloudflare Web Analytics, and GitHub with their own. Uptime checks need no key at all. The rest take a key you create in that service, and the connect dialog links you to the right page.
Can one key cover several products?
Yes. When a key can see more than one project or site, like PostHog, Sentry, GitHub, Supabase, or Bing, LopeBase lists what it can see so you match each one to a product, or connect all your products from the one key.
Do my connections count against my plan?
Plans count products, not connections. A product's Stripe account, analytics, Search Console property, and the rest all count as that one product. See pricing.
What happens if a key stops working?
When the service confirms a key or sign-in no longer works, the connection shows as needing a reconnect, with a Reconnect link next to its numbers. A service that is only busy is never reported as failing; LopeBase reads it again on the next pass.
What 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.
Start from what you want to get done
Pick the job, and the goal page shows which connectors it reads.
Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Find your search winsGet named when people ask AI
See whether ChatGPT, Claude, and Gemini mention you for your buyers' questions, and who they name instead.
Check your AI answersPublish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
Plan your articlesKnow your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
Track your MRRTurn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
Grow your signupsHear about outages first
Every site checked every 15 minutes, alerts by email or push, and a status note drafted for you.
Watch your sitesKnow what changed this week
One button reads a page's numbers and says what changed, what is at risk, and what to do next.
Read your weekLet your coding agent set it up
Run one command and your agent adds properties and connects sources over MCP.
Use your agentNot sure where to start? Connect one tool and Overview shows what needs you first.
Start freeBring every tool into one place.
Connect one product for free. Add the rest when you are ready.
- 14 days of Portfolio free
- Read-only keys
- Cancel any time