The Segment alternative you own: same tracking calls, your own warehouse.
Change apiHost in analytics.js, or the host in your mobile and server libraries, and every track, page and identify call lands in your own warehouse, on your own domain. Destinations become code you own, and nobody pays per tracked user.
- One setting changes in Segment
- Your history comes over
- Collected on your own domain
- First version in two weeks, at a fixed price
SegmentStream collects the events your Segment libraries already send into a warehouse you own, by changing one setting, apiHost. Your track, page and identify calls stay as they are. Destinations become code in your repository and audiences become checked segments. Stay on Segment if you rely on dozens of device-mode destinations; move if you want your events, your identity and your destinations in your own hands.
Stay on Segment if
- You rely on many device-mode destinations that load in the browser.
- Your marketers build audiences by clicking and want to keep doing so.
Move to SegmentStream if
- You want every event in your own warehouse as it arrives, not after a sync.
- Your bill grows with tracked users, and the data is yours anyway.
- You want destinations and audiences in code your team reviews.
We move you, if you want
Our engineers install the endpoint, serve it from your domain, bring your history over and rebuild your reports, then change the setting with you when the numbers match. It starts with a fixed-scope pilot.
Request a pilot →Last reviewed October 2026 · Sources: Segment custom proxy, Segment data export options
Change apiHost. Nothing else.
Your tracking calls stay as they are. Only the address changes: your workspace's endpoint on collect.segmentstream.com, or the same path served from your own domain. Segment stops receiving the events your workspace now collects.
analytics.load('WRITE_KEY');analytics.load('WRITE_KEY', { integrations: { 'Segment.io': { apiHost: 'collect.segmentstream.com/v1/e/WORKSPACE_ID/segment' }, },});Or drop the Segment SDK for a tracker of your own.
Your agent declares a stream in your repository and writes a small tracker for your site, sending the events your reports need. Nothing from Segment loads on your pages. Your track, page and identify calls become calls to the new tracker, and destinations stay code in your repository.
- Page views from the browser; requests and form submissions from your own server, with the IP address and user agent.
- A first-party cookie set by your own server on your domain, so it keeps its full lifetime.
- Bots and AI agents classified, sessions built and leads attributed, as models in your repository.
- This website is measured this way, with a tracker our own agent wrote.
from segmentstream.events import Stream, auth, protocolstreams = ( Stream( key="web", auth=(auth.WriteKey(), auth.Origin(("https://www.yourcompany.com",))), protocol=protocol.Json(batch=True), ),)const endpoint = 'https://collect.segmentstream.com/v1/e/WORKSPACE_ID/web';export function track(type: string, payload: Record<string, unknown> = {}) { navigator.sendBeacon(endpoint, JSON.stringify({ batch: [{ event_id: crypto.randomUUID(), event_time: new Date().toISOString(), event_type: type, schema_version: 1, payload: { url: location.href, referrer: document.referrer, ...payload }, }], }));}track('page_view');An event stream as its events/ folder declares it: the origins it accepts, batching, and the endpoint your tracker sends to.
Swipe the screen sideways to see all of it.
What comes over, and what stays
What you bring from Segment, and what you keep in the tools you like.
- Every new event, from the day the setting changes
- Your history, from the copies Segment already writes to your warehouse or cloud storage
- Anonymous and user ids, so each person's history joins up
- Event names and properties as your developers sent them
- The reports your team relies on, rebuilt and compared
- Device-mode destinations: load those tags directly or through your tag manager
- Segment's audience builder: audiences become segments your agent writes
Segment alternative: what it does
Your developers keep every analytics.track call they wrote. Events land in your own warehouse, on your own domain, and the tools that need them get them through destinations you own, without paying per tracked user.
- Change apiHost in analytics.load, or the host setting of your mobile and server libraries and events start arriving in your own warehouse. No new tags, no new tracking plan.
- Raw events keep the shape the tracker sends, and one normalised events table brings every tracker into the same model.
- Collection runs on your own domain, so more of your traffic is measured.
- The destinations you relied on are rebuilt in code, and every delivery is counted.
- Your history comes over from the copies Segment already writes to your warehouse or cloud storage.
- Sessions, channels and attribution join your events to ad cost and the CRM.
- The company agent answers questions from your events, within the roles of whoever asks.
What it covers
One setting, nothing re-instrumented
Point the Segment tracker you already run at your workspace by changing apiHost. The tracking calls your developers wrote keep working.
Every event in your own warehouse →
Every event lands in your own warehouse, in the region you choose, in the shape the tracker sends it, beside one normalised events table for every tracker you run.
Collected on your own domain
Collection is served from a path on your own domain, so ad blockers and browser tracking prevention cut less of it, and your first-party cookies keep their full lifetime.
Destinations in code →
The tools you sent events to get them from your workspace: conversions to ad platforms, traits to your CRM, rows to a sheet. Each destination is code in your repository, with every delivery counted.
Sessions, channels and attribution →
Sessions, channels, conversions and attribution built on your events and joined to ad cost and the CRM, which no single analytics tool sees.
Ask the company agent →
Your team asks about traffic, funnels and customers in plain language. The company agent answers from your warehouse, with the permissions of whoever asks.
Every Segment concept, and where it lives in your workspace
For your engineers: every Segment concept and where it lives once you have moved.
| In Segment | In your workspace | What to know |
|---|---|---|
| Tracking calls in your code | Unchanged: the tracker sends to your workspace | Only apiHost changes |
| Sources (web, mobile, server) | One Segment endpoint in events/ | analytics.js, iOS, Android and server libraries use the same host setting |
| Tracking plan and Protocols | Versioned event schemas in events/ | Checked on every event; invalid events are kept and flagged |
| Cloud-mode destinations | Destinations in your pipelines or actions | Each send counted, with the provider's credentials held by the platform |
| Warehouse destinations | Your warehouse, from the start | No sync schedule; events land as they arrive |
| Profiles and identity | Contacts in your company database, joined by user and anonymous ids | On the same records as sales and support |
| Engage audiences | Segments over your events and records | Refreshed and checked; sent on through destinations |
| Functions | Pipeline models and workflows in your repository | Reviewed as pull requests |
| Raw events | bronze.events_segment in your own warehouse | In the shape the tracker sends, in your region |
| One model for every tracker | silver/events | Event names, ids, pages and revenue in one schema |
| Access to the data | Roles for people, apps and agents | The same roles everywhere, with no extra seats |
What you keep elsewhere, and what SegmentStream does not do
- Once the tracker points to your workspace, Segment no longer receives its events. Plan the switch for when your reports match.
- Device-mode destinations that load third-party scripts through Segment. Load those tags directly or through your tag manager.
- A point-and-click audience builder. Audiences are segments your agent writes and your team reviews.
How a move off Segment works
Each step is a pull request in your repository or a check in the console. Our engineers can do all of it with you.
- 01
Add the Segment endpoint
One template adds the Segment endpoint, the model that normalises its events and a guide to your repository. Your agent installs it and you review the pull request.
- 02
Bring your history
Your history comes over from the copies Segment already writes to your warehouse or cloud storage, so your reports start with every month you already have.
- 03
Rebuild the reports and compare
The reports your team relies on are rebuilt on your history and compared with Segment, month by month, until every number matches or the difference is explained.
- 04
Serve collection from your domain
A path on your own domain is routed to the collector through your CDN or web server, so cookies keep their full lifetime and fewer events are blocked.
- 05
Change apiHost
apiHost changes in analytics.load, or the host setting of your mobile and server libraries, a test event is sent with the real tracker, and real traffic is checked arriving in your warehouse.
- 06
Switch your team
Your team opens the rebuilt reports and asks the company agent instead. Nothing is switched off before the numbers match.
We move your analytics off Segment, end to end, if you want us to.
Our engineers install the Segment endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Segment, then change the setting with you. Or do it with your own agent and our help on call. It starts with a fixed-scope pilot.
Nothing switches until the numbers match.
Both systems run side by side. Every number your teams rely on is compared, and every difference is explained before anything is turned off.
| Metric · Sept | Segment | Workspace | Status |
|---|---|---|---|
| Events | 61,204,377 | 61,212,904 | explained |
| Identified users | 184,903 | 184,903 | match |
| Order Completed | 9,412 | 9,412 | match |
| Revenue | £1,284,560 | £1,284,560 | match |
- Twilio Segment Connections
- Segment Protocols
- Segment Unify and Engage audiences
Your history comes over first and the reports your team relies on are rebuilt and compared with Segment. Then one setting changes, collection moves to your own domain, and every new event lands in your warehouse. We do the whole move for you if you want: see the offer below.
Enterprise, with our engineers
Our engineers install the Segment endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Segment, then change the setting with you.
Self-serve, with your own agent
Tell your agent you run Segment. It installs the endpoint and its model, prepares the first-party path for your domain and shows you the one setting to change, and segmentstream deploy puts it live.
curl -fsSL https://cloud.segmentstream.com/install.sh | shRelated solutions
Questions
Is SegmentStream Cloud a Segment alternative?
Yes, for collecting and owning your data. SegmentStream collects the events your Segment libraries already send into a warehouse you own, by changing one setting, apiHost. Your track, page and identify calls stay as they are. Destinations become code in your repository and audiences become checked segments. Stay on Segment if you rely on dozens of device-mode destinations; move if you want your events, your identity and your destinations in your own hands.
Do we have to re-instrument our product or website?
No. You change apiHost in analytics.load, or the host setting of your mobile and server libraries, and the tracking calls already in your website, app and servers keep working. No new tags and no new tracking plan. Re-instrumenting only comes in if you choose a tracker of your own instead.
Can we drop the Segment SDK altogether?
Yes. Your agent declares a stream in your repository and writes a tracker of your own: page views from the browser, requests and form submissions from your own server, and a first-party cookie on your domain. Your track, page and identify calls become calls to the new tracker, and destinations stay code in your repository. You can change the setting first and replace the SDK later, or do both at once.
What happens to Segment?
Once the tracker sends to your workspace, Segment stops receiving those events. That is the move, so the reports your team uses are rebuilt and compared on your history first, and the setting changes when they match.
Can we keep our history?
Yes, from wherever Segment already keeps a copy: a warehouse or cloud storage destination is read into your workspace once. From the day the setting changes, every event is collected directly.
Does it work for our mobile apps and servers too?
Yes. Segment's iOS, Android, React Native and server libraries send to a host you can set, so the same endpoint collects them. The guide shows the setting for each library.
What happens to our destinations?
Cloud-mode destinations are rebuilt as destinations in your repository, sending from your warehouse or from an action. Tags that ran in the browser through device mode are loaded directly or through your tag manager.
Will SegmentStream do the migration for us?
Yes. Our forward-deployed engineers do the whole move if you want it: the endpoint, the first-party path, the history, the reports and the comparison, starting with a fixed-scope pilot. Request it on this page and your note goes to our founder, not a sales queue.
What does it cost to run?
Usage: events received, warehouse storage and queries, and the compute your pipelines and apps use. No seats and no charge per tracked user.
Who owns the data?
You do. The events sit in your workspace's warehouse in the region you choose, and the code lives in a private git repository you can clone, keep on GitHub and take with you. SegmentStream runs it.
Rather have it moved for you? Request a pilot.
Our engineers install the Segment endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Segment, then change the setting with you.
- 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 worksBuild your company’s own software. Let agents run it.
$ segmentstream workspace create acme --region eu --subdomain acme
▸ Created workspace acme · database, warehouse and a private git repository
$ segmentstream workspace WORKSPACE-ID clone acme && cd acme
▸ your coding agent builds what your team asked for and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, company agent, API and MCP tools live for your invited members
Our engineers build the first version on your data in two weeks, at a fixed price.
Or build it yourself with your coding agent:
curl -fsSL https://cloud.segmentstream.com/install.sh | sh