The modern data stack, in one platform.
Connections, ingestion, models, checks, schedules, lineage, a warehouse, metrics and reverse ETL, declared in Python in one repository and run on managed compute. The same workspace holds your company’s records, apps and agent, so the data you model reaches the software people work in.
Every layer of the stack, in one place
Each layer a data team usually buys as a separate tool, and where it lives in a SegmentStream workspace.
The data stack is one layer of it.
A typical company pays for seven data tools and the engineers who glue them together, and the numbers still drift between them. On SegmentStream the data stack is one layer of the infrastructure your software runs on: pipelines, a warehouse and checks, in the same repository as your apps and your company database.
Before: the patchwork stack
~$210k/yr · 7 contracts · 2 data engineers · T+ 6 months
See how SegmentStream compares →Typical mid-market list prices.
After: one platform
Ontology
Apps and agent
Workflows
Data
Integrations
Usage-based · 1 contract · first version in two weeks
Models and destinations are a few lines of Python.
Ingestions, models, checks and destinations live in pipeline/, with schedules beside the jobs. The platform builds the graph, runs it on managed compute and keeps every run, so your coding agent can write it and you can review it like the rest of your code.
import ibis.expr.types as ir
import segmentstream as s
@s.model(
tier=s.Tier.Gold,
partitioning=s.Partitioning.Daily(column="day", start_date="2026-01-01"),
schema={"day": "date", "channel": "string", "cost": "float64"},
)
def cost_by_channel(ad_spend: ir.Table) -> ir.Table:
return ad_spend.group_by(["day", "channel"]).aggregate(cost=ad_spend.cost.sum())
@s.destination(connection="google_ads")
def google_ads_conversions(
qualified_leads: ir.Table, warehouse: s.WarehouseResource
) -> s.Delivery:
... # send each row through the connection
return s.Delivery(sent=sent, rejected=rejected)Bring your Dagster code
Existing Dagster assets move into your repository as they are and mix with SegmentStream models in the same graph, so a data team moves one pipeline at a time, without a rewrite, and runs it beside the old deployment until the outputs match.
Questions
Can SegmentStream replace Fivetran, dbt and Airflow?
For the data a company’s own software and agents need, yes: connections and ingestion, models with checks, schedules, lineage and a warehouse are one platform, declared in one repository. A large company-wide data platform with hundreds of sources can keep those tools beside it.
Which warehouse does it use?
Every workspace gets its own BigQuery warehouse, created with the workspace in the EU or the US.
Can we keep what we have?
Yes. Existing Dagster assets move into a workspace as they are and mix with SegmentStream models, and an existing BigQuery project can be read through a native connection.
Do we need a data platform team to run it?
No. Pipelines run on managed compute, with no clusters, workers or orchestrator to operate. Your coding agent writes the pipeline code, and our engineers can build the first version with you.
How is it priced?
On usage, with no seats and no charge per connection: compute in SSU, warehouse storage and queries, events and data transfer, on the published price list.
Rather have your data stack moved for you? Start a pilot.
Our forward-deployed engineers build one solution on your data, in your own workspace, as code you own. Tell us what you run today and what you want; your note goes straight to our founder.
- 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://segmentstream.com/install.sh | sh