Ligren

0.1.0-alpha.1 · not open for purchase

Write the task once. Agents work it stage by stage.

You describe what should be true when the work is finished. Ligren turns that into an ordered set of stages — plan it, write it, verify it — and runs each one as its own agent with its own record. Nothing starts unless you start it, and no agent can call its own work done.

  1. YouWrite the task
  2. AgentPlan it
  3. AgentWrite it
  4. AgentVerify it
  5. YouMark it done

A diamond is your turn. A circle is an agent’s.

See plans and pricingSee how it works

This is an alpha development preview. The core and the desktop app are at 0.1.0-alpha.1, and nothing on the capability manifest is marked available yet. The hosted team control plane is not running, so you cannot buy a plan today. The prices below are the settled public plan, published early.

The flow canvas in the Ligren desktop app. Task cards are laid out across server, desktop, web and admin swimlanes over waves 1 to 3. Cards are labelled done, running, queued or in review, and name the agent responsible — writer-agent, planner-agent or verifier-agent. Diamond gate nodes connect the rows, one marked opened and one marked not opened.
The flow canvas in the desktop app. Captured from the app’s built-in preview mode — the bar across the top reads “Preview — no Endpoint authority. Everything on screen is sample data.” The interface is Traditional Chinese only at this stage.

How it works

One task, from handing it over to taking it back

Four steps. Two of them are yours, two of them are the agents’.

  1. You

    Write the task

    A title, a description, and the conditions that have to hold before it counts as finished. That is the whole input.

  2. You

    Choose the shape of the work

    Pick a workflow template. Ligren lays it out as an ordered list of stages so you can see exactly what will run before anything runs. This step starts no agents by itself.

  3. Agent

    Each stage runs on its own

    A planning stage plans, a writing stage writes, a verifying stage checks. Each keeps its own run and its own attempt history, so a retry is recorded alongside the earlier work instead of overwriting it.

    The task detail view in the desktop app, on its runs tab. The workflow is in the planned state with zero of four stages complete, and the four stages are listed in order — main, planner, writer, verifier — each marked planned, above buttons to re-prepare, accept routing, and dispatch.
    One task, opened out into its stages. Also from the app’s preview mode; the bar reads “Preview — no Endpoint authority. Everything on screen is sample data.”

  4. You

    No agent gets to call its own work done

    Marking the task finished is your command, and Ligren refuses it until an independent check — a different run from the one that did the writing — has returned a verdict. A worker report, a hook, model text, or an exit code of zero is never enough.

Workflows

A workflow is made of four kinds of stage

These four are the whole vocabulary. You arrange them in the editor to decide how a task gets finished.

  • agent

    Hand it to an agent

    A piece of actual work. Planning, writing and verifying are all this kind — what differs is the role assigned to it.

  • gate

    A checkpoint

    Something that has to hold before the work moves on, such as a particular output having been checked.

  • join

    A meeting point

    Branches that ran separately have to arrive here before any later stage begins.

  • child task

    Split it off

    Work that needs its own owner, its own dependencies, its own working copy, or that carries on over on another machine becomes a task in its own right.

One thing to be straight about: A gate stage today is a structural checkpoint in the template — it does not stop and wait for someone to press approve. The place a person actually decides is the completion step above, and that one is enforced.

The workflow editor in the desktop app. On the left is a stage list named “server to client, two phase”: plan the contract first (agent), schema artifact reviewed (gate), write the server half (agent), write the client half (agent), both halves land (join), review against the contract (agent), drive the flow end to end (agent). On the right are the settings for the selected stage, with kind set to agent and role set to writer.
The workflow editor. From the app’s preview mode; a note at the top of that screen adds that workflows edited here currently exist only on the desktop side.

Pricing

Four plans, and the prices are settled

Priced in US dollars, per seat, per month. The subscription belongs to the organization, not to a person.

  • Free

    Freeno billing cycle

    Evaluate on your own. No payment method needed.

    • Up to 3 people in the organization
    • 1 run at a time, shared by the whole organization
    • Task cloud sync

  • Basic

    $15.00USD / seat / month

    Day-to-day tier for a small team. No cap on members.

    • Unlimited people in the organization
    • 3 runs at a time per seat
    • Task and Memory cloud sync

  • Pro

    $30.00USD / seat / month

    For teams that need more work in flight at once.

    • Everything in Basic
    • 10 runs at a time per seat

  • Max

    $50.00USD / seat / month

    The highest concurrency we sell.

    • Everything in Pro
    • 20 runs at a time per seat

Compare plans

ItemFreeBasicProMax
People in the organization3UnlimitedUnlimitedUnlimited
Runs at a time1 (shared org-wide)3 per seat10 per seat20 per seat
Task cloud syncYesYesYesYes
Memory cloud sync—YesYesYes

Not included on any plan

These are switched off on every tier. We do not advertise them and we do not give a date.

  • Hosted archive backup
  • Enterprise SSO, SCIM, data residency

Billing and subscription terms

  • Prices are in USD. Paid plans bill per seat, per month; Free has no billing cycle.
  • The subscription is held by the organization. Seat count sets that organization’s allowance.
  • You can cancel your own subscription whenever you want, without contacting us and without giving a reason. Cancelling does not cut you off — you keep the plan until the end of the period you have already paid for, and it does not renew after that.
  • You cannot buy a plan today. The hosted team control plane is not running, so the hosted allowance a subscription pays for cannot be delivered yet.
  • No refund policy is published yet. Until one is, this site takes no paid subscriptions.

Where this is

What is actually built, and what is not

This section is here so that nothing further up the page can be read as a promise.

Real today

  • Tasks, workflows, stages, runs and retry history are real tables on disk, not state held in memory.
  • Done is held shut: a task cannot be marked finished until an independent check has returned a verdict.
  • The run that does the checking is always a different run from the one that did the writing.
  • The four prices are seeded in the commercial catalogue, and they are the numbers on this page.

Not real yet

  • Nothing on the desktop app’s capability manifest is marked available.
  • Of the hosted control plane, only the account and permissions foundation slice is implemented; the rest is marked not started.
  • The real agent adapters fail closed — only a development fixture adapter runs. So running one real task end to end is not something you can do today.
  • The desktop app has only been verified on macOS x86_64, and the last complete evidence set was taken against an older core revision. Windows and Linux packaging, signing and auto-update have not been run.
  • The terms of service and privacy policy are placeholders, no refund policy is published, and there is no legal entity information yet.

Questions

What am I actually buying?
Seats in an organization. The seat count sets how much that organization can run at once and which sync features it gets. You cannot buy one today.
Can I use it for work today?
Not really. This is an alpha development preview and the real agent adapters are still closed. You can look at the model and the interface; do not put real work through it.
Do you support Windows or Linux?
Not yet. Only macOS x86_64 has been verified. Packaging and signing have not been run on the other platforms, so we do not claim them.
How do I cancel?
You cancel it yourself, whenever you like — no email to write, no reason to give. You keep using the plan until the end of the period you have paid for, and it does not renew after that.
When can I subscribe?
There is no date. It needs the hosted control plane running, and a refund policy and real terms of service published. We are not going to give you a timeline that no document commits to.