DataInbox
    Platform capabilities

    The operating layer between business events and production actions.

    Events arrive from people, applications, databases, devices, partners, and agents. DataInbox resolves the current business context, applies your conditions, makes approved capabilities available, and records every action and state change as evidence.
    • Event and data ingestion
    • Current context and state
    • Policy and approval decisions
    • Actions, new events, and evidence

    What the runtime does

    Five things happen for every operation.

    The same path applies whether the event came from a database, customer, application, device, partner, or agent. Intelligence may change; business control stays with the Inbox.

    1. 01

      Event

      Something relevant happens in a person, system, database, device, document, or agent.

    2. 02

      Context

      The Inbox resolves current data, state, history, domain meaning, and knowledge.

    3. 03

      Decision

      Schemas, authority, rules, limits, and approvals determine what may happen.

    4. 04

      Action

      A person, system, agent, or Companion performs only the permitted operation.

    5. 05

      Evidence

      The decision, state change, action, and outcome return as new traceable events.

    Operational use cases

    One operating context. One concrete outcome.

    See how business events connect to current context, company rules, permitted actions and measurable outcomes.

    vodafone

    Telecom

    Operational case

    Customer interactions validated in real time

    High-volume customer events are checked against current context and operating rules before service or communication continues.

    Interaction receivedContext validatedPermitted response

    Case 1 of 6

    Data and databases

    Data stays in the systems that own it. Context is assembled for the operation.

    DataInbox is not another giant database. An Inbox can receive events, resolve permitted data and references from source systems, and hold the business state and history required for its purpose.

    01

    Systems of record

    CRM, ERP, databases, APIs, streams, files, and devices remain authoritative for the data they own.

    02

    Operational context

    The Inbox combines only the current state, history, domain knowledge, and policy needed for this event.

    03

    State change and evidence

    Permitted actions update the relevant system, while the decision and outcome return as new traceable events.

    What the platform includes

    Six capabilities. One operational model.

    Start with the boundary and event you need. Add connections, rules, agents, or specialist providers without changing who owns the context and authority.

    Define

    Configurable Inboxes

    Define the events, entities, context, actions, ownership, and outcome for one operating boundary.

    Explore
    Connect

    Connectors

    Receive events and exchange data with systems, APIs, streams, files, devices, databases, and MCP capabilities.

    Explore
    Govern

    Rules and policies

    Apply validation, routing, authority, approval, retention, limits, and exceptions as runtime logic.

    Explore
    Operate

    Agent Runtime

    Give any agent bounded context and approved actions while the Inbox remains authoritative.

    Explore
    Extend

    Companions

    Make approved AI, payment, identity, and specialist providers available as governed capabilities.

    Explore
    Scale

    Federated architecture

    Let independent Inboxes exchange only the events, context, and references their policies permit.

    Explore

    Control that can evolve

    Change behaviour with evidence before impact.

    Configuration defines events, context, schemas, rules, actions, and approvals. Validate it, compare the change, dry-run it against representative events, and apply it predictably.

    01

    Validate

    02

    Compare

    03

    Dry-run

    04

    Apply

    Start with the operation

    Bring one event that should produce a better outcome.

    We map the source data, current context, rules, people, systems, agents, permitted actions, and evidence. You see the operating model before committing to a large programme.