About InviteHarbour
Why we built this.
In South Africa, one event is rarely one event. A wedding might mean a white wedding and a traditional ceremony, days or venues apart. A 21st or an umemulo pulls in family from everywhere. And every one of them runs on the same scattered mess: WhatsApp forwards, paper programmes, and a host repeating themselves all week. We built InviteHarbour to fix that.
The problem
Before an invite page, hosting an event in South Africa usually looks like this:
- Directions get forwarded as a pin or a voice note, and get lost the moment there's more than one venue.
- RSVPs trickle in across calls, texts and group chats, so there's never a reliable headcount for catering.
- A printed programme is out of date the moment the event runs late — which it almost always does.
- Guest photos end up scattered across dozens of phones instead of in one place everyone can see.
- Any change — a new time, a change of venue — means re-sending the same message to every guest, one more time.
- Guests who never got the forwarded message, or lost it in the chat, arrive not knowing where to go.
What InviteHarbour does
InviteHarbour turns all of that into one link. Send it once, and it carries everything — the invite, directions to every venue, RSVP, the live programme and photos — automatically up to date, on any guest's phone, with nothing to download.
- Every venue gets its own map and one-tap directions, so white wedding and traditional ceremony are never confused.
- Guests RSVP with a headcount and meal preference, so you see real numbers as they come in.
- A live, MC-driven programme updates on every guest's phone the moment things change — no reprinting, no timer, just the MC tapping Next.
- A photo gallery and a live guest photo wall keep every picture in one place, long after the event ends.
- A QR code at the venue catches walk-in guests who never got the link.
- One link to update, instead of one message to every guest, every time something changes.
Built for how events actually run here
We're not adapting a template built for another market. InviteHarbour is built around how South African events actually happen — multiple ceremonies, extended family, events that run on their own time, and guests who need things in plain language on a phone that might not have much data. Weddings, umembeso and lobola, umemulo, galas, launches, conferences, funerals and memorials, birthdays — every one gets a page that fits the occasion, not a copy-pasted form.
Privacy, built in
Guest information — RSVPs, phone numbers, meal preferences — is only ever visible to the host, never published on the page itself, and deleted on a schedule after the event. It's handled under POPIA from the ground up, not bolted on afterwards. Read the full privacy policy.
Planning something and tired of repeating yourself to every guest?