§ 01 — Deployment ModelDocument · REG-DEP-2026.04

Configurable for operators.
Deployable for regulated IT.

Regisseur is not a hosted chatbot bolted onto operational work. It is a deployable operating layer: local data plane, workspace providers, signed bundles, token-gated external actions, and runtime-produced demo artifacts.

Book a deployment walkthrough Map provider integrations
Built for local-first and on-premise evaluation.
No hosted product data plane required.
RuntimeLocal Docker data plane
ProvidersWorkspace-pluggable
SigningDocuSeal default
PromotionSigned bundles
Demo proofPlaywright artefacts
§ 02 — Local data plane

Run where the regulated data already lives.

Regisseur runtime
Web · worker · queue · ledger

Execution, audit events, work state, provider calls, and cascade resumes stay inside the deployment boundary.

Local services
Postgres · storage · DocuSeal

Core data, signed documents, and default e-signature flows can run without a vendor-hosted data plane.

Systems of record
DMS · policy admin · CRM

Existing systems remain authoritative. Regisseur reads, writes, and records through scoped provider contracts.

§ 03 — Provider layer

One workspace. Multiple outbound systems. One audit trail.

CategoryProvider choicesControl pointOperational use
MailSMTP default · Microsoft Graph · SendGridCredentials tested per workspaceInvitation and notification delivery
MessagingTwilio · REST gatewaySigned outbound callsExternal party nudges and confirmations
SigningDocuSeal default · DocuSign optionToken-gated embedded signingPolicy issue and signed PDF capture
Error reportingSentry · GlitchTip · NoOp in devWorkspace-selected resolverOperational evidence and incident triage

Each provider can be configured and tested per workspace. Credential reads are metadata-only in the UI; writes produce audit ledger entries.

§ 04 — External actions

Signing is a pipeline pause, not a side channel.

01

Pipeline reaches external action

A policy-issue step creates an envelope and marks the node awaiting signature.

02

Provider creates signer URL

DocuSeal runs in-stack by default; DocuSign can be selected when a customer requires it.

03

Portal token gates access

The signer receives a single-purpose link. No platform account or user JWT required.

04

Webhook resumes cascade

Completion stores the signed PDF, updates envelope state, and advances the workflow.

§ 05 — Vertical promotion

Verticals move as signed operational packages.

A line of business is a package of process templates, agents, forms, documents, and tools — promoted without hand-rekeying.

Operators dry-run a bundle, inspect import states, resolve conflicts explicitly, and install new versions without mutating history. In-flight work stays pinned to the versions it started with.

§ Next step

Bring your deployment constraints.
We will map the first workspace.

We will walk through providers, credential testing, signing, bundle promotion, and the UAT path needed before a live carrier demo.

Book the walkthrough Review security controls
Deployment
Local-first · on-prem capable
Providers
Mail · messaging · signing · error reporting
Promotion
Signed bundles · dry-run · audit