Clipless Docs

Clipless ​

Clipless is a hosted engine for multi-step, multi-person workflows: onboarding with a compliance review, a loan that goes from applicant to underwriter to officer, an expense claim that a manager can send back, a supplier check that runs every year.

You describe the workflow once, in React:

tsx
<Workflow id="expense_claim_v1">
  <Stage name="claim" actor="role:employee">
    <Field name="amount" type="number" required />
  </Stage>
  <Stage name="review" actor="role:manager">
    <Field name="decision" type="select" options={[{ value: 'Approve' }, { value: 'Reject' }]} required />
  </Stage>
</Workflow>

The engine does the parts that are hard to get right:

  • Who may do what. Each stage belongs to a role. The engine refuses writes from anyone else, and each role only ever receives the answers it is allowed to read.
  • Where the workflow goes next. Conditional stages, branches, and loop-backs ("send it back for changes"), decided on the server.
  • What happened. Every change is an event in an append-only, hash-chained ledger. State is rebuilt from it, so you get drafts, history and an audit trail without writing any of it.
  • The calls around it. Webhooks, email, one-time codes, AI prompts, identity checks and PDFs, declared where they happen and run by the engine, including ones that finish minutes later.
  • Sensitive data. vault fields are encrypted at rest with a key per session, and one session's data can be erased without touching anything else.

Your app keeps its own UI: Clipless is headless, with default field components you can replace.

What it is for ​

A process with several parties that runs over days, where you need to prove who did what:

  • Onboarding — customers, vendors, employees, with compliance stages and identity checks.
  • Regulated intake — patients, consent, permits: personal data kept out of caches or encrypted, one-time codes, consent that must be given.
  • Applications — loans, grants, insurance: several reviewers, slow checks, AI reads, generated documents.
  • Approvals — expenses, refunds, access requests, sent back and resubmitted as often as needed.
  • Recurring checks — an annual supplier review or KYC refresh, each run starting from the last.

Login and payment are not workflows: sign people in with your auth provider, and take a payment as an action that waits for the provider, the way an identity check does.

Where to go next ​

Pre-release

Clipless is not public yet: the packages are not on npm and the hosted engine has no public URL. These docs describe the product as it runs today in the repository.