Workflow engine for developers

Turn complex forms into executable workflows.

Onboarding, supplier checks, claims: many people and AI agents, many steps, weeks apart. Write it once, in React. Clipless runs it: it sends each person their link, chases them when they're late, shows them only what they may see, and records every answer and decision as an event.

Try the playground Getting started
Drops into your stack
  • React
  • Next.js
  • TanStack Start
  • React Router
  • Astro
  • Vite

Any React 19 app. Your components, your models, your backend.

Flagged Within policy Approved Sent back Claim employee Submits the claim and the receipt Policy check AI agent Reads the receipt, checks the policy Review manager Approves it, or sends it back ✦ AI: over the $75 meal cap Payout finance Pays it out
Why not a form builder

A submission isn't a database update. It's an event.

A form builder saves one person's latest answers and hands you a spreadsheet. The approvals, send-backs and checks after that end up in email and Zapier, and what someone told you in March is overwritten in July. Clipless runs the part after submit and keeps all of it.

A form builder
Clipless
After someone submits
A form builderYou get a row in a spreadsheet and an email.
CliplessIt moves on by itself: to the next person, back for changes, or up to finance when two business days pass.
AI
A form builderA summary on top, if anything.
CliplessAn AI step reads the receipt, fills in the fields, flags what's off and picks the route, or suggests answers a person accepts. Fields marked as personal data never reach the model.
The busywork
A form builderZapier, and hoping it runs.
CliplessAn email with a link when it's someone's turn, reminders when they're late, one-time codes, identity checks, PDFs and signed webhooks, declared in the workflow.
The record
A form builderThe latest answers, overwritten.
CliplessEvery answer, hand-off and AI decision as an event: who, when, and on which version of the workflow. Tamper-evident, round by round.
Personal data
A form builderOne table with everyone's answers.
CliplessEncrypted per person. Erase one, and everyone else's record stays intact.
Where it runs
A form builderTheir hosted page or an embed, with their branding.
CliplessA hosted page each person gets a link to, or inside your own app, built with your own components.
Your team
A form builderA shared login to the responses, paid per seat.
CliplessAn inbox each: what waits on you, and who to chase in one click. As many people as you like.
Changing it
A form builderEdited live in a builder, by whoever has the login.
CliplessOne file in your repo, reviewed like code. Sessions already running keep the version they started on.

Where Clipless has four stars, there's more to build.

One person, once? A form builder is the right tool. Clipless is for the forms that pass between people and AI agents.

How it works

Define it once. Everyone gets their own form.

The whole process lives in one React file, so a change is one edit in one place. Each person gets a form with only their stage in it, on a hosted page they're emailed a link to or inside your app. The AI step's prompt stays on the engine, out of the browser.

expense-claim.tsx 
<Workflow id="expense_claim_v1">
  <Stage name="claim" actor="role:employee">
    <Field name="description" required />
    <Field name="amount" type="currency" required>
      <Remarks />
    </Field>
    <Action id="policy" type="ai_prompt" blocking
      prompt="Is {{description}} within policy?"
      schema={VERDICT} />
  </Stage>

  <Stage name="review" actor="role:manager"
    renderIf={{ 'policy.flagged': { eq: true } }}
    transitions={[SEND_BACK]}>
    <Field name="decision" type="select"
      options={DECISIONS} required />
  </Stage>

  <Stage name="payout" actor="role:finance">
    <Field name="payment_ref" required />
  </Stage>
</Workflow>
  1. claim

    Employee

    fills it in

  2. policy

    AI agent

    checks the policy

  3. review

    Manager

    decides

  4. payout

    Finance

    pays it out

AI in the process

The AI takes a step. A person signs it off.

An AI agent is a participant, not a plugin. It reads the document, fills in what it can, flags what's off and suggests the rest for a person to accept. Its answers land on the same record as everyone else's, so six months later you can see what it was shown, what it said and who accepted it. Fields you mark as personal data never reach the model.

expense_claim_v1 · session 7Kq2 · revision 3 
Mar 4 09:12  employee  claim     amount $182, receipt dinner.pdf
Mar 4 09:12  ✦ AI      policy    flagged: over the $75 meal cap
Mar 4 11:40  manager   review    decision send back, remark "split the bill?"
Mar 6 11:40  engine    claim     reminder sent: 2 business days
Mar 6 13:05  employee  claim     round 2: amount $74
Mar 6 13:05  ✦ AI      policy    within policy
Mar 6 13:05  ✦ AI      payout    suggests category meals
Mar 6 16:20  finance   payout    category meals (accepted)
Mar 6 16:21  finance   payout    payment_ref PX-2231

Each line is hash-chained to the one before. Your database keeps the current truth; Clipless keeps how you got there.

Try it

Seven real workflows. Open one.

Each runs in your browser, nothing to install. Click through it, send it back, skip to a deadline, and watch the record fill up beside the form. Or describe your own below.

See it in action AI in the process

An AI that reads the certificate

A supplier uploads a certificate. An AI stage reads it, fills in the standard and the expiry, flags the number when something is off and sends it back or on. At sign-off it suggests an answer; quality take it or don't.

See it in action Filings

Repeating sections

A tax return with as many dependents and businesses as the household has. Every item is validated on its own; the accountant sees them as tables with totals.

See it in action Approvals

Send it back for changes

An expense claim the manager can return. It comes back as round 2, with notes on the amount that only finance can read.

See it in action Applications

Checks that take a while

A loan with four people, an identity check that finishes later, an AI risk read, generated PDFs and an email.

See it in action Recurring checks

The same check, every year

An annual supplier review that starts from last year's answers and shows the reviewer exactly what changed.

See it in action Regulated intake

Regulated intake

A patient intake with a one-time code, contact details kept out of caches, an encrypted history and consent that must be given.

See it in action Onboarding

Conditional stages

B2B onboarding where a risky industry or score routes the application through compliance.

Your process

Who does what, in what order. You get a working workflow to click through as every person in it.

For developers

It's just React.

The workflow is a file next to your screens, built with the components you already have. Deploy it with one command. Your backend starts sessions over HTTP and listens for signed webhooks; the engine does the rest. 

npx clipless login
npx clipless deploy ./expense-claim.tsx
Getting started

Your frontend

  • React
  • Next.js
  • React Router
  • TanStack Start
  • Inertia.js
  • Astro
  • Vite
  • TypeScript

Headless hooks and fields that drop into the app you already have.

Your components

  • Tailwind
  • shadcn/ui
  • Radix
  • MUI
  • Bootstrap
  • Ant Design
  • Your design system

Every field renders whatever you hand it, or start from ours.

Your models

  • Claude
  • OpenAI
  • Gemini
  • Groq
  • OpenRouter
  • Self-hosted

AI steps run on your own key, on any OpenAI-compatible API.

Your backend

  • Node
  • Bun
  • Deno
  • Express
  • NestJS
  • Django
  • FastAPI
  • Flask
  • Laravel
  • Rails
  • Phoenix
  • Spring
  • .NET
  • Go

Signed webhooks and an HTTP API. The engine is hosted; your servers just listen.

Pricing

Pay per session. Every feature on every plan.

A session is one run of a workflow: one claim, one onboarding, one annual check. Test environments are free and unlimited. You bring your own keys for AI, identity checks and file storage, so there is no markup on providers.

Free
$0
to build and launch small
  • Unlimited test sessions
  • 100 live sessions a month
  • Every feature
  • Community support
Get early access
Pro and Business
At launch
for teams running more sessions
  • Priced per live session; test sessions stay free
  • Every feature, on every plan
  • Your own keys for AI, identity checks and storage, with no markup
  • Early-access teams help set the prices
Get early access

Enterprise

A dedicated deployment with its own database and encryption keys, in the region you choose, plus single sign-on and custom terms such as multi-year retention, an SLA or a HIPAA business associate agreement, on request. Talk to us.

Clipless is in early access.

The engine isn't public yet. If you have a form that passes through more than one person or an AI agent, tell us about it, and we'll get you set up.

Get early access Try the playground Getting started