Naman Puja: the first version of a live booking platform

namanpuja.com lets families book Vedic pujas at home or online, and serves six countries. In June 2026 I built the first version in about two weeks: the booking API, a Next.js storefront, an admin console, and a bridge that copies every booking into the sales team’s CRM. A teammate has since rewritten and extended a lot of it. The booking flow, admin API and CRM sync I wrote are still in production.

Role: Built v1 of the backend, storefront and admin
Year: 2026
Built with: TypeScript, Node.js, Express, Zod, Prisma, Next.js 14, react-admin, Supabase, Vercel

Visit namanpuja.com

6countries the live site serves

66cities in production data

~2 weeksfrom first commit to v1

The namanpuja.com home page with a Navratri puja banner and booking buttons. — namanpuja.com today. The current front end is my teammate’s rebuild.

What v1 connected

StorefrontNext.js pages for each puja and city.
Booking APIValidated request, readable reference like NP-2026-000123.
Adminreact-admin console over a JWT-protected API.
CRMEach booking mirrored as a contact and a deal.

The CRM sync is isolated. If the CRM is down, the customer’s booking still goes through.

What I built

An Express and TypeScript API with a Zod-validated booking endpoint and human-readable booking references.
An admin API generated from a single CRUD router factory, shaped to what react-admin expects.
The country, city and puja data model, and a generator that seeded 72 puja-by-city landing pages.
A Next.js 14 storefront with statically generated pages, per-page metadata and structured data.
The booking-to-CRM bridge, the Docker Compose development stack and the onboarding docs the team started from.

What came after

A teammate later moved persistence to MongoDB, added payments, image hosting, blogs and the sitemap, and rebuilt the front end. I wrote 12 of the backend’s 65 commits: the v1 architecture.