#Build03 · Matrimony · Internal platform

Arranged marriage platform (Rishtabook)

Replaced a manual partner-tracking diaries with a structured database. Fewer errors, zero manual hassle.

Arranged marriage platform (Rishtabook) — screen 2

/week saved

more callbacks

hassle

Problem

Groom profiles, photos, and astrology details were tracked in physical diaries and bio-data PDFs read by hand. There was no searchable database, no compatibility scoring, and every match meant re-typing details from a PDF into a diary.

Solution

We replaced the diaries with a structured groom database, Cloudinary photo storage, and one-click PDF bio-data extraction. Astrology compatibility (guna milan) runs automatically through the Prokerala API, with a local fallback and caching so repeat matches are instant.

Process

We digitised the existing groom records first so nothing was lost, then added PDF extraction to cut manual entry. Astrology matching came last — live kundli matching via Prokerala, with a local Ashtakoot fallback and server-side cache to avoid repeat API calls on the same pair.

Technical details

How it's built.

What runs where, what it talks to, and what was handed over.

Stack

Next.js 14 (App Router)TypeScriptTailwind CSSlucide-reactreact-hot-toast

Integrations

Google Sheets API (service account) as the databaseCloudinary for photo storageProkerala API for kundli matching

Delivered

Searchable groom database (Google Sheets–backed)
PDF bio-data extraction
Photo upload via Cloudinary
Astrology compatibility scoring (Prokerala + local fallback)
Password-gated access, 72hr sessions

Architecture

How the pieces connect.

Groom bio-data (PDF or manual) is parsed and stored in Google Sheets, photos go to Cloudinary. DOB is converted to a nakshatra, then matched against the bride's profile via Prokerala (cached) or a local Ashtakoot fallback — the score shows against each groom in the list.