Lattuce tutorial · Comparisons & assistant
Using Lattuce alongside Notion
Use Lattuce with Notion to keep team knowledge in place while moving source-grounded research and writing into Writer.
Notion is built teams-first: real-time co-edit, relational databases, and workspace Ask across pages your team already wrote. Lattuce is built research-first: PDF grounding, citations, missions, translation, and self-hosted sovereignty.
Treat the boundary as a deliberate handoff, not a promise of a live two-way mirror. Notion can remain the shared operating manual while Lattuce holds the evidence, private drafts, review state, and export that must be reproducible.
When to use both
| Need | Use |
|---|---|
| Lab ops wiki, meeting notes, generic PM | Notion |
| Papers, PDF corpus, grounded compose, Weblate | Lattuce |
| Household research + writing with data at home | Lattuce (optional Notion for chores/planning) |
What Lattuce is adding for Notion-shaped teams
- Workspace Ask — grounded Q&A across vault notes, library sources, books, calendar, and the current paper draft (operator LLM required).
- Unified records — library collections as multi-view databases with persisted view tabs, filters, sorts, groups, and layout settings (table/board/calendar/timeline/gallery/list/relations). See
/api/databases/{database_id}/views. - Real-time co-edit — live notes, boards, and whiteboards with presence, reconnect recovery, and REST/offline fallback. Paper sections keep approval-gated REST editing; section-scoped discussions ship in Writer compose (Review pane and mobile sheet).
What Notion still wins
- Mature real-time multiplayer on every block
- General formula/automation language and arbitrary workflow automation
- Template and integration marketplace scale
- SaaS zero-setup for individuals
Integration pattern
- Keep Notion for team runbooks and non-academic PM.
- Run Lattuce on your VPS for sources, study, and DOCX export.
- Link out from Notion pages to Lattuce papers (
/papers/...) and share-token note readers. - Use MCP (
/mcp) so Cursor/Claude can search notes and run digest jobs against Writer — see Integrations and sync for the public boundary. Sync stays on REST; MCP is the online AI sidecar.
A safe handoff checklist
Before moving work from Notion into Lattuce, agree on:
- the page or database that remains authoritative for team decisions;
- the source files and citations that must be preserved in Library;
- who can see the Lattuce paper or share-token note;
- whether the handoff is a one-time export, a link, or an approved MCP operation; and
- where the final DOCX, bibliography, or decision record will be stored.
After the handoff, open the paper in Writer, check that every source is ready, and send back a stable link or exported artifact. Avoid pasting generated prose into the team wiki until a human has checked its citations and ownership.
What does not sync automatically
Notion relations, general formulas, permissions, comments, and templates do not become equivalent Lattuce objects just because a page links to a paper. Likewise, Lattuce source readiness, Writer approval state, and Weblate translation segments remain Lattuce workflow state. Keep a short handoff note in both systems when that state matters.
AI cost
Notion Business (~$20/user/mo) for sustained AI. Lattuce uses your LLM keys (DeepSeek/OpenAI) — see operator cost docs.
Related: Writer sources · Notes workflows · Integrations and sync
Browse more in Comparisons & assistant or return to all tutorials.