The module system

One platform, composed per project.

A small core is always on. Everything else switches on per project, so the app a project shows you is only ever the part of it you use.

Get started See the modules

The set

The core, and the ones you choose.

Every plan includes all 9. What changes from project to project is which ones exist at all.

Always on

Every project has these. They're the spine everything else links to.
Taskstasks · coreLists, custom stages, subtasks, assignees, due dates and automations, with four views over one backlog. Explore Docsdocs · coreA native editor with versioning and org- or project-scope. Link any doc to the work it describes. Explore

Opt-in per project

Switched on in settings. Off means gone, with no empty tab and no placeholder screen.
Bugtrackerbugs · opt-inOwn statuses and views, each linked to the task that fixes it. Clients can file them when you let them. Explore Roadmaproadmap · opt-inMilestones with shipped-versus-planned progress, rolled up from the tasks underneath. Explore Messagesmessages · opt-inClient threads, in the app and over email, on the same record as the work they're about. Explore Billingbilling · opt-inTime tracking is core on every project. Turn on Billing to attach rates and invoice from the same hours. Explore Knowledge baseknowledge · opt-inA structured home for reference docs, guides, and FAQs, in a curated reading order, with an owner and a review date so nothing quietly goes out of date. Explore Meetingsmeetings · opt-inEvery call recorded and transcribed, then searchable by question. Ask what was agreed and get the quote, who said it, and the second of the recording to hear it. Explore GitHubgithub · opt-inLink repositories to a project so pull requests, commits and issues attach themselves to the task or bug their branch names. Agents get the code context too. Explore

Why it holds

A module that's off was never rendered.

Off does not mean hidden behind a setting you might trip over later. There is no tab, no menu item, no half-loaded screen telling you to upgrade. A project you run on tasks and docs alone looks like a tool built for exactly that, and it stays that way however much the rest of the platform grows.

Your agents work the same surface.

Tasks, Docs, Roadmap and Knowledge base are drivable over the MCP server, so an AI-first team can open tasks, write docs, move roadmap items and draft articles without ever opening the app. It is the surface your team uses, not a separate API beside it.

See what agents can drive
agent · zeypm-mcp

▸what is still open on launch, then write it up

get_roadmap { }→ Launch · 5 of 8 shipped, 2 in progress list_tasks { stage: "Blocked" }→ 2 blocked · WEB-131, WEB-140 create_article { title: "Launch status, week 30" }✓ article created · draft

Compose your project in two minutes.

Start with the core. Switch the rest on the moment a project needs them.

Get started Book a walkthrough

No credit card · Core modules on by default