Tougather vs Notion: where each one actually wins

Deze pagina in het Nederlands

Where Notion wins

Starting with the losses, because a comparison without any is an advert.

Databases, relations and rollups

This is the real one. A Notion relation joins two databases, a rollup reads a value back across the join, and the same rows appear as a table, a board, a calendar or a gallery. None of that is here. A table in Tougather is a spreadsheet table: eight column types — text, number, currency, percent, date, checkbox, select and formula — with sort, filters, conditional formatting and per-column validation, and one view, the grid. Kanban exists, but as a board template of stickies, not as a second view of your rows. The nearest thing to a relation is a formula reaching into another table, which is worse at what relations are good at: following a link from one record to another and back.

A template gallery years deep

Notion's templates are thousands of pages of other people's work, and for some readers that is the product. Tougather ships six project templates and six board templates, plus what you save out of your own projects. Six is not a gallery.

Sharing that is already approved

Notion shares per person, per group and per guest, and publishes a page to the web. Tougather shares per link, and the document travels inside the URL fragment — the part after the # that browsers never send to a server. That makes a link genuinely private and genuinely unrevokable at once: whoever holds it holds the document. There is an admin surface, but it runs only against a real database, and with none configured every call returns a setup notice.

Native apps and a public API

Notion has desktop and mobile apps and an API a whole integration industry sits on. Here there is an installable PWA and no native build — no React Native, Capacitor, Expo, Electron or Tauri in package.json. The four API routes cover AI, checkout, the collaboration relay and config; none lets another program read a project.

A formula engine, not formula properties

A Notion formula is an expression over one row's properties. Useful, and not a spreadsheet: there is no cell to point at, so no B2, no rectangle, and no way to say “this column, forty rows down, in the other table” unless a relation is already there.

Here it is a grid with 167 functions in one library — maths, aggregates, logic, conditional aggregates, lookup, text, dates, type predicates, finance, statistics. Addressing is A1, and a fill preserves what you pinned: =B$2*$C2 dragged anywhere keeps both halves, rewritten over your source text so spacing and capitalisation survive. Every table in a project is also a sheet, so Costs!B2:B40 and [Costs]![Amount] reach across tables in the same document. A cell asked for while it is still computing returns #CYCLE! instead of hanging the tab.

Nine functions are absent on purpose, each answering with its reason rather than a bare #NAME?: RAND, RANDBETWEEN, UNIQUE, SORT, FILTER, TRANSPOSE, INDIRECT, OFFSET and VBA. Four need a spill model this does not have, two would build references at run time and blind the cycle guard, and macros are refused because repeating something over every row is what a formula column already is. If a spreadsheet is most of what you want, if it's mainly a spreadsheet you need is the closer comparison.

Slides, and a second screen

Notion has no slide editor. People build decks out of pages and present them full screen, or they leave for Google Slides. Here a deck is a block in the same project as the document and the table, with a master carrying logo, footer, slide numbers and background to every slide that does not opt out. Builds reveal by bullet, by object, by both or not at all — the whole animation model, because anything more is something you operate while also talking.

Presenter view is a second window with your notes, a clock you start and reset, and the slide coming next. The audience window stays the authority on position and the presenter window only sends requests, so the two cannot disagree. Know the limit first: it runs over BroadcastChannel, so it is two windows of the same browser on one machine, not a phone driving a laptop. Decks read and write .pptx with speaker notes, though an import drops theme, images, positioning and animations rather than half-copying them. For what belongs on the slides, building a deck when your tool has no slides has the outline.

A page that prints

A Notion page is a web page: it is as long as it is, and paper happens to it afterwards. A thesis or a client report is page-shaped first, usually stated as “A4, 2.5 cm margins, page number bottom right”. So there is a page setup here: A4, Letter or Legal, portrait or landscape, margins in millimetres, page numbers in the footer or header. Half of that works in a browser print, and the code says which half. Size, orientation and margins ride on @page; headers, footers and page numbers do not work in a browser print at all, because CSS margin boxes are unimplemented in every shipping engine. They go into the Word export instead of being a setting that silently does nothing.

That export is real OOXML: footnotes Word lays out on the page, w:ins and w:del tracked changes it can review, a header with a page field, a table-of-contents field. Reading .docx goes the other way and brings tracked changes in as proposals you accept or reject. Around it sit numbered footnotes, a contents list derived rather than stored, and citations in APA 7, MLA 9, Chicago and Harvard. The gaps are nearby: PDF export is window.print() into a clean popup rather than a generated file, equations reach Word as LaTeX rather than OMML, and PDF import does not exist.

No account, no server

Notion is an account first. Here the free plan has no login: you open the app and the work goes into this browser's local storage. Nobody can read it, including us, because there is nowhere to read it from — and that same sentence is the risk, because nothing is backed up and clearing your browser data deletes it.

Three things push back: the app asks the browser for persistent storage, it estimates the room left, and it exports one backup file holding every store plus the fonts and pictures in IndexedDB. The ceiling is measured rather than guessed — 50,000 rows is 3.4 MB and opens in 0.56 s, and 100,000 rows is refused because browser storage is full. Offline follows from all this rather than being bolted on; Notion's offline limits, explained sets both side by side.

Side by side

Who should stay on Notion

The cases where switching would cost you something real:

• Your workspace is built on linked databases. Relations and rollups have no equivalent here.
• You read the same rows as a board and a calendar. There is one view, and it is the grid.
• Gallery templates are how you start every project.
• An IT department has to approve the tool, or people outside your team need access per person.
• You depend on the API, on native mobile, or on tools that sync into Notion.

Where this fits is narrower: one document holding numbers you can compute, slides you can present and a page you can hand in, without an account and without a connection. If the question is broader than these two tools, we keep every comparison in one place, including Google Workspace compared.

Questions people ask