Backends that held up once real users arrived.

Healthcare, real estate, fundraising and consumer apps. Most of it is backend and infrastructure work, some of it end to end.

aa.healthHealthcare

aa.health HIPAA-Ready Backend

The product needed backend foundations that could handle sensitive patient data without creating fragile, one-off compliance workarounds.

Moved the product from architecture planning to production-grade healthcare backend foundations.

Python · PostgreSQL · Cloudflare · API security

HudproReal estate

Hudpro Real Estate Application Backend

Real estate products need the frontend, API layer, and database model to agree on inventory state, permissions, and search behavior before the dataset and workflows grow.

Gave the product a serverless application foundation for inventory browsing, workflow state, and production iteration.

Next.js · Python · AWS Lambda · DynamoDB · API design · Application architecture

WhydonateFundraising platform

Donation platforms have uneven traffic: quiet periods, sudden campaign spikes, payment-adjacent workflows, file and media storage needs, queue-backed background work, and search queries competing for backend capacity.

Kept fundraising workflows stable at 4M+ API requests/day.

Cloudflare Workers · TypeScript · Cloudflare Pages · Cloudflare R2 · Cloudflare Queues · PlanetScale · MySQL · Typesense

WakamiappConsumer app

Wakamiapp End-to-End Backend Platform

Wakamiapp needed more than isolated endpoints. The product required a backend foundation that could support user accounts, product workflows, data consistency, secure access, and future feature growth without forcing a rewrite after launch.

Turned the product backend from a build requirement into a maintainable platform layer that could support real user workflows and future product expansion.

Backend architecture · API design · Database design · Authentication · Cloud deployment

Also availableOutside the 14-day build

Cloudflare Workers Backends: Workers for the request paths that should be close to users: webhooks, proxies, auth checks, cacheable reads, and small APIs that do not need a full regional service.
AWS Cost & Architecture Review: A practical look at Lambda, API Gateway, containers, OpenSearch, databases, logs, and traffic flow to find what is expensive for a real reason and what is just drift.
Full-Stack Application Backends: Complete application delivery where the backend carries the product: Next.js surfaces, APIs, auth, databases, queues, search, deployment, and clear handoff notes.
Cloudflare + AWS Migration Planning: Small migrations with rollback paths. Move the edge-shaped parts to Cloudflare and leave the heavy regional work where it still belongs.
Architecture Audits: A clear read on what is actually slowing the product down: queries, service boundaries, deployment habits, cloud cost, or decisions made in the MVP rush.

What clients saidAll reviews

“Ashish delivered exceptional work on a highly technical Cloudflare/Workers project. His communication was excellent throughout.”

Cloudflare Edge Architecture

“Ashish is a fantastic dev. Very hardworking and was always able to come up with solutions for my project.”

Cloudflare Worker + Supabase Integration

“I'd love to work with Ashish again. He really writes clean, great code.”

ASN1/DER Parsing on Cloudflare Edge

“Was great working with him. He made everything work and went above and beyond.”

Custom Webhook with Reverse Proxy

Have a similar backend problem?

Share the bottleneck and the outcome you need. I'll suggest the cleanest next step, even if it isn't hiring me.

Book a 20-minute call Or write a brief