Product overview
Understand the Account boundary, four workspaces, settings, and the normal operating loop.
Combined is an ingestion-first control and data plane. It acquires approved company context, preserves provenance and freshness, and exposes only granted data to external agents and humans.
Account boundary
An Account owns Sources, memberships, grants, principals, retention, billing, usage, Activity, and query budgets. The Account switcher shows only Accounts visible to the signed-in principal. Every public API operation either resolves the visible Account list or requires an explicit Account UUID.
Workspaces
| Workspace | Primary job |
|---|---|
| Sources | Connect, authorize, configure, run, pause, review, and delete context Sources |
| Query | Discover logical relations and run bounded read-only SQL |
| Access | Create agents, inspect principals, grant Sources or datasets, apply limits, and revoke |
| Activity | Investigate content-free operational events, attempts, deliveries, and receipts |
The Account menu also opens Settings, with General, Members, Billing, Usage, and Privacy & retention sections.
Normal operating loop
- An Owner creates the Account and establishes billing and membership.
- A Deployer connects a Source, identifies the correct authorizer, selects datasets and fields, and chooses a schedule.
- Runs produce deterministic Deliveries; a lake commit advances freshness and provider state.
- Access grants bind a human or agent to exact Sources or datasets with row, byte, rate, and expiry limits.
- Query, REST, SDK, and MCP calls resolve the current grants before execution and again before a result returns.
- Activity preserves content-free evidence for authorization, ingestion, querying, support, and deletion.
What the product does not do
Combined does not host the consuming agent, execute autonomous business actions, provide a general
write API, centralize raw Desktop video/audio/screenshots, expose provider credentials, or offer a
semantic/vector search layer. search_context is bounded literal search compiled to the same SQL
path.
Private ingest/query services, internal callbacks, cron routes, webhooks, and recovery commands are implementation boundaries, not customer-callable interfaces. Use the public API for supported automation.