Your numbers, read-only
Connectors are how Canopus knows your MRR, your signups and what users do in your product. Both run on keys you create with read permissions only. Canopus never writes to your Stripe account or your PostHog project, and the keys are encrypted at rest.
Stripe
Create a restricted key
In Stripe, under Developers, then API keys, create a restricted key. Set exactly two permissions to Read: Customers and Subscriptions. Everything else can stay at None.
Paste it in Canopus
On the Connectors screen, paste the key. A publishable key or a key missing a permission is refused with a message naming what is wrong.
What Canopus reads: your customers, your subscriptions (all statuses) and your products. From them it computes daily MRR, active subscriptions, trials, new and churned customers over a 90 day window, plus per-contact billing facts in the CRM. Historical MRR is approximated from current subscription prices.
PostHog
Create a personal API key
In PostHog, under Settings, then Personal API keys, create a key with read access to projects, persons and queries. It starts with phx_. The project key that starts with phc_ cannot read anything and is refused.
Pick your region and project
Choose EU cloud, US cloud or your self-hosted address, then let Canopus list your projects and pick the right one. Project ids are numeric.
Choose the activation event
Either let Canopus detect it automatically or name the event that means a user reached value in your product.
What Canopus reads, through HogQL queries: signups per day, active users, activation, visitors, weekly and monthly retention, your top events, a signup funnel, error-tracking issues, and the signals built on top of them (errors, friction, performance, funnel, behaviour, acquisition).
What the keys can and cannot do
- Both keys are read-only by construction: the permissions you grant are the ceiling.
- Keys are stored encrypted and never shown again after you paste them.
- You can replace or disconnect a key at any time from the same screen.
- If a key loses a permission later, the connector shows the exact missing scope instead of failing silently.