I’m Hardik Ajmeriya, a full-stack developer. MERN applications built and deployed to AWS with CI/CD, containers and monitoring — one person, from first commit to live URL.
Three featured builds, then the full index. Hover a screen to look around it, or open any project in the list for details.
A website for an architecture practice where every house is drawn before it is built: as you scroll, a line drawing draws itself, gains dimensions, and is revealed as the finished photograph. Includes a drag-to-compare retrofit with revision clouds and an interactive materials schedule.
01 / 04 · Drawing turns into the house on scroll
A product landing page for an original Indian sweets brand. The hero swaps four sweets, each with its own colour palette, by click, auto-play or scroll; one toggle switches the whole page, prices included, between English and Gujarati; and a pinned gift box opens and fills itself compartment by compartment as you scroll.
01 / 04 · Hero and product switcher
An inference API sold by the request. SHA-256 hashed keys, per-project budgets enforced before spend rather than after, a bearer-auth public endpoint, and a dashboard reporting requests, p95 latency, error rate and margin.
Booking platform for a Bengaluru training studio. A live class schedule enforces per-session capacity, members sign up and authenticate over JWT, and coach profiles and tiered membership plans are all served from the API.
Table reservations for a thirty-eight cover restaurant. A server-side availability engine resolves every sitting against a fixed timezone and real capacity, so a booking made from any machine lands on the slot the kitchen expects.
Property portal for a Mumbai agency. Listings across seven PIN codes are filtered and full-text searched in MongoDB, alongside area guides, agent profiles and a valuation-request flow that reaches the office as a qualified enquiry.
A storefront built for a working Rajkot pottery and its real customers: a bilingual English and Gujarati catalogue, cart and checkout, WhatsApp and cash-on-delivery ordering, and delivery rules that match how the workshop actually ships.
A structured medicine management and storefront system with automated categorisation and real-time backend synchronisation, integrated into a wider medical platform.
Real-time visualisation of Jenkins pipeline runs with AI-assisted failure analysis. Streams build stages over SSE, processes logs deterministically and generates structured failure insights.
End-to-end delivery pipeline: Terraform-provisioned EKS, GitOps deployment through Argo CD, automated builds in GitHub Actions, and OpenTelemetry-based monitoring.
Cluster observability stack collecting and visualising pod health, CPU and memory usage, and service performance through Grafana dashboards.
Most developers hand you a repository. I hand you a running application with the infrastructure behind it, and stay on to keep it running.
Custom applications built on the MERN stack — client portals, admin dashboards, storefronts, booking systems and internal tools. Built to your requirements, not a template.
Subscription products built end to end — multi-tenant architecture, authentication and roles, billing, an admin dashboard, and the infrastructure to run it. From first version to paying customers.
REST APIs designed, documented and secured — plus integration of third-party services like payments, authentication, email and external data sources into your product.
Your application provisioned and deployed on AWS — networking, compute, storage and databases set up properly, with SSL, domains and environment separation handled.
Automated build, test and deploy pipelines so shipping an update is one merge instead of a manual afternoon. Includes rollback paths for when a release goes wrong.
Services packaged into Docker images and orchestrated on Kubernetes, so the application scales under load and behaves the same in every environment.
Dashboards and alerting so problems surface before your customers report them — plus ongoing bug fixes, feature work and infrastructure care after handover.
The stack I use day to day, across the application layer and the infrastructure underneath it.
Four steps, fixed scope, no surprise invoices. You always know what stage we’re at.
A free twenty-minute conversation about what you need, who it's for, and whether I'm the right person to build it.
A written breakdown of features, timeline and price before anything is built. If the scope changes later, we agree on it first.
Regular check-ins with a staging URL you can click through, so nothing is a surprise at the end.
Live on production infrastructure with monitoring in place, and continued support once it's running.
I work with React, Node and MongoDB on the application side, and Docker, Kubernetes, Terraform and AWS on the infrastructure side. If you need something built and actually running, that’s the job I take.
The things most people ask before starting a project. If yours isn’t here, just ask.
Web applications built on the MERN stack — React, Node.js, Express and MongoDB. Typically client portals, admin dashboards, storefronts, booking systems and internal business tools. I also take on the cloud side: deploying to AWS, setting up CI/CD pipelines, containerising with Docker and Kubernetes, and putting monitoring in place.
Most freelance developers hand over a repository and stop there, which leaves you to work out hosting, deployment and monitoring on your own. I do both halves — the application and the infrastructure it runs on. You get a deployed, monitored, running system rather than code you still need someone else to launch.
Fixed price, agreed before any work starts. After a free twenty-minute discovery call I send a written breakdown of scope, timeline and cost. If the scope changes later we agree the change first, so there are no surprise invoices. I do not bill hourly for defined projects.
It depends entirely on scope, so I give a specific timeline in the written quote rather than a generic estimate. A focused MVP is usually a few weeks; a larger application with integrations and custom infrastructure takes longer. You will have a staging URL to click through throughout, so progress is visible rather than something you take on trust.
Yes. Inheriting an existing codebase is common, whether the previous developer left, the project stalled, or it works locally but was never deployed. I will review what exists and tell you honestly whether it is better to continue with it or rebuild — including when continuing is the cheaper answer.
The application goes live on production infrastructure with monitoring and alerting configured, so problems surface before your customers report them. I stay available afterwards for bug fixes, new features and infrastructure maintenance. You are not handed a system and left alone with it.
Yes, entirely remotely, and with clients in any timezone. Communication is over email and scheduled calls, with regular written updates. I reply to enquiries within 24 hours, Monday to Saturday.
Tell me what you’re trying to build and roughly when you need it. If I’m not the right fit, I’ll say so.