Encrypted personal documents
iQabinet
Sensitive documents needed more than a password and a promise.
The problem
Families had important records spread across inboxes, filing cabinets, and individual provider portals. Centralizing those records made access easier, but raised the stakes for security and availability.
The work
What I carried.
iQabinet helped families organize and share financial, health, and household records through a secure, geographically redundant cloud service.
- 01
Set the technical roadmap and led architecture, delivery, and operations for the AWS-based platform.
- 02
Introduced split-key encryption so no single stored key could unlock a user's document collection.
- 03
Built and managed a distributed engineering team in Gujarat, India, with continuous delivery across cloud migrations.
Selected outcomes
Decisions that mattered
Assume the data matters
Financial and health records deserved an architecture that limited the damage of any single credential or infrastructure compromise.
Design for migration
The platform moved from Heroku and hosted MongoDB to AWS while customers continued to depend on their records.
iQabinet shaped a principle I still use: architecture should reduce what a user has to trust.