HIJAB Z.

Next.js and Supabase developer. I build the version that survives paying users, not the one that demos well: multi-tenant RLS that holds, Stripe webhooks that reconcile, TypeScript your next developer can read.

Most Next.js SaaS MVPs do not fail at launch. They fail three weeks later, when one customer can see another customer's data in Supabase, a Stripe charge goes through twice, or an AI feature starts making things up.

WHAT YOU GET

Your SaaS MVP, built on Next.js, Supabase and Stripe
Full-stack development end to end. Your authentication, subscription billing, dashboards and multi-tenant PostgreSQL with Row Level Security, ready for paying users on day one rather than a prototype you rebuild in three months.

Your Stripe subscription billing, done properly
Checkout, trials, webhooks with idempotency, customer portal, metered and per-seat pricing, dunning, proration, Stripe Connect for marketplaces. I have opinions about webhook idempotency and I am not sorry about them. This is where revenue quietly leaks when it gets rushed, and it is where most of my rescue work begins.

Your Next.js 15 and React web application
App Router, Server Components, server actions, edge functions, TypeScript throughout, Node.js services where the work belongs on a server. Deployed on Vercel. Lighthouse 90+, sub-second TTFB, SEO foundations that do not need redoing later.

Your APIs, designed and integrated
REST API design, webhook handling with retries and idempotency, third-party API integration, OpenAPI documentation, rate limiting, and error handling that fails loudly instead of silently at 2am.

Your database and multi-tenant architecture
PostgreSQL schema design, Supabase with Row Level Security, Prisma migrations, indexing and query tuning so your dashboards stay fast when the row count is no longer polite.

Your inherited codebase, audited and rescued
Cannot ship on what you were handed? You get an audit of authentication, billing and performance, then a stabilization plan in 7 days with the critical fixes ranked by what will hurt you first.

WHY CLIENTS COME BACK

3,600+ hours across 60+ Upwork projects, 100% Job Success, and not one contract that ended badly. That is not luck. It comes from scoping honestly before the contract starts, telling you about problems while they are still cheap, and shipping what I said I would ship on the day I said it.