UNOBITS
Changelog

What is built, what is coming, and what is not done.

Roadmaps are usually written to reassure people. This one is meant to be checkable — if something moves or gets dropped, it will say so here rather than quietly disappear.

01The record

Newest first.

After launch

PlannedLater this year

Ordered by what early workspaces actually ask for rather than what demos well. This list will change, and that is the point of publishing it.

  • Social channels joining the unified inbox alongside email and chat.
  • Live collaborative boards for work that happens with people outside your team.
  • More reporting starting points, so a useful dashboard is not a project.
  • Deeper Digital Twin coverage as it learns more industries.

1.0

At launchLaunch day

The whole operating system, open on every plan. Not a starter tier that grows into the real product — the real product, priced by how big you are.

  • All 26 rooms: inbox, chat, email, projects, CRM, files, office, finance, inventory, reports and the rest.
  • Donna across the system, in assistance, planning, code, tool and research modes.
  • The Digital Twin, which studies the businesses you actually lose work to.
  • Polymorphic setup: the workspace reshapes its structure and vocabulary around your industry.
  • Portals for clients and contractors, who never count as seats.
  • Over a hundred integrations, plus automations written in plain language.
02How we ship

Three habits that decide what lands.

Small pieces, often

Large releases are mostly a way of hiding risk until it is expensive. We would rather ship narrow changes continuously and be able to undo one of them.

Speed counts as a feature

A workspace you live in all day cannot make you wait. Performance regressions get treated as bugs rather than trade-offs, which is why it is built on vanilla foundations.

The roadmap comes from use

The most useful requests describe a workflow that is currently painful, not a feature. Those are the ones that move up the list.

Tell us the thing that is currently painful.

Describe the workflow rather than the feature you think would fix it — the fix is often somewhere neither of us expected.