# Mainline

> Project management for software teams that practise trunk-based development and continuous delivery. No backlog, no story points, no per-developer metrics. User story maps connected to real delivery: stories carry acceptance scenarios, move through deploy and release as separate events, and feed lead-time distributions computed from the team's actual history.

Free for one person, forever. Teams: $99/month for up to 8 people, $179/month for up to 16. 14-day team trial, no card.

## Try it

- [Live demo](https://mainline.dev/demo): full working story map, flow metrics, and pairing data. No signup.
- [Flow simulator](https://mainline.dev/flow-simulator): interactive simulation of how WIP limits change lead time.
- [Pricing](https://mainline.dev/pricing)
- [Sign up](https://mainline.dev/signup)

## Docs

- [Story mapping](https://mainline.dev/docs/map)
- [Teamwork and pairing](https://mainline.dev/docs/teamwork)
- [Flow metrics](https://mainline.dev/docs/flow)
- [Inventory: unreleased work as waste](https://mainline.dev/docs/inventory)
- [Trunk-based development](https://mainline.dev/docs/trunk-based-development)
- [Continuous integration](https://mainline.dev/docs/continuous-integration)
- [Continuous delivery](https://mainline.dev/docs/continuous-delivery)
- [CI Monitor for GitHub](https://mainline.dev/docs/ci-monitor)
- [AI coding with Mainline](https://mainline.dev/docs/ai)

## Comparisons

- [Mainline vs Jira](https://mainline.dev/vs/jira)
- [Mainline vs Linear](https://mainline.dev/vs/linear)
- [Mainline vs Asana](https://mainline.dev/vs/asana)
- [Mainline vs Miro](https://mainline.dev/vs/miro)

## For AI agents

- [MCP server](https://mainline.dev/.well-known/mcp.json): read a team's story map and acceptance scenarios directly from a coding agent.
- [MCP setup guide](https://mainline.dev/docs/ai)