Data you
can trust.
Workflows and election results, backed by evidence.
People follow the steps on their phones and attach the proof each step asks for. Hakiki keeps the record, who did what and when, so you can show it to anyone who asks.
14 days free. No card needed.
Form 34A, polling station 014
Presidential result
| Candidate | Agent | Second keying |
|---|---|---|
| Candidate A | 2,418 | 2,418 |
| Candidate B | 1,907 | 1,907 |
| Candidate C | 362 | 362 |
| Rejected ballots | 41 | 41 |
What you can rely on
Keyed by the agent, then again by a second person who cannot see the first figures. A mismatch opens a discrepancy.
Each audit entry carries the hash of the one before it, and the whole chain is re-checked every night.
Stored files are hashed again and compared with what was recorded when they arrived.
A ticked box proves nothing.
Most checklists let people skip what is inconvenient. Hakiki asks for the answer and the proof, in order, before work counts as done, then locks the result.
Without Hakiki
- Boxes ticked with nothing behind them
- No record of who did what, or when
- Steps skipped, nobody notices
- Records that can be quietly edited later
With Hakiki
- Workflows people follow step by step
- Photos and files required where they matter
- Every action timestamped and attributed
- An audit trail that shows any tampering
- 12:05:01Execution started8f3a…91c2
- 12:06:44Photo uploaded on step 3a27e…0d9b
- 12:07:11Submitted and lockedcc41…7f3a
Site visit, step 2 of 5
Is the generator running?
Photo of the meter reading
Required because the answer was yes
Why is it off?
Only asked when the answer is no
Ask only what applies.
A step can depend on an earlier answer. Skip what does not apply, and require a photo or a file exactly where the answer makes one necessary.
Everything a provable process needs.
Four parts that work together, so the record is complete without extra effort from the people doing the work.
Workflows
Versioned steps per department: yes/no, text, choices, numbers and file uploads.
Evidence
Photos and files checked on upload, stored privately and served only to signed-in users.
Audit trail
Who did what, when, on which record. Each entry is chained to the one before it.
Teams
People work inside their departments; what they can see follows their role.
Change the process without breaking the work.
Edit a new version as a draft while people keep running the active one. Work already started stays on the version it began with.
Version 3
Draft: new branch for night shifts
Version 2
Photo of the meter now required
Version 1
First published version
POST /api/executions
X-Api-Key: hk_live_…
{
"templateId": "4c1f…",
"label": "Site 14, weekly check"
}Connect it to your systems.
REST API
Start executions from your own systems with an API key.
Webhooks
Hakiki tells your systems when executions change.
Private file storage
Evidence goes to S3-compatible storage that only Hakiki can read.
Separated data
Row-level security keeps each organisation’s data apart in the database itself.
From a blank workflow to a locked record.
- 1
Write the workflow
A department head sets the steps, their order, what each one needs and when a step applies.
- 2
Publish it
People in the department see it and can start executions straight away.
- 3
Do the work
Each step is answered or proven with a file. Every action is timestamped.
- 4
Review and lock
The department head approves or rejects. An approved execution is locked for good.
| Person | Scope | Role |
|---|---|---|
| [email protected] | Whole organisation | Owner |
| [email protected] | Finance | Department head |
| [email protected] | Quality | Member |
Each organisation’s data stays its own.
People see what their role and department allow, and nothing from any other organisation.
Owner
Runs the organisation’s account: users, billing and the full audit trail.
Admin
Sets up departments, invites people and assigns their roles.
Department head
Writes and publishes workflows, then reviews and approves the work.
Member
Runs workflows step by step and uploads the proof each step asks for.
Wherever work needs proof.
Operations and field work
Site checks, maintenance and inspections with the photo that proves each one.
Compliance and audits
Records an auditor can follow from the first step to the sign-off.
Schools and programmes
Intake, onboarding and completion, tracked the same way every time.
IT and HR
Repeatable internal processes with someone accountable for each step.
Start free. Pay when it works for you.
14 days free, no card needed. Prices in US dollars.
Questions people ask.
Who is Hakiki for?
Any organization that needs structured, auditable workflows — compliance, operations, QA, HR onboarding, field work, and more.
How is data isolated between tenants?
Every record belongs to one organisation, and row-level security in the database only lets a request see its own organisation’s rows. The application checks the same thing.
Can one user have multiple roles?
Yes. A user can be Org Admin, Dept Head in one department, and a Member in another — all simultaneously via RBAC.
What happens when a workflow is completed?
It is locked: the service and the database both refuse changes, and every action is recorded in an audit trail built to show tampering.
Are file uploads secure?
Yes. Files are stored with UUID-based paths and served through authenticated API endpoints only.
Show your work. Keep the proof.
Write a workflow, publish it, and your team runs it from their phones. Every answer and photo lands in one record.