A pulse is a question, a chart and an alert in one object. You describe the behaviour; Northbeam writes the query against your warehouse, builds the cohort and watches it for you.
Type “users who finish onboarding but never invite a teammate”. Northbeam resolves it against your schema, shows you the SQL it wrote, and lets you edit it if you disagree.
See how the builder worksSnowflake, BigQuery, Postgres, Redshift in beta. Northbeam connects with read-only credentials and never stores a copy of your product data.
See all integrationsSlack, Linear, PagerDuty or email. Every alert carries the cohort, the curve and the two most likely causes, so the conversation starts at the second question.
How we handle your dataOnboarding completion dropped 14% in the last 2 hours. Cohort: signups from the pricing page.
No. Connecting a warehouse takes read-only credentials and about two clicks. Every design partner in cohort #1 was live in under a day, and four of them had no data hire at all.
Always. Every pulse shows its compiled SQL, and you can edit it. Nothing runs against your warehouse that you cannot read first.
It stays in your warehouse. Northbeam holds no copy, does not sell it, and does not train models on it. Read-only credentials are the only access we request.
Those tools ask you to ship events into their cloud and maintain a taxonomy. Northbeam reads the warehouse you already trust, so there is no second source of truth to reconcile.
The live demo runs on seeded SaaS data — no signup, no email, no sales call.