47 native integrations. Median 14 minutes from signup to first alert.
HBHUD ingests revenue, product, and pipeline telemetry through 47 native sources — no ETL brokers, no warehouse copies. Connect Stripe, Snowflake, Segment, HubSpot, and Linear; spot churn leading indicators in a single dashboard before your renewal conversation starts.
- SOC 2 Type II since Q3 2021
- OAuth · Read-only roles
- Median TTV: 14 min
Six surfaces, one Signal Graph.
Pick the job-to-be-done. Each category sits on top of your warehouse — not inside it — so you keep Snowflake, Databricks, or BigQuery as the source of truth while HBHUD reads the change-data-feed.
Every source we read from — listed, not invented.
Hover any tile for the median connect time from the last 1,200 onboarding runs. We name real integrations and the connectors we ship — named reference customers available under NDA, no fabricated logos.
Don't see your source? Bring it to the demo — we ship ~3 new connectors per quarter and prioritize from the live customer waitlist.
Median connect time, by source. Measured, not estimated.
Pulled from the last 1,200 onboarding runs in Q4 2025. These are the medians your team will see on a fresh HBHUD workspace — not best-case numbers from a marketing deck.
How HBHUD connects to your stack — read-only, scoped, audited.
Operators don't want marketing copy on this section. So here it is, plainly: every connector on the Signal Graph requests the minimum scope needed to read the field and nothing else. We don't write to your warehouse. We don't make outbound API calls on behalf of your users. We don't store row-level customer PII outside the field map your team approves during onboarding.
Read-only by construction
Stripe charges, Snowflake tables, Segment events — all read through scoped tokens, key-pair auth, or OAuth grants with explicit, minimum-privilege scopes. No source connector we ship has write access to your production systems.
SOC 2 Type II since 2021
Continuously audited. Our public-facing trust portal is updated within 24 hours of any control change — pen tests, sub-processor list, and access policies are linked from the trust page, not buried in a sales PDF.
PII handling
Field-level hashing on email and account-id by default. Customer identifiers stay inside the region you choose for workspace residency. We never sell, share, or train models on customer telemetry.
GDPR & CCPA
DSAR workflow, deletion SLA of 30 days, sub-processor list published to the trust portal. EU customers can pin workspace residency to Frankfurt or Dublin on request — defaults to US-West for everyone else.
Need the SOC 2 report, sub-processor list, or DPA? Open the trust portal or bring it to the demo.
Frequently asked, before the demo call.
The five questions our solutions engineers hear most often from RevOps and data-platform evaluators. If yours isn't here, bring it to the call.
Do you support a source that's not on the 47?
Yes — through our generic Postgres, S3, and webhook connectors, plus a low-code mapping UI for sources like Zuora or in-house billing. We also ship ~3 new native connectors per quarter, prioritized from the live customer waitlist. Bring yours to the demo and we'll show you the queue.
Does HBHUD write back to my warehouse?
No. We sit on top of Snowflake, Databricks, or BigQuery — we never replace them. Optionally we can publish derived metric tables to a dedicated schema you control, but only if you turn that on explicitly during onboarding. The default is read-only, CDC-based ingestion.
What happens after the 14 minutes?
You'll see your first three dashboards pre-populated from the connected sources: a revenue-cohort tile, a product-funnel tile, and a leading-indicator tile for churn on your highest-ACV segments. From there, you can author your own alerts in the visual rule builder — no SQL required.
How do you handle schema drift in Stripe or Segment?
Each connector ships with a pinned schema version and a soft-fail policy on unknown fields. New event properties appear in the field map within 60 seconds and surface as "unmapped" in the UI — your team either maps them or ignores them; we never silently drop or rename columns.
What OAuth scopes do you actually request?
The exact scopes are listed on each connector's docs page (linked from the gallery). For Stripe we request read_only; for HubSpot we request crm.objects.deals.read and crm.objects.contacts.read; for Salesforce we use a dedicated service user with read-only profile. Full scope inventory is on the trust portal.
Can I see named reference customers?
Yes — under NDA, with a short mutual form. We don't publish customer logos publicly for the same reason we don't publish revenue figures per account: it's an unfair signal to competitors. Reference calls are typically scheduled within 5 business days of demo qualification.
Ready to see the Signal Graph run on your data?
30 minutes, a solutions engineer, and a sandbox connected to a sample of your Stripe + warehouse. No deck.