Skip to content

Changelog

Everything that shipped, newest first.

0.2.0

Private beta

Canopus is open to its first private beta group. A founder connects Stripe, PostHog and Resend with read-only API keys, and the product reads the real numbers before any agent has written a word. From there it builds a product brief and an ideal customer profile you validate, audits your site on three axes, scores nine acquisition channels against that customer, writes email campaigns you approve before anything is sent, keeps a CRM filled from your own product and from Stripe, credits new trials and subscriptions to the campaign that last reached the person, and reports every Monday with two or three proposals. Approval is the only thing in this product with an effect outside it.

  • Connectors for Stripe, PostHog and Resend, by API key, encrypted at rest.
  • A product brief and an ICP proposed from your own data, and validated by you before any strategy is built on them.
  • Three audits, search, AI citability and conversion, each scored out of 100 from weighted rules, each run kept rather than overwritten.
  • Channel scoring across nine channels, with two or three recommended and the rest argued against.
  • Email campaigns written by an agent and sent through your own Resend account, after you have read and approved every message.
  • A CRM filled by a signed event endpoint, a lead endpoint and the Stripe sync.
  • Attribution, last touch over fourteen days, recomputed nightly against the equivalent previous period.
  • The Monday report and the playbook: three findings, three numbers, two proposals, and what each finished campaign taught.

What it does not do yet, plainly. Opens and bounces are not tracked, because no webhook from the sending provider is received. Nothing is published anywhere for you: content is written, you paste it where you publish, and you type back what happened. Audits read the HTML of your pages and never look at them, so there are no screenshots and no visual analysis. Attribution joins on contact identity rather than on UTM parameters, so a stranger arriving from a shared link is invisible to it. And Canopus never logs into your product: everything it knows arrives through an API key you issued or an event your own code sent.

0.1.0

First release

Before Canopus could read anybody's Stripe account, it needed the parts nobody demos. Authentication with passwords, magic links, one-time codes, Google and GitHub, passkeys and TOTP two-factor with backup codes. Organizations with invitations, roles, ownership transfer and a per-organization two-factor requirement, because a studio running several products keeps one organization per product. Billing on Stripe, with entitlements resolved in one place. Transactional email, and a job runner for the work that cannot happen inside a request.

The security controls came with it rather than after it: authorization through one set of guards that every protected page and every mutation calls, an audit log of security-relevant events that the account holder can read, sessions listed with device and IP and revocable one by one or all at once, and a content security policy that carries a nonce on every page rendered per request. There is an admin area behind a role check made on the server every time. All of it exists in English and in French, interface, emails, validation messages and metadata alike.