Maestro
The replacement for JIRA and Monday.
Work tracking, asset lifecycle, and channels (email, fax, voice, conferencing) in one queryable graph. Built for humans and agents as equal users, on data you own in your own Google Cloud Storage bucket.
Mastery × Organization × Efficiency
Operating thesis: comprehend, fulfill, perform. Ingest signal from every channel and turn it into typed, queryable work. Humans and agents execute against typed acceptance criteria. Every action is measured end-to-end. We beat the incumbents by being observable — not by feature count.
Why teams leave JIRA and Monday
JIRA and Monday model Work as their only first-class concept. Everything else — services, vendors, comms, knowledge — is bolted on. Maestro collapses the seam.
| Capability | JIRA | Monday | Maestro |
|---|---|---|---|
| Asset registry with lifecycle | None | None | First-class primitive |
| Email · fax · voice · conferencing | Plugin tier | Plugin tier | First-class primitive |
| Agents as first-class users | None | None | First-class identity |
| Typed executable acceptance criteria | None | None | First-class |
| Programmatic by default (UI = API) | Partial | Partial | Total |
| Data sovereignty | Cloud only | Cloud only | Your GCS bucket |
| Migration into the tool | One-way pain | One-way pain | First-class importers |
Four primitives, one graph
Executive rollups, deprecation campaigns, and impact analysis are graph traversals — not separate tools.
Work
Issues, epics, sprints, acceptance criteria. JIRA-class depth with Monday-class views.
Asset
Services, vendors, contracts, hardware, controls. Lifecycle from planning to retired. The system of record JIRA never had.
Channel
Email, fax, voice, conferencing, git, chatops. Typed adapters, bidirectional. Signal in, action out.
Knowledge
Pages, runbooks, decisions, transcripts. Sibling product on the same data plane. Searchable, citable, AI-ready.
Channels — typed integrations, not glue tape
Every channel implements the same typed contract: events flow in and become work; actions flow out and become deliveries. We integrate the providers — we don't rebuild them.
Programmatic by default
Every UI action is also an API call. Agents and integrations are not afterthoughts — they share the same first-class identity model as humans.
Human, scoped
A developer's CLI, personal scripts, browser extension. Scoped to that user's permissions.
Org-scoped service
CI pipelines, third-party integrations, Zapier-style flows. No human owner.
Autonomous identity
An agent with its own scope, work queue, and audit trail. First-class — not a script pretending to be a human.
GET /v1/agents/me/queue?priority=P0,P1 # work the agent may claim POST /v1/work/{id}/claim # atomic claim, optimistic lock POST /v1/work/{id}/ac/{ac_id}/evaluate # report AC result with evidence POST /v1/work/{id}/transition # workflow transition (review-gated) GET /v1/assets/{id}/dependents # blast-radius / impact analysis POST /v1/channels/{type}/dispatch # send email, place call, send fax
Status
Maestro is in active design. We are building publicly — the README is the canonical end-state specification, and each phase ships only after proving its thesis.
Model work, persist to GCS, expose REST + webhooks
- Projects, issues, workflows, MQL (Maestro Query Language)
- Web UI with multi-view boards (Kanban, timeline, Gantt, calendar, workload)
- REST API and outbound webhooks (GraphQL + websockets land in Phase 2 with agents)
- Append-only event log persisted to your Google Cloud Storage bucket
Already have an account? Sign in →