Today Orkestra goes public.

We’ve been building it for 18 months. The idea came from a very specific frustration: we were using 5 different tools to manage projects at a 12-person agency. Trello for tasks, Notion for wikis, Slack for chat, Google Sheets for reports, Zapier to glue it all together. Every week we lost hours looking for information that “surely someone put somewhere”.

The problem wasn’t productivity. It was visibility. Nobody had a complete picture of what the team was working on, because that picture didn’t exist anywhere — only scattered fragments did.

Orkestra solves that. But it also ships something else — and I think it’s what makes us genuinely different from Asana, Monday or ClickUp.

The differentiator: AI that operates, not that suggests

Most SaaS today say “we have AI”. It usually means a chatbot that answers questions about your data, or autocomplete in text fields. Useful, but it doesn’t change your workflow.

Orkestra did something different. We built an MCP (Model Context Protocol) server with ~160 tools covering 99% of the backend. That means any compatible client — Claude Desktop, OpenClaw, HermesAgent, or whatever comes tomorrow — can operate Orkestra with natural language.

What does “operate” mean? Things like:

“Create a sprint for next month with the 8 onboarding improvement tasks”
“What does Juan have pending this week?”
“Move all my tasks in ‘Code Review’ to ‘QA Ready’”
“Generate the status report for the Marketing area for today’s meeting”

And it works from the free plan. It’s not a $500/month enterprise add-on. From day one, no credit card, you connect Claude Desktop to Orkestra and start talking to your data.

What Orkestra ships with

These are the pillars the platform covers:

Project management: Kanban, list, calendar, Gantt (Pro), sprints, recurring tasks, bulk operations
Collaboration: integrated chat, real-time collaborative wiki (CRDT with Yjs), inline comments, area mentions
AI & automation: MCP with ~160 tools, process engine with approvals, bidirectional webhooks
Organization: areas (departments), hierarchical org chart, custom RBAC, granular visibility
Time: time tracking, workload view, time off, goals/OKRs
Compliance: SSO/SAML/OIDC, SCIM 2.0, full GDPR, US/EU/LATAM data residency
Mobile: Flutter app for iOS/Android/Web with offline-first mode

And some less common features that I think will surprise you: stock and resources (physical inventory + budget with confirmation flows), wiki with real simultaneous editing (Google Docs style), and real offline-first (local SQLite + auto sync).

How the pricing looks

Free ($0): 5 projects, 2 members per project, 250 MB, MCP included
Pro ($3/user/month): unlimited, time tracking, custom fields, Slack/GitHub integrations, 25 GB
Organization ($15/org/month flat): dashboard, audit log, areas, SSO, SCIM, webhooks, stock

The Organization plan is a flat fee per organization, not per user. That’s uncommon — and intentional. We want a 50-person company to pay the same as a 200-person one for enterprise features. The price gradient should come from the number of Pro seats, not a tax on being large.

There’s also Sponsored Pro ($2/user/month when the org pays) which mathematically makes the Organization subscription pay for itself at 8 sponsored users.

What’s next

This is the initial launch, not the end. In the immediate roadmap:

Stripe billing (right now it’s manual for early adopters)
Bidirectional calendar sync with Google/Outlook
Integration marketplace
More languages (French, Portuguese, German)
And a lot more content in this blog — use cases, guides, technical deep-dives

How to get started

Create a free account. No card, no fine print. In 15 minutes you have your first project running. And if you want to connect Claude Desktop from day one, the guide is at /en/ai-agents.

If you have feedback, write to me directly at thomas@orkestra.team. I’m the founder and I read every email. See you inside.

— Thomas