Neema Mushi
& Baraka Mushi
Issue QR invitations, assign ushers and admit every guest with a single scan, backed by a database rule that makes sure no card is ever used twice.
& Baraka Mushi
Illustrative example · Main Gate
Scan next guestSaturday 24 October 2026
DOUBLE · HY-EXAMPLEEvery card carries a random token, never a name or phone number. Revoke a compromised card and issue a fresh code in one click.
One check-in consumes the whole invitation. The database accepts entry once; simultaneous scans cannot both win.
Choose strict mode for server-confirmed admissions, or managed offline with queued sync and clear conflict review.
Each planner gets an isolated workspace. Guest lists, staff and reports never cross between organizations.
Assign each usher to an event and entrance, approve their phone, and revoke a lost device from the dashboard.
Invitations, check-ins and guests admitted are counted separately, so the numbers always mean what they say.
Couple, date, venue, entrances and offline policy.
Add guests by hand or import a CSV. Duplicates are flagged, never merged.
Design the invitation once; every guest gets their own QR.
Ushers see a green, red or amber result they can read at arm’s length.
Disconnected devices can accept the same card in managed mode. Use strict mode when every entry must be verified with the server.
14 days to try the full flow
per wedding, billed once
per month
Prices, limits and enabled features are set by the platform owner for each plan.