Where it stands
The software runs, and the whole cycle works end to end on the live system: writing a procedure, sending it for review, approving it change by change, signing, publishing, and checking the fingerprint chain.
The documents in it today belong to a made-up company.
Before it opens to other companies, each person gets a sign-in of their own, signing gets a proper identity check, and the separation between companies is proven with real accounts.
What an early shop gets: a say in what gets built next, a direct line for questions and fixes, and your own procedures, not demo data, deciding what gets fixed first.
- Controlled data
- Not for ITAR, EAR or CUI data.
- Where it runs
- Cloud only. The database is in AWS us-east-1, and the app runs on Vercel.
- The AI
- Anthropic’s Claude, called from Revari’s servers, only when someone presses a button.
- Getting your documents out
- There’s no export yet. It’s on the list.
What’s in it today
- Writing
- Numbered steps, tables, pictures, and flowcharts drawn inside the procedure. Links to sections of other documents.
- Review
- A route you configure. The people who sign approve each change first, then sign; anyone added just to read it marks it read. Work waiting for someone shows in their “Waiting on you” list. Nobody is notified yet, and reviewers can’t comment in the draft yet.
- Revisions
- One revision in force. Superseded ones stay readable and marked. Obsolete ones drop out of search.
- Lifecycle
- Draft, in review, approved, published, obsolete. Every step records who and when.
- Reading
- Search across published procedures, a light view for shop lighting, QR codes, and printing with the document number and revision on every sheet. Printed copies aren’t stamped uncontrolled yet.
- Evidence
- Each published revision is fingerprinted together with its approvals and chained to the one before. You can recheck the whole chain from inside Revari.An export with a standalone checker, so an auditor can verify your records on their own laptop.