Docs vs Notion: what each does today
Notion changed what people expect from a document tool. Pages inside pages, blocks you can drag around, a slash menu, databases that turn a doc into a lightweight app. Docs, the Notion alternative in the zerosoft suite, borrows a lot of those ideas, and implements a much smaller slice of them.
So this post is a map: where Notion is clearly ahead, what Docs actually does, and how to tell which one your team needs.
The short version
- Notion is a mature, all-in-one workspace: realtime collaboration, powerful databases, built-in AI, import and export from many formats, a large integrations ecosystem, and apps on every platform. It does a lot, and does most of it well.
- Docs is open source (AGPLv3), self-hostable, and focused: a block editor, nested pages,
[[links, templates, comments, sharing and a trash. It's a good fit for a team wiki, meeting notes and specs, on your own server if you want.
Where Notion is clearly ahead
Realtime co-editing. In Notion, several people can type on the same page at once and see each other's cursors. Docs saves automatically, but it doesn't merge simultaneous edits: if two people edit the same page at the same time, the second one to save gets a warning and chooses between loading the new version or overwriting it. For a wiki with page owners that's manageable. For a team that writes together live, it's a dealbreaker.
Databases. This is Notion's superpower. Relations between databases, rollups, formulas, many property types, and views like board, calendar and timeline over the same data. Docs has a database block: a small table with typed columns (text, number, select, date) that you can view as a table or a gallery. Useful for a list of tools or a reading list. It's not a replacement for a Notion database that runs half your operations.
AI. Notion has AI built in for writing, summarizing and answering questions across your workspace. Docs has no AI features.
Import and export. Notion imports from many tools and file formats, and exports to Markdown, HTML and PDF. Docs exports each page to Markdown, and to PDF through the print dialog, one page at a time: there's no export of the whole space. There's no Notion import either.
Search. Notion searches across the content of every page. Docs searches page titles. It's what powers [[ links, and doesn't search inside page bodies.
Integrations and API. Notion has a public API and a large ecosystem of integrations and automations. Docs has neither yet.
Apps, offline and polish. Native desktop and mobile apps, published sites on your own domain, synced blocks, years of refinement. Docs runs in the browser, and that's it.
Enterprise. SSO, audit logs, granular permissions. Our enterprise pieces (SSO/SAML, audit logs, custom roles) are in development in /ee, not shipped.
What Docs actually does well
The editor basics. Type / for the command menu: paragraphs, three heading levels, bulleted and numbered lists, to-dos, quotes, code blocks with a language, dividers, simple tables and the database block. Inline formatting, page icons with an emoji picker, cover images.
A real page tree. Pages nest as deep as you need. The sidebar shows the tree, you can drag a page onto another to nest it, and moving a page carries its whole subtree.
Links and mentions. Type [[ to link another page by title. Type @ to mention a teammate and notify them.
Templates. Meeting notes, project spec and weekly retro, plus blank. You can't save custom templates yet, but Duplicate copies a page with all its subpages, which makes a "Templates" section in your wiki work surprisingly well.
Comments. On the whole page or on a specific block, with resolve and reopen.
Sharing and trash. A share panel for anyone with the link, a team or one person, with view or edit access; people with view access open the page read-only. A trash where pages can be restored or deleted for good.
Version history. Docs saves an automatic version at most every 5 minutes while you edit, plus the ones you save by hand, up to 50 per page. Restoring a version first saves the current one, so nothing is lost.
Help center. The pages you publish become a public help center at /h/<your-handle>, with collections, search and a "Was this helpful?" vote per article. It isn't a site with its own domain and design like one published from Notion.
We wrote a step-by-step guide to building an internal wiki with Docs if you want to see these pieces working together.
Where Docs has an edge
You own it. AGPLv3, self-hostable, pages stored in a SQLite file or a libSQL/Turso database you control. No vendor can change the terms on your company's knowledge base. If lock-in worries you, this is the point.
It's part of a suite. The same login and team get you Track, Chat, CRM, Cal and Link. One concrete connection: Chat's auto-answer bot can use your Docs pages as its knowledge source (with AI enabled it answers from the most relevant pages; without it, it falls back to keyword matching). Your wiki can answer the simple customer questions.
Less to configure. Docs has fewer features, and that's not purely a weakness. Teams that drowned in Notion setups (databases of databases, relations nobody understands), sometimes do better with a tool that can only do pages and links.
Pricing. Notion has a free plan and per-seat paid plans, with AI priced on top on some plans; check their pricing page for current numbers. Docs self-hosted costs $0. zerosoft Cloud has a free tier, then charges per workspace for usage (clicks, bookings, emails, storage), with free seats.
Who should stay on Notion
Stay if:
- Your team writes on the same pages at the same time, often.
- You run real workflows on Notion databases: relations, rollups, formulas, board and calendar views.
- You use Notion AI daily.
- You need full-text search across a big workspace.
- You depend on integrations, the API, or publishing a site on your own domain.
- You need mobile or desktop apps, or offline access.
- You have years of content in Notion. With no importer, moving it would be manual work.
For those teams, Docs would be a step down, and we'd rather you know that before trying.
Who Docs is for
- Small teams that need a wiki, meeting notes and specs, with clear page owners.
- Companies that want their internal knowledge on their own server, under an open-source license.
- Teams already using other zerosoft products, especially Chat, who want docs and support in one place.
- Anyone who found Notion more powerful than they needed and is paying per seat for power they don't use.
The bottom line
Notion is the broader, more capable product, and for many teams it's the right tool. Docs is a lean, open, self-hostable editor that does pages, links, templates and comments well enough to run a team wiki, and that you own. We'll keep closing the gaps; realtime co-editing is on our roadmap. Until it ships, we won't claim it.