I build apps
founders ship.
Full-stack developer specializing in SaaS MVPs, e-commerce platforms, and admin dashboards — built with clean architecture and deployed to actually survive production.
Production-ready builds.
A full-stack website auditing platform that runs a real headless browser against any URL and surfaces actionable issues across performance, SEO, accessibility, security, UX, and conversion. The challenge was running Puppeteer and Lighthouse concurrently under real load — solved with a browser pool and a serialised Lighthouse queue to prevent Chrome port conflicts. Reports export as PDF, CSV, or JSON.
A full-stack website auditing platform that runs a real headless Full-stack furniture e-commerce store with a live admin dashboard, Role-Based Access Control, JWT authentication via HTTP-only cookies, and a Cloudinary image pipeline. Separately deployed frontend and backend — the kind of architecture a real production store would use.
Connects developers to open-source issues that match their tech stack by orchestrating the GitHub REST API. Upstash Redis caches results to cut redundant API calls, and per-IP rate limiting protects the system under unauthenticated traffic. Containerized with Docker for consistent deploys.
A multi-tenant micro-SaaS scheduling platform providing business owners with custom booking pages and automated confirmations. Built with strict data isolation utilizing schema-level foreign keys, relation traversal via Prisma, and action-level ownership validation. Race conditions are structurally prevented during high-concurrency booking actions using a hybrid approach of pessimistic row-level locking (SELECT FOR UPDATE) and Serializable transaction isolation levels.
Built for production, not just demos.
I'm a self-taught full-stack developer who builds complete web applications — from database schema to deployed product. I started with frontend and pushed myself deeper into backend to understand how real systems are architected and maintained.
I specialize in SaaS apps, e-commerce platforms, and service business tools. Not because that's a marketing decision, but because those are the problems I've spent the most time solving — which means I bring patterns that actually work, not just code that compiles.
My work is production-ready by default: Dockerized, CI/CD wired, and tested before I consider it done. I don't hand you a Vercel link with hardcoded secrets and hope for the best.
Currently taking on freelance projects. If you have a product idea or need a developer who can own the full stack, let's talk.
What I build for you.
Outcome-focused services. Tell me what you need to achieve — I'll handle the stack.
From validated idea to deployed product. Auth, billing, dashboard — built in weeks, not months.
- Multi-tenant architecture
- Stripe subscription billing
- Admin & user dashboards
- Role-based access control
Custom storefronts that sell. Secure checkout, inventory management, and an admin panel you'll actually use.
- Stripe / payment integration
- Product & inventory management
- Order tracking & emails
- SEO-optimized pages
Well-designed REST APIs and backend services that are a pleasure to integrate with and a nightmare to break.
- REST API design & build
- Third-party integrations
- Database schema design
- Authentication systems
Booking systems, client portals, and lead-gen sites for local businesses that need to look and work great.
- Appointment booking systems
- Automated email reminders
- Customer-facing portals
- Business owner dashboards
Data-rich internal tools that give you visibility and control. Real-time metrics, filters, exports — done right.
- Real-time data & charts
- Complex filter & search
- CSV / data exports
- User & team management
Dockerized deployments, CI/CD pipelines, and VPS setup so your app stays up and ships faster.
- Docker environments
- GitHub Actions CI/CD
- VPS / server setup
- Automated backups
How I build.
I didn't come up through a computer science program. I learned by building real things, breaking them, and figuring out why — which means every concept I know is attached to a problem I actually had to solve.
Over 2 years of daily building, I've shipped 5 production applications, gone from frontend-only to owning the full stack, and learned that the gap between "it works locally" and "it works under real load" is where most of the interesting problems live.
I'm not a generalist who dabbles in everything. I specialize in Next.js, Node.js, and PostgreSQL with Docker on top — and I go deep, not wide.
How a project works.
No big reveals at the end. You see real progress every step of the way.
Before writing a line of code, I understand what success looks like for you — a working demo, a shipped product, or a specific metric. Scope and timeline defined upfront, no surprises.
DB schema, API contracts, and component structure are defined before building starts. This prevents costly rewrites and keeps scope manageable as requirements evolve.
Core functionality ships first, then features are layered in. You get something real to use and react to early — not a big delivery at the end that surprises both of us.
Dockerized, CI/CD wired, VPS configured. I don't hand you a zip file or a Vercel link with hardcoded secrets — I hand you a live, running application you actually own.
What you actually get.
The things clients care about that rarely make it onto a resume.
I don't consider a project done until it's live. Dockerized, deployed, CI/CD wired — you get a URL that works, not a zip file and a good luck.
You see progress weekly — real, working features you can click through, not vague status updates. If something changes scope or timeline, I tell you immediately.
Clean architecture, consistent naming, documented decisions. Whether you hand it to another developer later or build on it yourself, the codebase won't be a mystery.
I give you a realistic estimate upfront, not an optimistic one to win the project. MVPs in weeks, not months — and I don't disappear when something gets hard.
You're not dealing with a dev shop where your project gets handed to a junior. I own the entire stack — frontend, backend, infra — which means no handoff gaps.
Under 24 hours for replies, always. If I'm unclear on something I ask — I don't spend a week building the wrong thing. Direct, clear communication every step.
Let's build
something real.
Tell me what you're building — I'll reply within 24 hours with a rough scope and honest timeline. No sales pitch, just a direct conversation.