Product
From raw event ingestion to enriched analytics delivery, Heritage Sterling handles the full data pipeline so your engineers focus on building features, not plumbing.
View Pricing
Every step from ingestion to delivery is observable, auditable, and configurable through the API.
Most analytics tools are black boxes: data goes in, a chart comes out, and nobody is quite sure what happened in the middle. Heritage Sterling is designed around full pipeline observability. Every event that enters the system receives a unique trace ID. Every transformation step — normalisation, enrichment, aggregation — is logged with a timestamp and the version of the rule set applied. You can replay any 30-day window of events with a modified rule set and compare outputs side by side before committing to a change in production. This is the kind of data confidence that lets you stand behind your numbers in a board meeting.
The building blocks of a data stack your team will rely on every day.
Accept up to 50,000 events per second per tenant via the ingest endpoint. Batched and streaming modes supported. Built-in schema validation rejects malformed payloads at the edge, keeping your signal quality high without burdening your application layer with defensive code.
Define signal rules in a declarative JSON DSL — no proprietary query language to learn. Rules can reference rolling windows (1 min to 90 days), cross-event joins, and external lookup tables you upload via the config API. Version-controlled and auditable by default.
Route signals to Slack, PagerDuty, email, or any HTTPS endpoint. Alert conditions support hysteresis thresholds to eliminate flapping. Every outbound webhook delivery is logged, retried with exponential backoff, and visible in the delivery log within your dashboard.
Embed interactive charts directly into your own product using our signed-embed tokens. No iframe security headaches, no separate BI tool licence. Charts inherit your product's CSS variables for seamless visual integration, and data permissions are enforced server-side per token.
Every endpoint is documented in OpenAPI 3.1 with real request and response examples, error code tables, and rate limit headers explained in plain language. The docs site is versioned alongside the API — when we ship a breaking change we keep the previous version live for 12 months.
GDPR-compliant by architecture, not by checkbox.
Heritage Sterling runs entirely on infrastructure within the EU. Primary data residency is in Dublin with a warm standby in Frankfurt. Data at rest is encrypted with AES-256; data in transit uses TLS 1.3 exclusively. We hold ISO 27001 certification (audit completed Q1 2024) and publish a full sub-processor list on our trust page, updated within 30 days of any change. For enterprise customers, a Data Processing Agreement is available as a pre-signed PDF — no legal back-and-forth required for procurement teams under time pressure.
“The embedded analytics feature saved us roughly four months of development time. We went live with in-product reporting for our customers in January 2024, and the signed-token permission model meant our security review passed in a single cycle — something that almost never happens.”
Ciarán Daly, CTO, Strata Commerce, Cork
Interactive sandbox, SDK downloads, and OpenAPI specs — all available without creating an account.
Open the Docs