Multi-tenant SaaS, enterprise dashboards and REST APIs — built with Go, Next.js, React and PostgreSQL, and shipped through pipelines instead of by hand.
Three systems in production — inventory floors, payroll and patient records. Each one is a case of getting the boundaries right before the first user showed up.
Inventory, sales and warehouse movement in one system, with dashboards that stay current while the data underneath keeps changing.
Full stack — Go services, React dashboards
An HR platform where every organisation runs in its own tenant on shared, reusable modules for employees, attendance and leave.
Full stack — architecture, auth, CI/CD
One platform for dietitians, counsellors, admins and patients — four roles reading the same records through very different windows.
Full stack — role model, dashboards, pipeline
Aadil KhanBHOPAL, INDIAFor three years I've been building the software people actually run their day on — inventory floors, payroll, patient records. I care about the parts that decide whether a product survives its first thousand users: the data model, the auth boundary, the deploy that happens without anyone watching.
On the backend that means Go and Node.js over PostgreSQL and MongoDB — REST APIs with JWT auth, refresh token rotation and role-based access control. On the frontend, React and Next.js: dense dashboards rather than marketing pages. Before this I spent a year teaching web development to 200+ students, which is still the fastest way I know to find out whether you actually understand something.
Grouped by the job each tool does, not by how popular it is. If it is on this list it is because I have shipped something with it.
What the systems are written in
Services and APIs
Interfaces and dashboards
Storage and access
Access control and sessions
Pipelines and servers
Where it runs
Day to day
A new product, a system that needs modernising, or a backend that has outgrown its first version — send me the details and I’ll tell you honestly whether I’m the right person for it.
