Keep your track calls. Drop the CDP bill.
Segment, RudderStack and other SDKs can send to a custom host. Point them at your workspace and every event lands in your own warehouse without re-instrumenting or paying per user.
You pay per user to read your own events.
CDPs charge per tracked user, keep the raw data on their side and sell it back to you through a warehouse sync. The more you grow, the more you pay to read your own events.
Replaces Segment, RudderStack Cloud and mParticle.
- The same SDK calls on web, iOS, Android and server, pointed at your own domain
- Raw events in your warehouse in the format your SDK sends
- Identity and audiences built from your own data
- Pay for the compute you use instead of per tracked user
How it works
- 01
Point your SDK home
Change apiHost or dataPlaneUrl. Every existing call keeps working.
- 02
Store raw, model once
Events are stored raw and normalised into one model alongside your other trackers.
- 03
Build identity and audiences
Identity, audiences and traits are computed in your warehouse.
- 04
Activate
Sync to ad platforms and CRM with reverse ETL, without per-user pricing.
Enterprise, with our engineers
Our engineers move your sources and identity graph, replay your history, and rebuild the destinations you depend on. Every existing track call stays as it is.
Self-serve, after launch
Install the event source for your SDK and change its host. Events land in your warehouse; identity and destinations run as jobs you own.
Install from the marketplace
Everything below installs into your workspace as code. Use it as it is, or change anything.
Twilio Segment
Keep Twilio Segment. Change apiHost and own every event.
Event source · Connect or replace
RudderStack
Keep RudderStack. Change the data plane URL and own every event.
Event source · Connect or replace
Amplitude
Keep Amplitude. Change serverUrl and own every event.
Event source · Connect or replace
Mixpanel
Keep Mixpanel. Change api_host and own every event.
Event source · Connect or replace
PostHog
Keep PostHog. Change api_host and own every event.
Event source · Connect or replace
Customer 360
One profile per customer, across every system.
App
Audience & CRM Sync
Write model outputs back to CRM, ad and email tools.
Extension
Questions
Do we have to re-instrument?
No. Your analytics.js, mobile and server calls stay as they are. You change the host they send to.
What happens to destinations?
Destinations become reverse ETL jobs from your warehouse: audiences, conversions and traits sync on a schedule.
Which SDKs are supported?
Segment's analytics.js, RudderStack's SDKs, Jitsu, Snowplow, Amplitude, Mixpanel and PostHog can all send to a custom host.
Rather have it built for you? Start a pilot.
Our engineers move your sources and identity graph, replay your history, and rebuild the destinations you depend on. Every existing track call stays as it is.
- One solution, on your data, in your own workspace
- First version live in two weeks
- Parity proven before anything is switched off
- Fixed scope and price, credited to your contract if you continue
Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.
How the pilot worksYour company’s context, ready for every agent.
$ segmentstream workspace create acme --region eu
▸ workspace ready · data, objects, metrics and access rules in one place
▸ connect Claude, ChatGPT or Cursor with one connector
▸ tell your agent: “add our billing API as a source”
Our engineers build the first version on your data in two weeks, at a fixed price.
Or join the waitlist for self-serve:
Pilots are open now. Self-serve opens to the waitlist this fall.