Roadmap posts usually list everything a company hopes to build. This one separates what ships today from what does not, because the second list is more useful when you are deciding whether to adopt something.
What ships today
11 Operating Systems, included on every plan: Work, Revenue, People, Hiring, Finance, Communication, Product, Operations, Strategy, BI, and Engagement.
Cortex AI across all of them: chat grounded in your data, 420+ plays, deliverables with citations, and scheduled Autopilot runs on the Business plan.
Governed autonomy: autonomy levels, authority contracts, an approvals queue, a tamper-evident audit chain, and undo at both action and run level.
The public API at brainis.ai/api/v1, with reads across the main resources and governed writes through the action registry.
Integrations: Slack, Google Calendar, and Microsoft 365, plus warehouse connectors.
In progress
More integrations. Teams, Gmail, GitHub, Linear, Jira, Zapier, Make, and n8n are in the catalog as coming soon. We are not going to promise dates.
Outbound webhooks. The API supports polling with updated_since today; event delivery to your endpoint is the natural next step.
Gov OS and Data Marketplace, both in beta and not yet part of the core product.
What we have deliberately not built
This is the part worth reading.
Outbound email sequences. Marketing automation is not in the product, and the features are hidden rather than half-shipped. If you need sequences, we are not your tool for that today.
Accounting. Finance OS handles invoices, expenses, and budgets. It does not do statutory reporting, tax filing, or bank reconciliation. Keep your accounting package.
Payroll execution. We hold pay runs and pay stubs as records. Filing and jurisdiction-specific compliance stay with a specialist provider.
Device and app provisioning. Not what we do.
Deeply configurable workflow engines. Brainis ships opinionated defaults rather than a toolkit for modeling any process. That is a trade, and for some companies it is the wrong one.
Important: We would rather you know the gaps before adopting than discover them in month two. If one of these is central to your operation, the honest answer is to keep a specialist tool alongside, or to not switch.
How we decide
Two questions: does it need the shared data layer to work well, and would building it make the product harder to use for people who do not need it? Features that pass the first and fail the second usually do not get built.
Tell us what is missing
The gaps above are known. If something else is blocking you, that is the useful thing to tell us. Get in touch.
Sharing insights on business operations, AI, and modern team management.
Run your company on Brainis
All 11 Operating Systems on every plan, from $29 a month. No per-seat pricing — you pay for AI capacity, not headcount.
See pricing