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.
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.
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 chat in Telegram.”
Works with Claude Code, Cursor, Codex or any agent that can run a CLI. The workspace repository ships with the instructions it needs.
> 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 everywhereWhat 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 21 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
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, Telegram channel
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
Get access first.
Self-serve opens to the waitlist first, in cohorts. Builders on the waitlist go first.
Built for other teams too
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 worksYour company’s software, built by agents, owned by you.
$ 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 agent writes the five folders and runs the checks
$ git add -A && git commit -m "First version"
$ segmentstream deploy
▸ app, ontology 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 join the waitlist for self-serve:
Self-serve opens to the waitlist first.