case.studies

Engineering Documentation

Technical case studies for work you can't open-source

A curated collection of backend systems and production software from my career. When source code stays private due to confidentiality agreements, these case studies explain the architecture, tech stack, data flow, and engineering decisions instead.

View Projects Portfolio
Architecture System design & diagrams
Tech Stack Languages, infra & tools
Engineering My contributions & trade-offs

Confidentiality

Why are some repositories private?

Many projects here were built professionally or in collaboration with organizations.

Their source code contains proprietary business logic, confidential assets, or intellectual property owned by the respective organization. I cannot legally publish those repositories — but I can document the engineering behind them.

  • Architecture
  • Technologies
  • Backend design
  • APIs
  • Data flow
  • Deployment
  • My contributions

Portfolio

Projects

Engineering-first documentation for systems built in production environments.

PharmaStock

B2B pharmaceutical stock management platform connecting distributors and pharmacies — inventory uploads, searchable catalog, and stockist lookup.

Open Source Private Server API
Go Echo v5 PostgreSQL HTMX Docker Linux VPS Nginx
View Case Study GitHub

DevFlow

Terminal-first developer workspace manager unifying project registries, command execution, tmux sessions, and Git operations into a single Go TUI.

Open Source TUI System
Go Bubble Tea Lip Gloss tmux Git CLI SQLite
View Case Study GitHub

Clinqer

Scalable, event-driven Hospital Management System automating clinic workflows, WhatsApp communications, idempotent webhooks, and distributed BullMQ job processing.

Confidential N6T Technologies
Python Django REST PostgreSQL Redis BullMQ WebSockets AWS EC2
View Case Study

About

Dhrutinandan Swain

Backend engineer focused on reliability, data integrity, and maintainable architecture.

This site exists because some of my best work lives behind NDAs. Rather than leaving gaps on a résumé, I document the technical depth — architecture trade-offs, API design, data flow, and production constraints — from real projects I've built and deployed.