Skip to content

Your real numbers in, your own domain out

Canopus is an autonomous growth manager that reads the data a SaaS already has, Stripe and PostHog by read-only API key, and sends email from the founder’s own domain once its DNS records are published.

Two keys, pasted once, and three or four DNS records, published once. Your revenue and sign-ups appear the same day, every later decision is made against those numbers rather than a guess, and your campaigns leave from the domain you already own. Nothing you connect can be written to, you connect no email tool at all, and everything read is stored in the EU. Stripe also fills the CRM, which is where everything else starts.

What does connecting a source actually involve?

  1. The permissions are listed before you leave

    The Stripe form shows the exact permissions the key needs, Customers and Subscriptions in read, while you are still on the page. You create the restricted key in Stripe with those two boxes ticked and paste it back. The account permission is not asked for: it buys a display name on the tile and nothing else.

  2. The key is proven against the live API, then stored

    Each permission is probed separately before anything is written. A key that lists customers but cannot read subscriptions is refused by name, with the fix attached, instead of connecting and then reporting an account with no revenue. Only a key that answered is encrypted and saved.

  3. The first sync reads ninety days back

    Stripe fills daily revenue and your customer list, PostHog fills sign-ups, active users and the busiest event names. After that the sync runs on its own, once a day, resuming where the last one stopped, and a source that goes quiet is flagged rather than left silent.

  4. Your sending domain is verified, then Canopus sends from it

    Add the domain you send from. Canopus shows the three or four DNS records to publish, checks them, and marks the domain verified. From then on campaigns leave from that domain under your sender name, and deliverability, bounces and complaints are handled for you. Each plan carries a monthly email quota: 5,000, 25,000 or 100,000.

What does this replace?

  • Exporting a Stripe CSV on the first of the month and pivoting it in a sheet.

    Daily revenue and subscriptions are read for you and kept as one row per day.

    Replaces: Stripe CSV export
  • Reading MRR in one tab, product usage in another, and joining them by eye.

    Stripe and PostHog are joined on email, the only identifier both agree on.

    Replaces: Two browser tabs
  • Paying a sending tool and configuring it for a domain you already own.

    You publish the DNS records once; Canopus sends from your domain and manages its reputation.

    Replaces: An email sending tool
  • Finding out a revoked key broke your reporting long after it happened.

    A connector that has not synced in 36 hours is flagged rather than left quiet.

    Replaces: Noticing by accident
  • Keeping API keys in a password manager, a .env file and a shared note.

    One encrypted record per source per organization, with the last four characters shown.

    Replaces: A shared note

What does Canopus read, what does it send, and what does it never touch?

Stripe is the authority on money. The connector reads your customers and your subscriptions, nothing else. It never writes: there is no create, no update, no refund, no cancellation anywhere in the driver, and the restricted key you are asked to make cannot perform one even if the code tried. Card numbers are not read and could not be: Stripe does not expose them to an API key of any kind. From the subscription list it builds one revenue figure per day for the last ninety days, plus the plan, the status and the amount for each person who pays you. A sync reads at most 5,000 objects from a single list, and when it hits that ceiling it says so in the log and on the connector page rather than presenting half your revenue as all of it.

PostHog is the authority on behaviour. It is read through a personal API key, the only kind that can read anything, and the form refuses a project key by prefix before a request is made, because PostHog answers every bad key with the same 401 and the distinction has to be drawn on this side. The connector asks for new identified people per day, active users, activation, retention cohorts and the busiest event names in your product. Those event names are the closest thing to a real feature list that exists anywhere: they come from what people do rather than from what your marketing page claims. PostHog writes nothing into your customer list. A tool that observes people does not get to decide who is a customer.

The sending domain is not a connector, and that is the point. You never connect an email tool. You add the domain you send from, and Canopus shows you the three or four DNS records to publish: DKIM for signing, SPF and a return path for bounces, DMARC for policy. It checks them until each one reads verified, and from then on it sends on your behalf from that domain, under your sender name, with your postal identity in the footer. Deliverability, bounces and complaints are handled by Canopus, and the reputation earned or lost is your domain’s rather than a pool shared with other customers. Each plan carries a monthly email quota (5,000 on Starter, 25,000 on Growth, 100,000 on Scale), and sending stops at the quota rather than turning into a surprise invoice.

Keys are encrypted with AES-256-GCM under a secret that lives in the deployment environment and never in the database. Each ciphertext is bound to the organization and the source it belongs to, so a record copied from one organization into another fails to open rather than decrypting into the wrong hands. The queries that draw the interface omit the column entirely; exactly one piece of code decrypts a key, and it runs inside the job queue for the length of one sync. Keys are never logged, never sent to a model, and never displayed. What you see on the tile is the last four characters, which is enough to recognise a key you already hold and worthless to anyone who does not.

Everything read is stored in the EU: Supabase Postgres in a Paris or Frankfurt region, with functions running in Paris. A connector that stops working is noticed by a job that runs on its own and lists every connection whose last successful sync is older than 36 hours, or that has never synced at all. A revoked Stripe key otherwise produces the most expensive kind of silence, a revenue chart that stops moving and looks like a slow quarter.

Stripe on its own is enough to start. PostHog and the sending domain each degrade visibly rather than breaking: with no PostHog, the product brief says plainly that it worked from the site alone and the ideal customer profile is capped at speculative; with no verified domain, campaigns are written and wait for your approval, and approval asks for the domain. Disconnecting a source deletes the encrypted key immediately and stops the sync, and it leaves the numbers already collected in place. Your revenue history, your contacts and your metric rows are yours, and removing a key is not a reason to erase them.

Questions founders ask

See your own numbers first

Connect Stripe and your real revenue is on screen in five minutes, before an agent has said a word. Create your account, answer the questions, and your strategy gets written.