✳ Nairobi, Kenya
- WhatsApp+254 799 756 331
- Emailhello@muvevi.com
- LinkedInlinkedin.com/in/muvevi
- GitHubgithub.com/mutua-muvevi
- Twitter / X@muvevi
Available for freelance & full-time roles.
Let's build something great.
Backend & API Development
NestJS REST and GraphQL APIs, background job systems, webhook integrations, and data pipelines — built to scale, documented properly, and handed over in a state you can maintain.
A good backend is invisible. When it's working, you don't think about it. When it breaks, you lose users and money. I build backends with that in mind — proper error handling, structured logging, queue-based job processing, and API contracts that don't break clients when they change.
NestJS is my primary framework because it enforces structure at scale. Fastify as the HTTP adapter because it's genuinely faster than Express and the overhead matters under load. Prisma for type-safe queries that don't produce mystery runtime errors.
I've integrated with Stripe, M-Pesa Daraja, Resend, Cloudinary, Firebase, Twilio, and a handful of custom third-party APIs. The pattern is always the same: typed clients, retry logic, dead-letter queues for webhooks, and proper error surfaces.
- NestJS + Fastify REST API (or GraphQL)
- Prisma ORM + PostgreSQL schema design + migrations
- Background job system (Bull + Redis)
- Webhook handling with signature verification + retry queues
- Rate limiting, request validation, and input sanitisation
- Structured logging (Pino) + error tracking (Sentry)
- Third-party integrations (Stripe, Daraja, Resend, Cloudinary, etc.)
- OpenAPI / Swagger documentation
- Docker + docker-compose for local dev
- Render / Railway / VPS deployment config
Resource modelling, endpoint design, auth model, and error response spec — documented before coding starts.
Database schema review or design, with migration strategy for zero-downtime deploys.
Core API, then third-party integrations, then background jobs. Integration tests run against a real test database.
k6 load tests to verify performance under expected traffic before any production deploy.
Full Swagger docs, environment variable reference, and a recorded architecture walkthrough.
Scalable APIs that hold up when the traffic comes.
Questions before committing? Let's talk.