Host the app your team opens, with sign-in and roles built in.
The app in app/ is what your team opens: a CRM, a finance tool, a dashboard, anything with screens. The platform hosts it, signs invited members in and gives it the ontology and the warehouse as the signed-in person.
Hosting with one deploy
app/ is a Next.js app in your repository. segmentstream deploy builds it and puts it online at your-name.segmentstream.app. No hosting account, servers or copied secrets.
Sign-in for invited members
People you invite sign in with an email code, or a link the first time. They need no SegmentStream account, and nobody else gets in.
Roles from the ontology
The ontology decides who may use the app and what they may do. requireUser() in server code, <Can> around controls, and the ontology checks every call again.
Records as the member
segmentstream.ontology reads and changes records as the signed-in member, typed from your ontology. The app holds no database credentials.
Warehouse data and measures
Read-only SQL over the workspace warehouse with named parameters, and measures through the ontology's aggregates.
Agent sign-in pages included
The starter includes the page where members approve their agents and connect their Telegram account to the company agent.
In code
// app/src/segmentstream.tsimport { createSegmentStreamApp } from "@segmentstream-cloud/app";import type ontology from "../../ontology";import link from "../segmentstream.json";export const segmentstream = createSegmentStreamApp<typeof ontology>(link);// app/src/app/leads/page.tsxexport default async function LeadsPage() { const user = await segmentstream.requireUser(); const { items } = await segmentstream.ontology.lead.find({ where: { status: { in: ["new", "contacted"] } }, orderBy: [{ field: "createdAt", direction: "desc" }], limit: 20, }); return <LeadList leads={items} viewer={user.email} />;}Use it, build on it, or have it built
Use it
Every workspace starts with a deployed app you can open and invite people to.
Build it with your agent
Your agent writes the screens in app/ against your ontology; you review the change and deploy.
Have our engineers build it
Our engineers build the first version with you, as code in your repository.
Replaces Retool and admin panels, Separate hosting and auth vendors and Dashboard seats.
Works with
Solutions built with it
Read more
- 8 October 2026Agent sprawl: how to run a company on one AI agent instead of 3,000Companies are building AI agents by the thousand, each with its own instructions, its own keys and its own copy of the rules. Vercel went the other way and moved hundreds of internal agents behind one. Here is how a company runs on a single agent, and what has to sit behind it.
- 8 October 2026MCP gateway vs raw MCP servers: how to run a company through any agentEvery tool your company uses now has an MCP server, and the usual way to give an agent access is to plug them all in. It demos well and breaks on permissions, rules, context and the next agent you try. An MCP gateway over your company's ontology gives every agent one door, with your own actions, roles and history behind it.
- 7 October 2026Read this before you cancel HubSpot or SalesforceCompanies are cancelling CRM contracts and having AI agents write their own. Writing the CRM is now the easy part. What decides whether it survives is the layer underneath it: objects, permissions, actions, history and safe access for agents. That layer is called an ontology.
- 3 October 2026AI agents can build your BI. Here's why they get the numbers wrong.Benchmarks keep finding that agents writing SQL against raw tables give confident wrong answers, while the same agents answering through a semantic layer get nearly everything right. What that means for how you build analytics now.
Start a pilot.
Want apps and sign-in set up for you? Our forward-deployed engineers build it with you in your workspace, as code you own.
- 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.