For developers and AI builders

Five folders, typed blocks, one deploy.

A workspace is a repository with app/, ontology/, pipeline/, connections/ and agent/. Your agent assembles typed blocks instead of inventing infrastructure, the checks catch mistakes, and segmentstream deploy runs all of it with an API, MCP tools and sign-in.

Start a pilot Request access

Sound familiar?

Infrastructure before the product

A database, an auth provider, a hosting account, a queue and a warehouse before the first screen works.

Agents without guard rails

An agent writing an app from scratch invents its own permissions, and nothing checks them.

Everything around the app

The app works, then someone asks for an API, an MCP server and an audit trail.

Inside SegmentStream

Five folders, one repository, one deploy.

The app, the ontology, pipelines, connections and the agent in a repository you clone with git. Each push to main deploys that exact commit.

The console's source code page at the root of our workspace repository: the agent, app, connections, events, ontology and pipeline folders, the README's project map, and the Clone panel with the CLI command and the git remote, noting that every push to main deploys that exact commit — The whole workspace is a git repository you own: the app, the company database, pipelines, connections and the agent. Clone it with git; every push to main deploys that exact commit.

Tell your agent

From a sentence to typed blocks.

“Add a purchase_order entity with an approve action only finance can run.”
“Build a page that lists each account manager's renewals for next month.”
“Load our Google Ads and Meta cost into the warehouse every morning.”
“Post every new lead to our sales channel in Slack.”

Works with Claude Code, Cursor, Codex or any agent that can run a CLI. The workspace repository ships with the instructions it needs.

What happens

terminal

> claude "add purchase orders: over £5,000 they need a finance approver"
▸ ontology/purchase-order.ts        entity, approve action
▸ ontology/roles.ts                 finance may run purchase_order:approve
▸ app/src/app/purchase-orders/page.tsx

$ npm --prefix ontology run check
▸ ontology checks pass

$ segmentstream deploy
▸ app, API and MCP tools updated · same roles everywhere

What you get

Five folders, one deploy

app/, ontology/, pipeline/, connections/ and agent/ in one repository. segmentstream deploy ships them together.

A typed ontology

Entities, properties, relationships, actions and roles in TypeScript with the Ontology SDK. Checks catch mistakes before deploy.

API and MCP for free

Every workspace app's ontology is a REST API, a typed SDK and MCP tools, with the same roles for people, API keys and agents.

Sign-in that's already done

Invited members sign in with an email code. Pages read records as the signed-in person and query the warehouse with bound parameters.

Data when you need it

Pipelines, schedules and a warehouse in Python, and 24 ready-made connections plus any API with a key, OAuth 2.0 or client credentials. Credentials stay with the platform.

A repository agents understand

AGENTS.md and skills ship in the repository, so your agent follows the platform's conventions from the first prompt.

Where teams like yours start

Internal tools and dashboards

Pages and dashboards on your records and data

Sales and CRM

Leads, deals and clients, shaped to how you sell

Projects and tasks

Projects, tasks and cycles with your workflow

Tools you'll use

The same surface for you and your agent.

Ontology SDK

@segmentstream-cloud/ontology

Entities, actions and roles; REST, OpenAPI and MCP from one model

App SDK

@segmentstream-cloud/app

Email-code sign-in, roles, records and warehouse data for Next.js

Pipeline SDK

segmentstream-pipeline (Python)

Connections, ingestion, models, checks and schedules in Python

Agent SDK

@segmentstream/agent

The company agent: ontology tools as the member, in your team’s channels

CLI

segmentstream

Workspaces, deploys, members, jobs and data from the terminal

MCP and API

/mcp and /api/ontology on every app

REST, OpenAPI and MCP on every app, per caller

Start building.

Install the CLI and give your coding agent the task, or request access and we will set up your workspace with you.

curl -fsSL https://segmentstream.com/install.sh | sh

Built for other teams too

For founders and operators

Run the company on software you own

For finance leaders

Contracts, approvals and revenue recognition

For sales and RevOps

A CRM you own and leads graded within hours

For marketing and growth

Audiences, campaigns and attribution

Enterprise pilot

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 works

NameWork email

CompanyWhat should the pilot cover?

Anything we should knowHow did you hear about us?

Goes to our founder’s inbox. No sales queue, no newsletter.

Build 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

Start a pilot

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