SegmentStream
Objects

The objects your company runs on, in one model every app and agent shares.

Your company's ontology: the customers, deals, products and orders it runs on, with their fields, links and the actions allowed on them. People and agents read and change the same records, and every CRM screen, back-office tool or ERP view is an app on top.

Any object, any field

Describe what your business is made of: customers, companies, deals, products, orders, contracts. Add any field; change it in a pull request.

Linked to each other

A deal belongs to a company, an order to a customer, a ticket to an account. Links are first-class, so apps, metrics and agents follow them.

Edited by people, filled from sources

People edit records in your apps; sources fill them from Stripe, HubSpot or Shopify; Identity merges the duplicates into one record.

Actions with permissions and history

Define what can be done to an object, and who may do it: move a deal, issue a refund, approve an order. Every change is kept in the history.

Ready for every agent

Agents read and change objects through the Agent Gateway, with each person's access, so an agent can work in your CRM, not just report on it.

Metrics on top

Revenue per customer and pipeline per stage count straight from objects, so the metrics and the records never disagree.

In code

objects/sales.py
company = ObjectType(
    name="company",
    fields=(
        Field("name", "string", required=True),
        Field("domain", "string", unique=True),
        Field("segment", "choice", options=("smb", "mid-market", "enterprise")),
    ),
)

deal = ObjectType(
    name="deal",
    fields=(
        Field("title", "string", required=True),
        Field("stage", "choice", options=("new", "pilot", "won", "lost")),
        Field("amount", "number", unit="currency"),
    ),
    links=(Link("company", to="company"),),
    actions=(Action("move_stage", fields=("stage",), roles=("sales",)),),
)
Pipeline SDK reference →

Use it, install it, or build on it

Every block on the platform comes three ways. Most teams use all three.

Use it

Create, edit and search records from the console, an app or an agent.

Install it

Apps from the marketplace, such as the CRM, bring their objects with them.

Build on it

Your agent defines object types, links and actions in the repo; you approve them in a pull request.

Replaces CRM and back-office SaaS, Spreadsheet trackers, Airtable bases and Hand-built admin databases.

Install from the marketplace

Solutions built with it

Enterprise pilot

Start a pilot.

Want objects set up for you? Our forward-deployed engineers build it for 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 works

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

Your company’s context, ready for every agent.

$ segmentstream workspace create acme --region eu

▸ workspace ready · data, objects, metrics and access rules in one place

▸ connect Claude, ChatGPT or Cursor with one connector

▸ tell your agent: “add our billing API as a source”

Start a pilot

Our engineers build the first version on your data in two weeks, at a fixed price.

Or join the waitlist for self-serve:

Pilots are open now. Self-serve opens to the waitlist this fall.