Good document experiences begin below the surface. Oxora’s foundations keep rendering, editing, and extraction in distinct, considered layers.
A modular document core
Document state sits behind an engine-independent interface. Editing commands, snapshots, and anchors stay separate from the React view, creating room for the engine to evolve.
Basic rich-text editing and stable paragraph identities
Comments anchored to a passage
Local replica synchronization experiments with Yjs
PDFs with a path back out
A Rust and WebAssembly foundation handles browser-based PDF workflows. Exported annotations are reopened and checked before download.
PDF rendering and page navigation
Ink and rectangle annotations with undo
Native PDF annotation write-back
Extraction with explicit boundaries
Use native PDF text extraction for digital documents. Scanned-page OCR can use optional Google Document AI or AWS Textract adapters, with provider configuration kept outside the document UI.
Build alongside us
These foundations are in development. There is no public production API or supported SDK release yet. We’re interested in the workflows, integration constraints, and document edge cases you need to solve.
// A separation of responsibilities, not a public API. Document experience └── Document core ├── PDF rendering & annotation ├── Text editing & anchors └── Text extraction & OCR adapters
Early foundations, clearly described. Full DOCX fidelity, production collaboration, and hosted identity controls are not available today. Talk with us about the pieces that matter for your use case.