xProduct platform · v3.2

The operational control plane for modular systems.

One unified runtime that orchestrates applications, data, automation and integrations - engineered for teams running production-grade business operations.

Request Architecture Demo View Architecture
Uptime SLA
99.98%
Modules
40+
Events / day
12.4M
Scroll

Architecture

Four planes. One coherent runtime.

Every xProduct deployment is a single runtime composed of four planes - presentation, control, data, and edge - sharing one identity, policy, and audit fabric.

Presentation plane

Interface & dashboards

Operator consoles, embedded reports, and role-scoped dashboards rendered from a shared design system.

  • Dashboards
  • Forms
  • Embeds
  • Reports
Control plane

Workflow & policy engine

Schedules, approvals, conditional logic, and event routing - declared once, executed across every module.

  • Workflows
  • Policies
  • Approvals
  • Events
Data plane

Unified operational store

Normalized entities, audit trail, and queryable history shared across every connected application.

  • Entities
  • Audit log
  • History
  • Search
Edge plane

Integrations & webhooks

Outbound webhooks, inbound connectors, and signed API surfaces for every external system.

  • API
  • Webhooks
  • Connectors
  • Queues

Five layers stacked into one runtime.

A request enters at the experience layer, passes through orchestration and services, then resolves against identity, data, and infrastructure.

  1. L4
    Experience

    Operator consoles & dashboards

    Role-scoped UI, embedded reports, and approvals - the surface every user touches.

  2. L3
    Orchestration

    xProgramming workflows

    Schedules, routing rules, and policy decisions that turn intent into coordinated action.

  3. L2
    Services

    Modular business apps

    Billing, CRM, inventory, HR, reporting - composable services sharing one contract.

  4. L1
    Data & identity

    Unified entities and audit

    Normalized records, ACL, event store, and a single audit log for every change.

  5. L0
    Infrastructure

    Compute, storage, observability

    Queues, telemetry, and the runtime substrate that keeps every layer above it honest.

Workflow engine

A declarative workflow engine for real operations.

Compose triggers, conditions, branches, and actions across every module. Workflows version, replay, and observe like code - without redeploying the system.

  • Event-driven triggers across every module
  • Conditional branches, retries, and SLAs
  • Versioned workflows with safe rollback
  • Audit trail on every step execution

Data fabric

Every module reads from the same source of truth.

A unified entity graph keeps writes, audit trail, and downstream consumers in lockstep - across operational databases, blob storage, webhooks, and external APIs.

Sources

ingesting
  • Operational DBwrites · cdc
  • Object storageblobs · sync
  • Webhooksevents · triggers
  • External APIsstream · poll

Consumers

consuming
  • Reports & exportsscheduled
  • Live dashboardsrealtime
  • Alerts & approvalspolicy
  • Downstream workflowsautomation

Module lifecycle

Modules install like services, not plugins.

Modules install side-by-side with what's already running. No rebuilds, no migrations, no downtime windows.

  1. 01

    Install

    Pull a module from the Marketplace into your workspace.

    marketplace.module
  2. 02

    Bind

    Module attaches to the shared entity graph and event bus.

    runtime.bind
  3. 03

    Configure

    Map roles, fields, and routing rules to your tenant.

    tenant.config
  4. 04

    Operate

    Run side-by-side with existing modules - no rebuild.

    live.traffic

Capabilities

Production-grade automation primitives.

  • Event triggers

    Webhook, schedule, entity change, or manual call.

  • Conditional routing

    Branches based on role, tier, region, or custom expressions.

  • Policy gates

    Built-in approvals, RBAC checks, and rate limits per step.

  • Retries & DLQ

    Exponential backoff, replay queue, and dead-letter inspection.

  • Long-running tasks

    Durable waits, timers, and human-in-the-loop steps.

  • Observability

    Trace every execution with metrics, logs, and step diffs.

Production deployments

What teams actually run on xProduct.

Each region runs the same runtime - different modules, same shared identity, audit log, and policy fabric.

prod-eu-1 Healthcare
Load68%

Multi-clinic patient operations

Patient records, scheduling, billing claims, and inventory unified across 12 clinics with role-scoped dashboards.

  • appointments.svcok
  • claims.queueok
  • inventory.syncsyncing
Modules9
Workflows47
Events / day184k
prod-us-2 Finance ops
Load41%

Accounting close automation

Invoice ingestion, approval chains, ledger sync, and exception routing executed end-to-end with full audit trail.

  • ledger.syncok
  • approvals.svcok
  • exception.dlqok
Close time−68%
Exceptions1.2%
Approvers32
prod-apac-1 Operations
Load82%

Internal ops control center

Vendors, contracts, internal requests, and SLAs orchestrated through a single operator console with policy gates.

  • sla.engineok
  • vendor.apidegraded
  • approvals.svcok
Avg. SLA4.2h
Auto-resolved61%
Connected apps18

Production posture

Built for systems that have to stay up.

  • Sub-100ms p95

    Event execution stays predictable under production load.

  • Audit-ready by default

    Immutable log of every state change, decision, and integration.

  • Tenant-grade isolation

    Per-tenant identity, data, and policy boundaries baked in.

  • Region-aware deploys

    Pin workloads and storage to specific regions for compliance.

Scroll to Top