Parisar

A community platform, built in India

The society runs itself. Quietly.

Parisar handles the gate, the households, the staff register, safety, notices and billing for a residential society — and it does it without ever turning your residents into an audience. Your society pays a subscription. That fee is our entire business.

Bring Parisar to your society See the 3-second gate

One business model, stated plainly

A society pays a transparent per-home subscription. There is no second business underneath it — nothing that earns money from residents' attention, movements or contact details.

This matters because a resident cannot switch societies over a bad app. A captive audience is easy to monetise, and in this category it usually is. We built the refusal into the architecture instead of into a policy paragraph.

  • No advertising. There is no ad surface in the product, and no code path that could serve one.
  • No data brokering. Resident data is not sold, rented, or shared with a partner for marketing.
  • No engagement mechanics. No streaks, no feeds designed to be sticky, no notification sent to win a session.
  • You can leave. Export everything and delete your account in one tap — no committee approval, no waiting period.

The flagship loop

A visitor at the gate, answered in three seconds

No phone call, no shouting over a bad line, no guard guessing. The guard raises the visitor, the resident answers on a card, the guard sees the answer. Offline included.

  1. STEP 01 · GUARD TABLET

    The guard raises the visitor

    Name, purpose, flat. Two taps on a cheap tablet, one-handed, at night.

    GATE 1 · 21:14

    Ramesh K. — delivery

    To B-704 · Sharma household

    Ask resident
  2. STEP 02 · RESIDENT PHONE

    The resident answers a card

    One screen, two buttons, no app tour. Any adult in the household can answer.

    VISITOR AT GATE 1

    Ramesh K.

    Delivery · waiting

    Allow
    Deny
  3. STEP 03 · GATE

    The answer lands at the gate

    Recorded once, in the visitor log the committee can audit. Nothing else is inferred from it.

    ANSWERED · 2.4s

    Allowed by B-704

    Pass valid until 22:14

When the internet is down, the tablet still verifies a visitor pass cryptographically and queues the events until the connection returns. A gate that stops working is not a gate.

Four areas, one system of record

Gate & visitors

Expected guests, delivery flows, cab entries, gate passes that work offline, and an auditable log the committee actually reads.

Households & residents

Owners and tenants as equal residents, one account across several homes, and a clean handover when a flat changes hands.

Staff & safety

A staff register without biometrics or ratings, SOS that reaches the right people first, and a fire-alarm path that does not depend on someone's phone being unmuted.

Notices & billing

Maintenance invoices, receipts and dues on one ledger; notices with a declared priority so a lift outage and a yoga class never arrive the same way.

Quiet by design

Every notification has a ceiling

Each message type declares how loudly it may ever reach a resident. Quiet hours are enforced by the platform, not by each feature remembering to be polite — and nothing can escalate itself to win your attention, because that path does not exist in the code.

Illustrative — final ceilings are set in the platform, not per society
Message Ceiling
Fire alarmFull alert, overrides quiet hours
Visitor at gateRing once, then silent
Maintenance dueSilent, in-app only
Community noticeDigest, never at night

Start with one gate and one building

A pilot runs on a single gate for six weeks. If the committee is not convinced, nothing carries over and your data leaves with you.

Talk to us Already have an app?