The console: see and manage everything your workspace runs.
The console at cloud.segmentstream.com is where you manage a workspace: the ontology map, records, access, connections, secrets, jobs, lineage, the warehouse, members, the agent and the source code. People use it in the browser; agents use the same operations through the CLI.
The deployed ontology at a glance: entities, relationships, actions, roles and connections, with the checks every deploy passes.
The ontology map
Every entity of the workspace, its relationships, actions and roles, as deployed. Focus on one entity to see its neighbours, and open the inspector for the descriptions agents read.
Records
Browse the records of any entity, newest change first. The console reads; every change goes through an action in the app, the API or an agent.
Access
A table of every read and action against every role, computed from the ontology. It is the same for people, API keys and agents.
Connections and secrets
Authorise the connections declared in code and keep named secrets for pipeline code. Values are write-only.
Jobs, lineage and warehouse
Jobs with their schedules and runs, the lineage of every table, and the warehouse explorer with schemas and previews.
Members
Invite the people who use the app and give them roles. They sign in to the app with an email code and need no SegmentStream account.
Agent and source code
The company agent's model, channel and deployed version, and the source code of the workspace at any commit, with its history.
In code
# Everything in the console has a command, for you or your agent.$ segmentstream ontology member invite ada@example.com --role sales$ segmentstream connection list$ segmentstream job runs revenue_pipeline$ segmentstream lineage asset gold/revenue_summary$ segmentstream warehouse preview gold revenue_summaryUse it, build on it, or have it built
Use it
Every workspace comes with the console. Sign in at cloud.segmentstream.com.
Build it with your agent
Your agent changes the workspace in code and deploys; the console shows the result, version by version.
Have our engineers build it
Our engineers walk your team through the console during a pilot, on your own workspace.
Replaces Admin panels per tool, A separate secrets manager and Orchestrator UIs.
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 console 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.