For teams of 3 to 30

Project management
for small teams.

Small teams do not need a project-planning suite. They need one place where the board, the writing around it, and the automation touching it all live under the same membership list. That is what Laver is.

14-day trial · £2.49 per seat per month · viewers are free

Everything a small team actually uses

Kanban boards
Repeating sprints
Team wiki
Agent API

ONE WEEK, ONE TEAM

How a six-person team
runs a release.

The same four features, in the order a real week uses them. Nothing here is a roadmap item — it is what the product does today.

  1. 01

    Monday — the board holds the work

    One board per project, with the status columns you name: Backlog, To do, In progress, Deployed. A ticket carries a rich-text description, assignees, labels, a priority, a due date, a subtask checklist, comments, attachments, and a record of what changed. One column is marked as the completion column, which is how the rest of the product knows what "finished" means.

    Boards and columns
  2. 02

    The sprint ends itself

    Turn the board into a repeating series — 7, 14, or 21 days, or anything from 1 to 90. When a sprint closes, Laver creates the next board with the same columns, groups, and people, carries the unfinished tickets across, and leaves the finished ones behind. The closed board becomes an honest record of what that cycle delivered, so nobody has to write a summary of it.

    How sprints roll over
  3. 03

    The decision goes in the wiki, not a thread

    The wiki is a tree of pages belonging to the workspace, with history, attachments, and full-text search. It is not attached to a board, so every member can read it — the brief, the runbook, and the reason you chose the thing you chose stay in the same workspace as the tickets that came out of them.

    Wiki pages
  4. 04

    Friday — the agent files its own tickets

    Anyone can issue a workspace-scoped API key for themselves. It acts as the person who created it and inherits their board access, so there is no second permission model to maintain. Every write carries the version it expects, which is what makes an agent and a person safe to work on the same board at once.

    curl -X POST https://api.laver.app/boards/$BOARD/tasks \
      -H "Authorization: Bearer $LAVER_API_KEY" \
      -d '{"title": "Flaky checkout test", "status": "To do"}'
    Agent API quickstart

THE REAL THING

This is the actual board.

Laver running Laver: the live product board this app is built on, filtered to marketing work.

The real Laver product board, filtered to marketing work across Backlog, To Do, In progress, and Deployed columns
Captured from the live product · August 2026

HONEST FIT

Where it fits,
and where it does not.

Laver is opinionated and small on purpose: one way to look at a board, a fixed set of fields on a ticket, one place each for people, billing, and documentation.

A good fit when

  • Who is doing what changes daily and needs to be visible without asking.
  • The team is roughly three to thirty people who want a shared board without configuring one.
  • The writing around the work keeps getting lost in chat.
  • You want agents filing and moving tickets on the same board as everyone else.

Not what it is

  • A substitute for a spreadsheet or a document editor.
  • A full project-planning suite with Gantt charts.
  • A public site — there is no anonymous view of anything, and access is granted per workspace and per board.

WHAT IT COSTS

£2.49 per seat, per month.

Or £19.99 per seat billed once a year. Everyone gets the whole product — there are no tiers to compare. Only active owners, admins, and members are billable; viewers are free. Prices are in British pounds and exclude VAT.

Keep reading