inkury
A local-first document platform’s editor becomes aanty’s canvas.
How inkury fits into aanty
inkury is a local-first document platform with a canonical model, Blake3 hashing and a CRDT-ready core — but comments, mentions, presence and sync are all Phase-2 placeholders today. aanty provides that comment/mention/presence layer, and in return inkury’s editor becomes aanty’s own canvas and docs engine — a two-way strategic fit, not a one-way integration.
Comments, mentions, presence
aanty fills inkury’s Phase-2 placeholders — comments, @mentions and live presence — on top of its CRDT-ready core.
inkury’s editor as aanty’s canvas
The two-way fit: inkury’s document engine becomes the canvas/docs surface inside aanty’s own product.
Shared auth foundation
Builds on the passkey/WebAuthn stack inkury already shipped, rather than a second identity system.
Bi-directional integration
Events flow both ways: inkury activity lands in aanty as a typed message in the right thread, and actions taken in aanty — approvals, replies, assignments — flow back out to inkury, kept in sync through the same tenant-scoped access controls as the rest of the product.
See it alongside
Other integrations and pages that pair naturally with this one.
See inkury inside a real aanty workspace
Bring the inkury events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.