Platform deep dive · six surfaces

Six surfaces. One platform.

Praxis is six tightly-integrated systems — runtime, intelligence, 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.

Workflow runtime

44 step types, one runtime

Human tasks, AI decisions, agentic loops, sub-workflows, scripted logic, HTTP calls, dialogs, forms, events, timers, sagas, payments, signing, federated calls — composed in a single state machine.

Idempotent dispatcher safe across worker restarts
Sub-workflow nesting with bounded depth
Time-based pauses with durable wakeups
Event publish/subscribe across workflows
Workflow runtime · part of Praxis
Intelligence layer

Semantic Kernel underneath. You don't have to care.

An IAiBackend abstraction over OpenAI, Gemini, and local models. Governance — cost ceilings, PII redaction, rate limits — runs at the platform layer, not in your handlers.

IAiBackend, IAiAgentOrchestrator, IAiGovernanceService
Vector knowledge plane for context retrieval
Hybrid local + cloud routing
Per-tenant token quotas & usage tracking
Intelligence layer · part of Praxis
Authoring surface

Engine Workspace

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

Visual node graph with type-checked edges
Inline simulation with synthetic inputs
Definition diff and rollback
Role-aware authoring (architect / operator / viewer)
Authoring surface · part of Praxis
Operations surface

Operation Center

Per-tenant subdomain. 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
Custom subdomain per tenant
Mobile-ready, accessible by default
Theme-token customization
Operations surface · part of Praxis
Audit & isolation

Multi-tenancy that's physical, not policy

Per-tenant MongoDB databases. Tenant context is required at every persistence boundary. Cross-tenant data paths simply don't exist in the codebase by design.

Isolated per-tenant database
Audit log on every state-changing call
SOC 2-ready architecture (audit-readiness; not yet certified)
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 in `Workflow.Engine.Handlers/BuiltIn/` and the assembly scanner wires it in. No DI ceremony.

Assembly-scanned DI registration
Public IStepHandler contract
Versioned REST API with OpenAPI spec
Local Docker dev loop
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.

~30 seconds
— 02

Runtime + intelligence wire up

44 step types in one state machine, with the AI governance, routing, and knowledge plane layered underneath.

automatic
— 03

Operation Center generates

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

under 60 seconds
— 04

Operate, audit, extend

Idempotent worker, per-tenant audit trail, and an assembly-scanned handler model your engineers can extend.

forever · live
03 Workflow runtime

44 step types. One state machine.

Human tasks, AI decisions, agentic loops, sub-workflows, scripts, HTTP calls, events, timers, sagas, payments, signing, and federated calls — composed in a single, idempotent dispatcher.

Human task AI decision Agentic loop Sub-workflow Form HTTP call Service call Script Dialog Event publish Event subscribe Delay Trigger Saga Approval chain State machine Payment Sign document Webhook + 25 more
Idempotent dispatcher · durable wakeups · bounded sub-workflow 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.