Hyphen

Governed operational infrastructure for designing, running, and embedding workflow and agent systems.

Hyphen helps teams turn real operating processes into software that can be audited, adapted, and embedded. It gives you a design layer for shaping process intent, a runtime for executing workflows and bounded agents, and delivery layers for putting those systems inside products and operator-facing environments.

The platform, in three layers

Design

Shape the process before it runs.

Run

Execute human, workflow, and agent systems on one governed runtime.

  • Workflows for deterministic process execution
  • Agents for bounded reasoning, orchestration, and escalation
  • Primitives for approvals, forms, loops, matchers, and custom tables
  • Actions for connecting APIs, databases, and model calls
  • Templates for production patterns you can adapt quickly

Embed

Put Hyphen inside your product or internal operations stack.

  • Gateway for auth, tenancy, key management, and public edge access
  • Hyphen SDK for browser-safe embedded surfaces and session management
  • API Reference for direct platform integration
  • Embedding Hyphen for choosing the right delivery mode

Choose your starting point

I need to understand what Hyphen is

Start with:

I want to build a process on Hyphen

Start with:

I want to embed Hyphen into a product or operator surface

Start with:

How Hyphen works

flowchart LR A["Process intent"] --> B["Design layer<br/>Process Studio or DSL"] B --> C["Governed runtime<br/>workflows, agents, approvals, tables"] C --> D["Delivery layer<br/>gateway, SDK, API"] D --> E["Internal tools, products, operator surfaces"]

The same core runtime supports different operating styles:

  • deterministic workflows with explicit branching
  • bounded ReAct agents for judgment-heavy steps
  • human approvals and forms for controlled pauses
  • embedded surfaces for operations teams and product users

What Hyphen is good at

Hyphen works best where the process matters as much as the output.

Examples:

  • reconciliation and exception handling
  • ticket triage and escalation
  • document review and structured approvals
  • customer onboarding and verification
  • internal operational tooling that needs auditability, human gates, and embedded delivery

Why teams adopt it

  • One governed runtime for workflows, agents, and human decisions
  • Explicit control over tools, branching, and escalation paths
  • Embeddable delivery through the gateway and SDK
  • Durable audit state across runs, approvals, tables, and traces
  • Multiple authoring levels ranging from guided design to direct DSL control

For AI agents

If you're an AI agent or coding assistant, fetch /llms.txt for the complete documentation in one structured text file optimized for LLM consumption.

Built by the Hyphen team. API Reference