Why we put docs, tables, chat, and projects on one substrate

Every team ships work the same way: a brief in one tool, the data in another, the conversation in a third, the plan in a fourth. Each has its own login, its own search box, its own idea of who can see what. The work is connected in your head — and nowhere else.

We call this the tab-switching tax. It’s not the seconds lost alt-tabbing. It’s the context that leaks through every gap: the decision buried in a thread nobody links, the table that drifts out of sync with the doc that describes it, the permission you granted in one app and forgot in the other.

One graph, not five silos

Zanbase puts docs, real databases, chat, and project tracking on one substrate. A doc, a table, a channel, and a project are all resources in the same graph. They share:

• One permission model. Grant access once. A doc, the table it links to, and the channel about it obey the same rules — no five-way reconciliation.
• One search index. Find the thing, not the app it lives in.
• One real-time engine. Presence, cursors, and live edits aren’t a feature on one surface. They’re how every surface already works.

The point isn’t fewer tabs. It’s that the brief, the data, the discussion, and the plan stay connected — because they were never separate to begin with.

Specialized surfaces, unified data

Unifying the substrate doesn’t mean flattening the tools. A table is still a real database. A doc is still a rich-text editor. A board is still a board. What changes is underneath: they read and write the same graph, so a table view can live inside a doc, a task can link to a channel, and a change in one place shows up everywhere it matters.

That’s the whole idea. Keep the surfaces sharp. Make the ground they stand on one thing.

Open a workspace and feel the difference.