---
title: What Laver is
description: What Laver is for, the handful of objects you work with, and the things it deliberately does not do.
section: Start here
order: 1
---

# What Laver is

Laver is a hosted work tracker for small teams. Work lives on kanban boards as
tickets that move left to right through status columns, and the long-lived
writing that surrounds that work lives in a wiki next to it.

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

## The problem it solves

Most teams end up with work in one tool, decisions in another, and no reliable
answer to "what is everyone on right now". Laver keeps the board and the
reference material in the same workspace, under the same membership list, so
that access is decided once and both halves stay in step.

It is a good fit when the answer to "who is doing what" changes daily and needs
to be visible without asking. It is not a substitute for a spreadsheet, a
document editor, or a full project-planning suite.

## The objects you work with

- **Workspace** — the tenant, and the boundary for people, billing, and
  everything inside it. Every user in a workspace holds one role: owner, admin,
  member, or viewer.
- **Board** — one kanban board inside a workspace, with its own columns and its
  own access list.
- **Status column** — a column on a board, such as `Backlog`. Columns belong to
  a single board and set the order of the workflow. One column per board is
  marked as the completion column.
- **Ticket** — a card on a board. It carries a title, a rich-text description,
  assignees, labels, a priority, a due date, a checklist of subtasks, comments,
  attachments, and a history of what changed.
- **Wiki** — a tree of pages belonging to the workspace, with page history and
  attachments. It is not attached to a board, so every member of the workspace
  can read it.
- **Sprint** — an optional setting on a board that turns it into a repeating
  series. At the end of each sprint Laver creates the next board with the same
  columns, carries the unfinished tickets over, and leaves the finished ones
  behind on the old board.

The containment is strict: a workspace holds boards, a board holds columns and
tickets, and nothing is shared between workspaces. See
[Workspaces and boards](/docs/concepts/workspaces-and-boards).

## Who it is for

Teams of roughly three to thirty people who want a shared board without
configuring one. Laver assumes everyone with a login is a colleague: access is
granted per workspace and per board, and there is no anonymous or public view of
anything.

It also suits teams who want their tooling to write to the board. Every action
in the app is an API call, and workspace-scoped API keys let scripts and agents
create and move tickets — see the [API quickstart](/docs/agents-and-api/quickstart).

## What Laver does not do

Said plainly, so you do not go looking:

- **Only a board view.** There is no list, calendar, timeline, or Gantt view. You
  can put two boards side by side with Split view, and that is the extent of it.
- **No custom fields.** A ticket's fields are the ones listed above. You can add
  workspace labels, but you cannot add a field.
- **No estimates or time tracking.** There is nowhere to record points or hours.
- **No reporting or dashboards.** No burndown, velocity, or charts of any kind.
- **No automation rules.** The only automatic behaviour is sprint rollover.
- **No self-serve import.** There is no importer in the app; existing work comes
  in through the API.
- **No public sharing.** Every page requires a login and a membership; there are
  no share links or guest accounts.
- **No free tier for new workspaces.** A new workspace is locked until its owner
  starts a subscription, which begins with a 14-day free trial and requires a
  card up front.

## Where to go next

- [Quickstart](/docs/start-here/quickstart) — a working board in about five
  minutes.
- [Your first workspace](/docs/start-here/first-workspace) — what a new
  workspace comes with.
- [Roles and permissions](/docs/workspaces-and-access/roles-and-permissions) —
  who can do what.