event67
Open menu

The app for a multi-day wedding weekend

A destination wedding is not one event. It is six events across four days in a place none of the guests know, and it is run by two people who are also getting married that week.

1,000
a 130-guest wedding weekendOne dot ≈ 8 attendees

A planning figure for a destination wedding where most guests travel and stay several nights.

Six events, four days, one unfamiliar place

A wedding weekend app carries the full run of a multi-day celebration: the welcome dinner, the ceremony, the reception, the day-after brunch, each with its time, venue and dress code. event67 adds a guest directory, push updates when plans change, and one shared album for everybody's photographs. It is a gathering app, not a wedding planning platform: no registry, no seating chart, no RSVP-with-meal-choice and no payments.

Six events, and a guest who only knows about two

The welcome drinks, the rehearsal dinner, the ceremony, the reception, the brunch, the pool afternoon. Each with a different venue, a different start time and a different dress code, and half of them only apply to some guests. A filterable schedule where each guest stars what they are attending solves a problem that is currently solved by four group chats.

Guests who have never met

Two families and three friendship groups, most of whom will spend four days together. A directory with photographs and a short profile turns the first evening from name-badge awkwardness into recognition, and QR connections keep the contacts afterwards.

Plans that move, in a place with poor signage

The boat is delayed, the dinner moves indoors, the coach leaves twenty minutes earlier. A push announcement that deep-links to the affected event reaches everyone at once, which is the one thing a group chat does badly at a hundred and thirty people.

Every photograph in one place

A wedding produces thousands of guest photographs that the couple never see. The shared album collects them under the event with a full-screen viewer, and the couple gets them in the week after rather than in a trickle over a year.

The weekend, event by event

  1. Save the date

    Invite from the guest list

    Import the guest list as CSV and send invites themed to the wedding. Delivery is tracked per recipient, which on a list assembled from two families is worth having.

    Uses the themed app and branded invites with delivery tracking.

  2. The month before

    Publish the weekend

    Every event with its time, venue, dress code and who it is for. Guests star what applies to them. Optional activities with limited places use server-enforced capacity with automatic waitlist promotion.

    Uses the weekend schedule.

  3. Arrival day

    Welcome, and who else is here

    Open the directory as guests arrive so people can find each other before the first dinner. Check-in is available where a coach or an excursion needs a headcount.

    Uses the guest directory.

  4. Through the weekend

    One channel for changes

    The coach time, the weather call, the location of the after-party. Push announcements deep-link to the post, which is far more reliable than a message in a chat nobody has muted yet.

    Uses push announcements.

  5. The week after

    The album

    Everyone's photographs in one viewer, moderated at whatever level the couple wants. This is usually the feature guests mention, and it is the reason the app keeps being opened after the weekend ends.

    Uses the shared album.

Setting up a wedding weekend

Four steps, done in an evening, ideally a month before anybody travels.

  1. Create the event across the whole weekend

    Thursday to Sunday, so the schedule reads as one weekend rather than four days.

  2. Enter every event with venue and dress code

    Including the ones only some guests attend. Guests star what applies to them.

  3. Import the guest list and invite

    One CSV, invites themed to the wedding, delivery tracked so nobody is missed.

  4. Open the album on arrival day

    Set it open rather than moderated. A reported photo auto-hides, which is the safeguard that makes open safe.

What a 130-guest wedding weekend costs

A hundred and thirty guests activate. Fifty are free and the remaining eighty are billable once for the whole weekend, however many events each guest attends.

activated attendees
130activated attendees
billable, after the first 50 are free
80billable, after the first 50 are free
for the whole event, at $5.00 each
$400for the whole event, at $5.00 each

A wedding of fifty or fewer guests costs nothing at all. Guests who cannot travel never activate and never appear on the bill.

This is not a wedding planning platform

event67 is built for business gatherings and it shows in what is missing. A couple choosing this should choose it for the weekend logistics, not for planning the wedding.

  • No registry, gift list or contributions.
  • No RSVP with meal choice or dietary collection. Forms collect responses, but they do not attach to a guest record as an RSVP.
  • No seating chart or table planner.
  • No accommodation or travel booking.
  • No payments of any kind.
  • No vendor or supplier management.
  • No wedding website in the usual sense. The event site exists and is not indexed by search engines, which is a privacy feature rather than a marketing one.

Last updated

What it costs

Free up to 50
activated attendees, on one live event
$5
per activated attendee beyond 50
$4,750
the most one event can ever cost, whatever happens past 1,000

Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.

See the full pricing

Questions people actually ask

Is this a wedding planning tool?

No. There is no registry, no seating chart, no RSVP with meal choices and no payments. event67 is built for business gatherings, and what it does well for a wedding is the multi-day logistics: the schedule, the directory, the announcements and the album. Keep your planning tool for the rest.

Can guests RSVP through the app?

Not in the way a wedding usually means. Guests can star which events they are attending, and forms can collect responses, but there is no RSVP record attached to a guest with a meal choice. Collect formal RSVPs however you already do and import the confirmed list.

Who can see the wedding?

Only guests you invite. The event site is not indexed by search engines and there is no public listing anywhere. That privacy is the default rather than a setting to find.

Will older guests use it?

Some will not, so the weekend should never depend on it. There is a web version for anyone who will not install an app, and the printed schedule card in the welcome bag is still worth doing. The album is the feature that brings sceptics back.

Can we brand it to the wedding?

Yes. Colours, typography and a logo or monogram flow through every screen. The contrast checker warns if a palette pair falls below WCAG AA and confirms before saving; it never blocks the save, so the design decision stays yours.

Four days, six events, one schedule

Every guest sees what applies to them, hears when it changes, and adds to one album. Free up to fifty guests.