Engineering software that has to be trusted, not just shipped.
I'm Peemkay, founder and lead engineer at Peemkay TECH, a software practice built around one idea: the sector shouldn't determine the quality bar.
Peemkay TECH began the way most serious engineering practices do , solving a real, high-stakes problem. Early work building secure communications, dispatch management and biometric identity verification systems for a military signal corps set the bar: the software had to work offline, protect sensitive data, and never fail quietly.
That same discipline now carries over into every engagement , whether it's a Django storefront processing real customer payments, a student portal serving an institution, or a new AI-driven idea that needs a technical co-builder, not just a coder for hire.
I work end-to-end: architecture, backend, frontend, mobile and deployment, across Python (Flask/Django) and Flutter, with computer vision and biometric systems as a specialty. Confidential and NDA-based engagements, common in government and defense work, are a normal part of how I operate.
Core values
Security by Design
Authentication, access control and data protection are part of the architecture, not an afterthought.
Confidentiality
Government, defense and enterprise clients get NDA-respecting workflows and discretion by default.
Cross-Sector Versatility
The same rigor applies whether the system serves a signal unit or a fashion boutique.
Clean, Maintainable Engineering
Code that the next developer, or future you, can actually read, extend and trust.
A process built for accountability
Six stages, applied whether the project is public-facing or fully confidential.
Discover
Understand the real problem, constraints and stakeholders before writing a line of code, including compliance or confidentiality requirements.
Design
Architect the system: data models, security boundaries, and the platforms it needs to run on.
Develop
Build in focused, reviewable increments with clean, documented code, not throwaway prototypes.
Secure & Test
Validate authentication, access control and edge cases, especially for offline, low-connectivity or sensitive environments.
Deploy
Ship to production with proper configuration, monitoring and a clear handover.
Support
Stay available for fixes, iteration and scaling as the project's needs grow.