I design production-grade backend systems with a strong focus on:
- API contracts & response consistency
- Error management & observability
- Scalable NestJS architectures
- SaaS-ready infrastructure (multi-tenant mindset)
I don’t build demos.
I build foundations that survive production.
Enterprise-grade NestJS backend foundation
- Modular architecture
- Security-first design
- SaaS & multi-tenant ready
- Clean separation of concerns
🔗 GitHub: https://github.com/MertcanMert/nexus-api
Advanced Response & Error Management for NestJS
A dedicated system that standardizes every response, every error, and every log.
- Deterministic API responses
- Centralized error categorization
- Developer-friendly console observability
- Production-ready logging (JSON / ELK-friendly)
🔗 GitHub:
https://github.com/MertcanMert/nexus-api-v2-response-system
📦 NPM Package:
https://www.npmjs.com/package/nexus-api-v2-response-system
Reusable DTO utilities for NestJS
- Cleaner DTO definitions
- Validation consistency
- Reduced boilerplate
📦 NPM:
https://www.npmjs.com/package/armert-dto-for-nestjs
🔗 GitHub: https://github.com/MertcanMert/armert-dto-for-nestjs
- TypeScript
- NestJS
- Node.js
- PostgreSQL / Prisma
- Redis
- React
- Next.js
- TailwindCSS
- REST / OpenAPI
- GraphQL
- Docker
- Jest
I actively build and maintain:
- NPM packages
- Backend infrastructure modules
- Opinionated but extensible architectures
My goal is simple:
Reduce backend entropy. Increase system correctness.
- 📧 Email: mertcan@armert.com.tr
- 🌐 Website: https://armert.com.tr
- ✍️ Blog: https://dev.to/mertcanmert
Backend is not about endpoints.
It’s about guarantees.