Stellary Beta Is Open
The Stellary beta is live with delivery, documents, cockpit, AI agents, MCP, plugins, skills, pipelines, automations, API access, and workspace governance. We are looking for beta testers through Discord.
6 min read
Update on April 10, 2026: Stellary beta is now open. This post keeps the original early-access milestone, but we have updated it so it remains useful in context. If you want the current public milestone, read Stellary Beta Is Open.
Early access was never just about giving people a free preview. It was the phase where we validated whether Stellary could work as a real operating environment for teams.
The answer was yes, but it also helped us understand where the product was already strong and where it still needed tightening before opening beta more broadly.
What Teams Had Access To During Early Access
The early-access product already covered the core Stellary model:
- organizations, workspaces, and projects
- delivery with cards, scopes, and views
- documents and contextual knowledge
- cockpit signals such as missions, priorities, decisions, and proposed actions
- AI setup assistance
- agents and MCP connectivity
- plugins, skills, pipelines, and automations
- API tokens and workspace governance
That mattered because we did not want to test a fake shell. We wanted early teams to use the real product shape.
What Early Access Helped Validate
1. Delivery and documentation need to stay close
One of the clearest patterns was that teams do not just want a board. They want the surrounding context to stay attached to execution.
Specs, decisions, project framing, and runbook-style material become much more useful when they live next to delivery instead of in a disconnected tool.
2. The cockpit is not a cosmetic layer
Early teams consistently validated the need for a layer above task tracking.
Missions, priorities, decisions, and proposed actions help teams see the project as an evolving operating system, not just a queue of tickets.
3. AI only becomes meaningful with real context
The product became much more compelling once agents could work with the actual workspace state instead of generic prompts.
That reinforced our direction around MCP, approvals, and governed execution rather than shallow assistant behavior.
What Changed After Early Access
Early access gave us enough confidence to sharpen the public product narrative.
The product is now much clearer around:
- organization -> workspace -> project structure
- delivery as the execution layer
- documents as living project context
- cockpit as the piloting layer
- MCP and agents as part of the real product surface
- extensions through plugins, skills, pipelines, and automations
In other words, early access was the proving ground. Beta is the point where that model becomes much easier to understand from the outside.
Why We Kept It Free
We wanted usage, not vanity signups.
Keeping early access free reduced friction, but the bigger reason was learning speed. We wanted teams willing to test real workflows, share what broke, and pressure the product in realistic situations.
That feedback loop helped us improve not just UX details but the shape of the product itself.
If You Are Discovering Stellary Now
If you are reading this after early access, the best next step is not this announcement. It is the current product material:
Early access was the start. Beta is where the product becomes ready to be evaluated more seriously. To ask questions live and follow announcements, join the community on Discord.