Matrimony, arranged the way your community already does it

The problem with a single national matrimony site

A general matrimonial service has one job that works against itself. To serve everybody it has to reduce every community's marriage customs to the same handful of dropdown fields — religion, caste, mother tongue, city — and then hand the family a search box.

But the questions that decide a match are rarely the ones in the dropdown. Whether two gotras can marry. Whether a sub-community considers a particular surname the same lineage. Which nearby districts count as "close to home" and which are a different world. Whether the family expects the first conversation to happen between the elders or between the two people. None of this fits a filter, and all of it decides the outcome.

So the family does the matching themselves. They scroll, discard, cross-check with relatives, and use the platform as a contact list rather than as a matchmaker.

What a community platform does instead

When a matrimony platform serves one community, the customs stop being filters and become the structure. Lineage rules can be enforced rather than displayed. The fields families actually ask about can be compulsory. Match ranking can weigh what that community weighs. The language of the interface can be the language spoken at home, and a profile can be read by a parent who does not use English.

It also changes who trusts it. Families join a matrimonial platform because someone they know recommended it — a relative, a community group, a temple committee. A platform with a community's own name on it can earn that recommendation. A national brand asking the same families to trust it cold usually cannot, however large it is.

What Match & Wed provides underneath

Building all of that once per community would mean rebuilding identity, moderation and safety every time, badly. Those are the parts where mistakes are expensive and where a small launch has the least experience. So they belong to the platform:

• Profile approval. Every profile is reviewed before it becomes visible, by the same standard on every community platform.
• Verification. One definition of what a verified profile means, and one honest account of its limits. See verification.
• Reporting and removal. The same route to report someone, and the same obligation to act on it, everywhere.
• Contact rules. Interest, acceptance and only then conversation — so nobody receives messages from someone they have not agreed to talk to.
• Wedding services. One marketplace serving every community platform, because the wedding itself is the same problem for all of them.

Indian matchmaking is not one market

"Indian matchmaking" describes hundreds of separate marriage markets that happen to share a map. A community in western Rajasthan and one in coastal Karnataka are not competing for the same matches, do not use the same vocabulary for the same relationships, and would not recognise each other's rules about who may marry whom.

Treating them as one market is what produces a search result full of profiles a family was never going to consider. Treating them as separate markets is the entire design of this platform — including the naming: each community's platform is named in its own language and its own idiom, not given a house suffix borrowed from another region.

Which communities are live