The Amplitude alternative: your events, funnels and cohorts in a warehouse you own.
Change serverUrl in the Amplitude SDK and every event lands in your own warehouse, on your own domain. Your history comes over from the Export API, and funnels, retention and cohorts become models you own, beside customers and revenue.
- One setting changes in Amplitude
- Your history comes over
- Collected on your own domain
- First version in two weeks, at a fixed price
SegmentStream collects the events your Amplitude SDK already sends into a warehouse you own, by changing one setting, serverUrl, and brings your history over from Amplitude's Export API. Funnels, retention and cohorts become models and pages you own, joined to the rest of the company. Stay on Amplitude if your team lives in its charts or relies on Experiment and Session Replay; move if you want your product data in your own hands.
Stay on Amplitude if
- Your team explores data in Amplitude's charts every day and wants to keep that.
- You rely on Amplitude Experiment or Session Replay.
Move to SegmentStream if
- Your bill grows with tracked users, and the events are yours anyway.
- You want product events beside customers, revenue and support in one place.
- You want questions answered by an agent, not only in charts.
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: Amplitude Browser SDK 2, Amplitude domain proxy, Amplitude Export API
Change serverUrl. 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. Amplitude stops receiving the events your workspace now collects.
amplitude.init('API_KEY');amplitude.init('API_KEY', { serverUrl: 'https://collect.segmentstream.com/v1/e/WORKSPACE_ID/amplitude/2/httpapi',});Or drop the Amplitude 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 Amplitude loads on your pages. Every Amplitude call in your product becomes a call to the new tracker, in one pull request your team reviews.
- 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 Amplitude, and what you keep in the tools you like.
- Every new event, from the day the setting changes
- Your history, from Amplitude's Export API
- 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
- Amplitude Experiment and feature flags
- Session Replay
- Exploring by clicking in Amplitude's charts: reports become pages and questions for the agent
Amplitude alternative: what it does
Your developers keep every amplitude.track call they wrote. Events land in your own warehouse, beside the company's customers and revenue, and the funnels and cohorts your team relies on become models you own, without a bill that grows with tracked users.
- Change serverUrl in amplitude.init, or the same option in your mobile SDKs 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 funnels, retention and cohorts your team relies on become models you own, compared with Amplitude before anyone switches.
- Your history comes over from Amplitude's Export API.
- 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 Amplitude tracker you already run at your workspace by changing serverUrl. 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.
Funnels, retention and cohorts →
Funnels, retention, cohorts and the dashboards your team opens are rebuilt as models and pages you own, and compared with Amplitude before anyone switches.
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 Amplitude concept, and where it lives in your workspace
For your engineers: every Amplitude concept and where it lives once you have moved.
| In Amplitude | In your workspace | What to know |
|---|---|---|
| Tracking calls in your code | Unchanged: the tracker sends to your workspace | Only serverUrl changes |
| Events and event properties | Every event as the SDK sends it | Names and properties unchanged |
| User properties | Traits on the contact in your company database | Beside the person's deals, orders and tickets |
| Segmentation, funnels and retention charts | SQL models and pages in your app | Compared with Amplitude on your history |
| Cohorts | Segments over your events and records | Refreshed and checked; sent on through destinations |
| Dashboards | Pages in your app with sign-in and roles | Built by your agent from a plain-language brief |
| Data governance and taxonomy | Versioned event schemas in events/ | Checked on every event |
| Raw events | bronze.events_amplitude 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, Amplitude no longer receives its events. Plan the switch for when your reports match.
- An analytics interface to explore in by clicking. Reports become models and pages in your app, built by your agent or our engineers, and the company agent answers questions in plain language.
- Amplitude Experiment, feature flags and Session Replay. Keep them in Amplitude or another tool.
How a move off Amplitude 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 Amplitude endpoint
One template adds the Amplitude 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 Amplitude's Export API, 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 Amplitude, 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 serverUrl
serverUrl changes in amplitude.init, or the same option in your mobile SDKs, 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 Amplitude, end to end, if you want us to.
Our engineers install the Amplitude endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Amplitude, 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 | Amplitude | Workspace | Status |
|---|---|---|---|
| Events | 48,201,377 | 48,201,377 | match |
| Weekly active users | 182,410 | 182,396 | explained |
| Sign-up to activation | 34.2% | 34.2% | match |
| Week 4 retention | 27.8% | 27.8% | match |
- Amplitude Analytics
- Amplitude cohorts
- Dashboards on Amplitude
Your history comes over first and the reports your team relies on are rebuilt and compared with Amplitude. 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 Amplitude endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Amplitude, then change the setting with you.
Self-serve, with your own agent
Tell your agent you run Amplitude. 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 Amplitude alternative?
Yes, for collecting and owning your data. SegmentStream collects the events your Amplitude SDK already sends into a warehouse you own, by changing one setting, serverUrl, and brings your history over from Amplitude's Export API. Funnels, retention and cohorts become models and pages you own, joined to the rest of the company. Stay on Amplitude if your team lives in its charts or relies on Experiment and Session Replay; move if you want your product data in your own hands.
Do we have to re-instrument our product or website?
No. You change serverUrl in amplitude.init, or the same option in your mobile SDKs, 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 Amplitude 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. Every Amplitude call in your product becomes a call to the new tracker, in one pull request your team reviews. You can change the setting first and replace the SDK later, or do both at once.
What happens to Amplitude?
Once the tracker sends to your workspace, Amplitude 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. Amplitude's Export API returns your raw events by time range, and they load into your workspace before the setting changes, so your reports start with every month you have.
What about experiments and session replay?
Amplitude Experiment, feature flags and Session Replay stay with Amplitude or another tool; this replaces the analytics. Keep their SDKs for those features, or switch them off when you move.
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 Amplitude endpoint, serve it from your domain, bring your history over, rebuild the reports your team relies on and compare them with Amplitude, 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