> product

Everything your agents need to know_

Allye is the shared workspace for teams that ship with coding agents: projects, epics, specs and tasks, a knowledge base, team memory, skills, an API catalog and todos. You work in the web app; your agents work over MCP; both open the same records.

Join the waitlist follow a spec ↓

allye.app/hq · DEMOsample

DashboardMy workProjectsKnowledge baseMemoriesSkillsAPI catalogTodosTeam

DEMO / DEMO-11 Billing exports / specExport invoices as CSV_in_progressDEMO-12functionalapp · apiv3[D-01](user) CSV only, UTF-8, one file per request[BR-01]Only invoices the user can already see are exported[AC-01]Given 3 invoices, when I export, then the file has 3 rows[NFR-01]Streams rows instead of loading all in memory[Q-01](resolved) Timezone of dates → the team's timezone

TASKS · 312.1query invoicesdone12.2stream rowsin_review12.3docs pagetodoACTIVITYyou · approved v3Claude Code · spec_get DEMO-12Codex · task_submit DEMO-12.2navigator · staged the runbook

> map

One plan, four levels deep_

A project is your product and its apps are your repositories. Epics group the work, specs say exactly what to build for one app, and thin tasks point at the spec instead of repeating it.

PROJECTAPPS · EPICSSPECSTASKS

PROJECTDEMO · team Billing

APPapi · main

APPweb · main

EPIC DEMO-11Billing exports

SPEC DEMO-12 · apiExport invoices as CSV

SPEC DEMO-13 · webExport button

TASK DEMO-12.1query invoices

TASK DEMO-12.2stream rows

TASK DEMO-12.3docs page

◆ a project belongs to one team◆ apps are repositories with a default branch◆ one spec per app; the epic holds them◆ epic status is computed: planned → in_progress → done◆ blocked is computed from dependencies◆ nothing is deleted: cancel and reopen

> spec lifecycle

A spec has a life, not a status field_

Every spec moves through the same five steps. There are no free status changes and nothing is deleted: a spec is cancelled or reopened, and every version stays readable.

DEMO-12 · Export invoices as CSVsample

draft→in_review→approved→in_progress→done

[D-01](user) CSV only, UTF-8, one file per request[BR-01]Only invoices the user can already see are exported[AC-01]Given 3 invoices, when I export, then the file has 3 rows[NFR-01]Streams rows instead of loading all in memory[Q-01](resolved) Timezone of dates → the team's timezone

v3+4−1diff vs v2approved by you

12.1query invoices[AC-01]done12.2stream rows[NFR-01]done12.3docs page[BR-01]donecoverage3 / 3 AC

Draft

Write the spec in the web app, or run /bridge blueprint and let the crew interview you and write it. Every rule, criterion, decision, quality bar and open question gets an anchor that tasks can point at.

[BR] [AC] [D] [NFR] [Q] · functional · technical · bugfix

In review

Submit it once no question is open. Reviewers read each version and its diff; a spec that needs work goes back to draft.

spec_submit · spec_versions · spec_diff · spec_back_to_draft

Approved

One approval on the current version is enough, and it is a human call: Bridge asks for it and approves only on your explicit yes.

spec_approve · only on your yes

In progress

Thin tasks move from todo to in progress, in review and done. Blocked is computed from dependencies, never set by hand.

task_next · task_start · task_submit · task_complete

Done

Coverage maps the acceptance criteria to the tasks that satisfy them, so nothing is called done without a task behind it.

spec_coverage · spec_validate

> modules

Next to the specs, the context_

The docs, the decisions and the reusable know-how your agents need live in the same workspace, searchable by meaning and reachable over the same MCP server.

Knowledge basetour on the home →Pages and folders in Markdown with Mermaid, in company, project and personal spaces. Pages link to pages, show their backlinks and keep every version you can restore.

Companyyour whole organizationProject · DEMOthe project's teamPersonalprivate to you

historyv1v2v3v4restore v2

backlinks↩ Changelog · DEMO-12↩ Decisions · DEMO-12 [D-01]linked spec · DEMO-12

Team memoryDecisions, patterns and incidents your agents search by meaning, saved without duplicates and linked into a graph.[DEMO-12] CSV only, UTF-80.91Large exports must stream rows0.84Export ignored access groups0.79createdupdatedsupersedednooptour on the home →

SkillsReusable instructions for your agents in personal, team and organization scopes. Import them from GitHub; every edit is a revision you can restore.Review a migrationteamWrite release notesorganizationMy commit stylepersonalsample skills · revisions · restore

API catalogThe APIs your team builds and calls, imported from a URL and searched by meaning, so agents find the real endpoint.POST /invoices/{id}/refundsbillingGET /customers/{id}crmimport from URLnewsample entries · semantic search

TodosPersonal todos with priorities and due dates, overdue and upcoming lists, and a prompt that turns a conversation into a todo.Rotate staging keysurgentReply to the export reviewhighUpdate the runbookmediumsample todos · /todo-add

> sync

Two doors, one record_

You approve a spec in the browser; your agent reads it as approved on its next call. Nothing to export, sync or paste into a prompt.

you · web appsample

DEMO-12 · Export invoices as CSVv3 is in review. One approval on the current version is enough.approve v3request changes

your agent · over MCPsample

>specs · spec_get DEMO-12status: approved · v3>tasks · task_nextDEMO-12.1 · query invoices · todo

> access

Permissions follow your team_

A project belongs to one team, and reading, creating and every transition need that permission in the team. Access groups grant View, Create, Edit, Delete, Import, Export and Manage per area, for people and their agents alike.

◆ tenant chosen at OAuth consent◆ organizations can require MFA◆ personal notes and preferences stay private

access group · Developerssample

ViewCreateEditDeleteImportExportManage

Projects

Knowledge base

Memories

Skills

API catalog