Features
What Hakiki does, in detail.
Structured workflows, evidence on the steps that need it, review, and an audit trail that shows any tampering. Here is how each part works.
Who can see what
Acme Health
- Theatre
- Pharmacy
Riverside Schools
- Admissions
- Transport
Each organisation sees only its own rowsEnforced by the database
Separation
Each organisation’s data stays its own.
Every record belongs to one organisation. Row-level security in the database lets a request see only its own organisation’s rows, and the application checks the same. Inside an organisation, departments and roles decide who sees which work.
Evidence
Proof that is checked, not just attached.
A step can require a photo or a file. Hakiki checks the file’s type against what the step allows, records its hash when it arrives, and checks every stored file against that hash each night.
meter-reading.jpg
Step 4: photo of the meter
- File type
- image/jpeg, allowed for this step
- Size
- 2.4 MB
- Hash recorded
- e3b0…b855
- Checked again
- Every night
Everything else you get.
Versioned workflows
Improve a workflow as a draft while the published version keeps running. Work in progress stays on its version.
Six kinds of step
Yes or no, text, one choice, several choices, a file upload, and a table of numbers.
Locked when done
A completed execution is locked: the application and the database both refuse changes to it.
PDF records
Export an execution, with its answers and evidence list, as a PDF to share or file.
API and webhooks
Start executions from your own systems with an API key, and get told when they change.
Two-step sign-in
Protect accounts with a code from an authenticator app such as Google Authenticator.
Private file serving
Evidence files have no public links. They are served only to signed-in people allowed to see them.
Review
Department heads approve or reject completed work, and the decision is recorded with it.
Try it with your own process.
14 days free, no card needed. Write one workflow and run it with your team.