Gate & visitors
Expected guests, delivery flows, cab entries, gate passes that work offline, and an auditable log the committee actually reads.
A community platform, built in India
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.
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.
The flagship loop
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.
STEP 01 · GUARD TABLET
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
STEP 02 · RESIDENT PHONE
One screen, two buttons, no app tour. Any adult in the household can answer.
VISITOR AT GATE 1
Ramesh K.
Delivery · waiting
STEP 03 · 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.
Expected guests, delivery flows, cab entries, gate passes that work offline, and an auditable log the committee actually reads.
Owners and tenants as equal residents, one account across several homes, and a clean handover when a flat changes hands.
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.
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
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.
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.