Workflows Planned

Durable workflows.
On the roadmap.

A durable, user-authored workflow engine with scheduled triggers, escalation chains, and threshold alerts is planned. Approval gates with separation of duties are live today — and approval-queue apps are a buildable pattern right now.

Start building See what works today
Promotion Approvals
Approval gates live
Promotion Request prm_4e91a2
capsule field-ops · assignment-mgmt
promotion TEST → PROD
artifact sha256:9b4f…e2c1
schema_drift none · re-verified at apply
requested_by maya.chen
status awaiting 2nd approval
Works Today Live

Approvals are live.
In the release pipeline.

Relpin ships approval gates as part of governed releases — and the platform primitives to build approval-queue apps now. No engine required.

01
Release approval gates

TEST requires 1 approval, PROD requires 2 with separation of duties — the requester cannot self-approve. Enforced by the platform, not by convention.

02
Approvals bound to the artifact

Every approval is bound to the exact artifact hash. Re-planning invalidates prior approvals — nobody approves a moving target.

03
Buildable approval queues

Approval-queue apps are a buildable pattern today: real TypeScript on governed SQL, row-level audit on every decision, and governed Slack notifications.

TEST gate: 1 approval. PROD gate: 2 approvals with separation of duties.
Approvals bound to the exact artifact hash — re-planning invalidates them
Row-level audit captures every approval decision with actor and before/after diffs
Slack notifications run through the governed connector — idempotent and audited
Approval gates live · Row-level audit live · Slack connector live See the approval-queue pattern →
Workflow Engine Planned

Durable execution.
Governed triggers.

The planned workflow engine: user-authored, durable workflows promoted through the same DEV → TEST → PROD lanes — with scheduled triggers, escalation chains, and threshold alerts. None of it ships yet.

01 Planned
Durable workflow engine

User-authored workflows that survive restarts and retries. Planned to run server-side under the same governance as apps: versioned, promoted, audited.

02 Planned
Scheduled triggers

Cron-style schedules that start workflows on a defined cadence. Planned with the same fail-closed defaults as the rest of the platform.

03 Planned
Escalation chains

Pending approvals escalate on a timer — to the next approver, then the team. Planned as a first-class construct, not a buildable workaround.

Planned Preview of a planned capability
Workflow Engine
Workflow Run run_77c3f0
trigger · schedule cron 0 7 * * 1
step · collect_requests done
step · await_approval waiting · 2h
escalate · team-lead after 24h
notify · slack #ops pending
Planned Threshold alerts — notify when a metric crosses a defined limit
Planned Durable state — workflow runs persist across failures and deploys
Planned Audited steps — every state transition recorded with actor and timestamp
Planned Same promotion lanes — workflow definitions promoted DEV → TEST → PROD with approvals
Engine planned · Triggers planned · Alerts planned · Nothing in this section ships yet
Workflows

The engine is planned.
The gates are live.

Start with approval gates and the buildable approval-queue pattern today. The durable workflow engine is planned on the same governed foundation.

Start building Explore the platform

Open beta · Engine planned · Approval gates live today

Approval gates · Separation of duties · Row-level audit · Engine planned