Write the policy, get it approved by someone other than the author, and prove that everyone read the exact version. Every step lands in an audit trail that can't be quietly rewritten, on servers you control.
Pre-release. The first usable release, R1, targets Jan 2027; 31 of its 32 epics are done. See progress
Documents in a wiki, sign-offs in email, evidence in a spreadsheet: that's how most teams govern today. Procera keeps the whole loop in one place, with one history.
Write in the block editor, from a starter template or a blank page.
A second person approves. The author can't approve their own work.
Go live now or on the effective date. The old version is superseded.
People confirm the exact version, on a laptop or a phone.
Export who acknowledged what, with the content hash and sign-in method.
Every step is appended to a hash chain that the product verifies.
Each pillar lists what you can use on the main branch today. Everything else is on the roadmap with a date.
Write policies and SOPs in a block editor, review them with separation of duties, and publish on a schedule.
Ask people to read and acknowledge, send announcements with receipts, and (from R2) run requests and approvals.
Roles with scoped grants, a hash-chained audit log, encrypted files and workspace isolation enforced in the database.
An overview of what needs attention, every list as a data grid with saved views and exports, and reports later on.
Every screen here is the real app on the main branch, and every status comes from the public tracker. Workflow automation (requests, forms, the designer) is still being built, and the features page says exactly where it stands.
One governed home for policies (what and why) and SOPs (how), each with an owner, a version history and a lifecycle.
Ask people to read and acknowledge a specific version, chase them politely, and export evidence that stands up later.
Targeted news and notices, with an optional confirm-by date and approval before anything goes out.
Every change and every sensitive read is recorded in a per-workspace hash chain. Records can't be edited or deleted.
A permission catalogue, built-in role templates and custom roles, granted to people or groups and scoped to a department or collection.
From a ten-person startup to a multinational, in every department. Pick a role.
Start from the employee handbook pack, get it reviewed, and send it to everyone with a due date. Reminders and manager escalation do the chasing.
Next: Leave and onboarding requestsAvailable now
When someone on your team misses a due date, Procera tells you once, with a link straight to what's outstanding.
Next: Approve your team's requests from one inboxAvailable now
Home shows what's waiting for you. Read the policy, acknowledge it on the page, and get back to work.
Next: Raise and track requestsAvailable now
Roles with scoped grants, two-step verification required by role, and passkeys for step-up. Sensitive reads are logged too.
Next: Single sign-on and SCIM provisioningIn progress
Keep spending and expense policies versioned and reviewed by someone other than the author, and know who accepted which version.
Next: Expense and purchase approvalsAvailable now
Every change and sensitive read lands in a hash chain that Procera verifies. Export what an auditor asks for, with the version hash attached. Procera supports audit practices; it doesn't make anyone compliant by itself.
Next: Legal hold, cases and investigationsPlanned · R5, Aug 2027
Each acknowledgement records the version and its content hash, so “I read it” means this text, not whatever the page says today.
Authors can't approve their own documents, and reviewers confirm it's them with step-up before an approval counts.
Target a department, group or location, set a confirm-by date, and see reach and read receipts per post.
Every mutation and restricted read is chained by SHA-256. Change one record and verification fails from that point on.
How verification works (an illustration, with shortened hashes)
7c1e09abdocument.publishedOlivia Ownerprev 52f0c3d1a90f44e2acknowledgement.recordedBen Bakerprev 7c1e09ab3b2d71c8acknowledgement.recordedCara Chenprev a90f44e2e07a5f16evidence.exportedOlivia Ownerprev 3b2d71c8Chain verified: 4 records
Each release is usable on its own and ships when its end-to-end test gate passes. Requests and approvals arrive with R2; e-signing with R3.
Apache-2.0, with no telemetry by default. Procera needs PostgreSQL and an SMTP server. Valkey is an optional cache, and files sit on local disk today, with an S3-compatible backend next.
$ git clone https://github.com/CasualOffice/Procera.git
$ cd Procera
$ less docs/00-INDEX.md
# design docs, tracker and E2E packs are all in the repoRun it on your own server with Docker Compose, read the code and the design, and follow R1 as it lands. No sign-up, no sales call.