Product specs, policy wikis, design briefs, and writers' rooms all suffer when the tool treats a document as a single autosaved blob. Canvas brings save points, draft lines, and semantic diffs to team docs; Plot extends the same platform to scripts and production — one Team subscription for creative and operational work.
The RFC still needs a decision on rate limits before eng review Thursday.
Branched a draft line for the alt API shape — main stays stable.
Save point “Ready for eng review” is frozen — comment away, nothing overwrites it.
0+
Block types on Canvas
0
USD / seat / mo (Team)
0%
Pro features included
Your org already lives in shared docs — Inkwell adds save points, draft lines, and block-aware diffs so async review means “diff since last milestone,” not “please re-read the whole wiki.” RFCs survive eng review cycles; policy paragraphs have audit milestones; onboarding docs evolve without silent rot.
Mara co-writes the pilot cold open on Plot.
Priya versions the budget + production wiki on Canvas.
Same save-point history across the script and the ops docs — one subscription, not two tools.
Creative teams should not juggle Final Draft for scripts and a separate wiki for specs, briefs, and runbooks with no shared version model. Team plan covers Plot co-writing for writers' rooms — scripts, treatments, and series bibles — plus Canvas for specs, research docs, and internal wikis: the same save-point semantics across both products.
Remote and hybrid teams review on their own schedule. Comment threads stay on the block; save points freeze “ready for sign-off” states; diffs replace “please read the whole doc again.” Legal, product, and creative passes reference the same named baseline.
Inkwell — async review breaks when the tool only autosaves — named save points turn “please re-read the whole doc” into a diff since last sign-off.
The three primitives that do the heavy lifting in this workflow.
Parallel document versions the whole team can compare — policy drafts, spec spikes, or alt cold opens on Plot. Incorporate what worked; keep rejected branches for reference.
Control who edits, comments, or administers the workspace. Team tier includes permissions and audit-oriented features — see pricing for current scope during beta.
Team-level skill configuration for repeatable passes on your docs — tone, structure, research digest — with reviewable diffs inside the canonical document.
Skills and diffs run on your draft — nothing lands until you accept it. Every accepted change can become a save point.
How product and engineering teams use save points and diffs instead of duplicated filenames.
Headings, code blocks, citations linked to sources — structure from the first paragraph, not pasted from a chat summary.
Reviewers comment on blocks; no one overwrites the baseline while async feedback arrives across time zones.
Alternate API shape or policy wording lives on a branch — main stays stable until sign-off.
Semantic diff between save points shows exactly what changed. Incorporate the spike or discard — history preserved either way.
We name what Docs, Notion, and Confluence do well. Inkwell is for teams that need named history and semantic diffs on top.
Google Docs
Frictionless real-time co-editing everyone already knows.
Inkwell difference
Inkwell adds named save points, draft lines, and semantic diffs — async review and rollback are first-class, not buried in version history.
Notion
Flexible blocks and databases for team wikis.
Inkwell difference
Canvas matches block flexibility but treats version control as core — immutable save points and branch-like draft lines, not page snapshots alone.
Confluence
Enterprise wiki with permissions and audit expectations.
Inkwell difference
Inkwell diffs at block and paragraph granularity between named moments; Team plan includes role-based permissions and audit-oriented features.
Final Draft / WriterDuet
Deep screenplay formatting and room collaboration for scripts.
Inkwell difference
Plot covers screenplay-native workflows — scripts, treatments, and series bibles; Canvas + Team extends the same platform to specs, research docs, and runbooks — one subscription for creative and operational docs.
Migration, granularity, pricing, and feature status — the concrete questions buyers raise before they switch.
Team includes everything in Pro plus real-time collaboration, team workspaces, shared draft lines, role-based permissions, custom AI skill configuration, and Canvas access for members. Plot and Canvas both ship on Team — see the pricing page for the live feature matrix during beta.
Docs and Notion excel at familiar co-editing and flexible wikis. Inkwell adds named save points, draft lines, and semantic diffs as first-class primitives — closer to how engineering teams version code than how word processors autosave a single file.
Yes. Team covers Plot for screenplays and room collaboration plus Canvas for specs, research docs, and internal wikis — one platform with two products instead of separate tools for scripts and everything else.
Audit logs come with the Team tier — owners and admins review workspace activity from organization settings. SSO is an Enterprise feature — contact team@inkwell.software about Enterprise for SSO, custom deployment, and an SLA. Scope may evolve as Team and Enterprise features ship during beta.
Writers' rooms & co-writers
Parallel takes without losing the room's history
Read the guide →Researchers & technical writers
Citations, structure, and history — not one undiffable blob
Read the guide →Showrunners & executive producers
See what changed, which pass stuck, and what the room tried
Read the guide →Plot + Canvas on one subscription — shared workspaces, draft lines, and permissions for creative and ops teams.
Or email team@inkwell.software
