A language and runtime for AI workflows

Give AI a job.
Keep control.

WhippleScript turns an AI-authored workflow into a durable program: bounded work, explicit access, safe data flow, human gates, and a record you can inspect.

See what you can build Inspect the guarantees

Typed workflowsNo ambient authorityAppend-only historyCompiler-checked policy

Three ways in

Same system. Different reason to care.

WhippleScript sits between intent and execution. Start with the part of that boundary you own.

I want to get things done.

Describe the automation you need. Let AI write the whip. Connect inboxes, files, APIs, models, and people—with the hard engineering already built in.

→ 02

I build systems.

Inspect a typed, deterministic coordination language with durable effects, IFC, explicit capability seams, versioned execution, and machine-checked invariants.

→ 03

I own the data.

Let teams create their own automations inside a signed policy envelope. Decide which data, models, people, and destinations may connect—once.

→

What a whip does

Intent goes in. Governed work comes out.

ASK“Triage support and draft replies.”

→

AUTHORAn agent writes a typed .whip.

→

CHECKTypes, authority, flow, outcomes.

→

RUNDurable effects with a causal record.