Platform deep dive · six surfaces

Six surfaces. One platform.

Praxis is six tightly-integrated systems — runtime, reasoning, authoring, operations, compliance, and developer ergonomics — designed to be one platform from the start, not stitched together later.

01 The platform

One runtime. Six surfaces that fit together.

Each surface is generated from the same conversation and kept coherent as it changes — not bolted on later.

Business-flow runtime

Forty-four step types, one runtime

Human tasks, reasoned decisions, agentic loops, nested flows, scripted logic, outbound calls, dialogs, forms, events, timers, long transactions, payments, signing, federated calls — composed in a single state machine.

A dispatcher whose effects never double, across worker restarts
Nested flows with a bounded depth
Time-based pauses with durable wake-ups
Events published and subscribed across flows
Business-flow runtime · part of Praxis
Reasoning layer

A model layer you never have to think about

One abstraction over hosted, open and local models. Governance — cost ceilings, sensitive-data redaction, rate limits — runs at the platform layer, not inside your steps.

One backend, one orchestrator, one governance contract
A knowledge plane for context retrieval
Hybrid local and hosted routing
Per-tenant quotas and usage tracking
Reasoning layer · part of Praxis
Authoring surface

The workspace

A canvas where architects design, simulate, and version definitions. Assistance is opt-in, never the only path.

A visual node graph with type-checked edges
Inline simulation with synthetic inputs
Definition comparison and rollback
Role-aware authoring for architects, operators and readers
Authoring surface · part of Praxis
Operations surface

The operation centre

A subdomain per tenant. The end-user app you'd otherwise build by hand — generated from the business flow and the schema, kept in sync with both.

Inbox, dashboards, dynamic forms
A custom subdomain per tenant
Ready for small screens, accessible by default
Look and feel you can set per customer
Operations surface · part of Praxis
Audit & isolation

Multi-tenancy that's physical, not policy

A separate database per tenant. Tenant context is required at every persistence boundary. Cross-tenant data paths simply don't exist in the codebase by design.

An isolated database per tenant
An audit row on every state-changing call
An architecture ready for audit — certification not yet held
Configurable data residency on the custom path
Audit & isolation · part of Praxis
Developer ergonomics

An engineering team can extend it

Drop a new step handler into the handlers project and the scanner wires it in. No registration ceremony.

Registration by assembly scanning
A public step-handler contract
A versioned interface with a published specification
A local development loop in containers
Developer ergonomics · part of Praxis
02 How it composes

Intent in. A whole platform out.

The same description drives every surface — so they never drift apart.

— 01

Describe the operation

From your workspace, in plain language — it compiles into a typed, reviewable business-flow definition. The architect refines with you, never around you.

about thirty seconds
— 02

Runtime and reasoning wire up

Forty-four step types in one state machine, with governance, routing, and the knowledge plane layered underneath.

automatic
— 03

The operation centre generates

An isolated tenant database and a live app — inbox, forms, dashboards — appear at your own subdomain.

under a minute
— 04

Operate, audit, extend

A worker safe to restart, a per-tenant audit trail, and a handler model your engineers can extend.

forever · live
03 Business-flow runtime

Forty-four step types. One state machine.

Human tasks, reasoned decisions, agentic loops, nested flows, scripts, outbound calls, events, timers, long transactions, payments, signing, and federated calls — composed in a single dispatcher whose effects never double.

Human task Reasoned decision Agentic loop Nested flow Form Outbound call Service call Script Dialog Publish an event Subscribe to an event Delay Trigger Long transaction Approval chain State machine Payment Sign a document Inbound hook and twenty-five more
A dispatcher whose effects never double · durable wake-ups · bounded nesting

See it on your own data.

Create your workspace in minutes — account, plan, done. Then describe your first business flow in the workspace and watch Praxis build it. Your database, exportable in one click.