Our Declaration
Operations
must be
provable.
We built Hakiki because "pencil-whipping" destroys enterprise value. Paper checklists and standalone forms are untrustworthy. Organizations need structurally enforced, mathematically verifiable truth.
The Architecture
of Compliance.
Hakiki isolates state. We allow department heads to engineer workflow templates via a strict Node Builder. Once published, these templates are locked.
When an operator triggers a workflow, the system spins up a totally isolated, time-stamped Execution Instance binded to that exact template version. Data flows sequentially. Role-Based Access Control (RBAC) gates prevent tampering.
Upon completion, the entire execution is ingested into a PostgreSQL instance and converted into an immutable ledger record.
System Hierarchy Enforcement
Tenant AdminAUTH_OK
Absolute organizational orchestration, SLA monitoring, and cross-department visibility.
Org AdminAUTH_OK
Department structuring, domain partitioning, and high-level role assignment.
Dept HeadAUTH_OK
Workflow template authoring, version control management, and logic definition.
Team MemberAUTH_OK
Active execution of rigid processes and upload of cryptographic evidence.
Under the hood.
We didn't just build a frontend. Hakiki is backed by enterprise-grade backend infrastructure. Every API endpoint enforces strict validation schemas before writing to disk.
INFO [Core] Initializing RBAC policies...
INFO [DB] Postgres instance migrated securely.
SYNC [Storage] S3 Buckets restricted.
INFO [Audit] Hashing interceptor active.
Template versioning — updates create new versions, history always preserved
Strict ordering — optionally require steps completed in rigid sequence
Multi-participant executions — add team members via enterprise SSO directory
Secure file uploads served through authenticated, UUID-based endpoints
Five static step types — boolean, text, single-select, multi-select, file upload
Full audit logging — every action permanently cryptographically hashed
Email notifications for core system states (trigger, wait, complete)
Complete multi-tenant data isolation engineered at the postgres service layer