✦ For every celebration
A page of its own for every guest, in one language or two. The wax seal breaks, the card rises, your music starts. Then it runs the rest of the evening: replies, seating, gifts, the day plan, the reminders.
Free up to 50 guests · No subscription · No card details to start
50
Guests free,
the whole product
2
Languages on one card,
right to left included
0
Passwords to
remember, ever
1
Flat fee, once,
never per guest
Three honest routes to an invitation you are proud of, and the last one is not a consolation prize. Pick whichever describes you.
Layout, background, stamp, wax seal. Five options each, and your event opens on a finished invitation before you have touched a canvas. Change your mind as often as you like: a pick only edits the part it owns.
A real editor in the browser. Scenes, your photographs, text on an arc, your colours and your fonts, an envelope and a seal you choose. What you see on the canvas is exactly what your guest gets.
Invite a designer to your event. They work on the invitation and leave the rest of it alone. When it is right, bank it as a template and use it again for the next celebration.
A primary and an optional secondary language on the same card, with full right-to-left support, set per event. Hebrew, Arabic, Afrikaans, whatever the family actually reads.
Guests do not get a form. They get an envelope. The seal breaks, the flap folds back, the card rises and the details settle in, with your music behind it.
One link per household, not one link for the whole world. It knows who they are, so the RSVP arrives with their names already on it.
Merge your list into personal messages and send them from your own number, with a proper link preview so the invitation shows its face in the chat.
Sent for you, with the wax seal inline. Every guest-directed message carries an unsubscribe link, and a confirmed unsubscribe is honoured everywhere.
For the guests who are never going to open a link on a phone. Same page, same reveal, reached from paper.
One tap adds the date, the time and the venue to whatever calendar the guest already uses.
You sign in with a magic link or a passkey. Your guests sign in with nothing at all: their link is the invitation.
Publishing is a real gate, not a flag. Until you publish, no invitation leaves the building by any route.
Per person, not per household, so you know that three of the four Cohens are coming and which one is not.
142
Coming
18
Declined
24
Not yet
Sample figures, for illustration
Plus allergies and access needs, in the guest's own words
Meal choice, dietary notes, a lift from the airport, whatever you need. The answers arrive summarised, so you hand one page to the caterer.
Automatic reminders go to the guests who have not replied, and only to them. Broadcast to everyone who is coming when the parking changes.
Set the deadline once and the form locks itself. You can still record a reply by hand for the aunt who telephoned.
Drag a guest to a table. A decline frees the seat on its own, and the cost report totals confirmed attendance rather than optimism.
Move a table to any position in the run and the plan redraws around it. Export the whole thing to a spreadsheet for the venue.
Most guests come for the whole night. A second crowd arrives later, for dessert and dancing. That is a different card, a different schedule, a different cost per head and no seating, all on one event: one bill, one set of hosts, one library of images.
Set a price per head and the report totals confirmed attendance, broken down by who invited whom. Agree a headcount with a co-host, and hand unused seats between yourselves.
Any store, no retailer lock-in. Quantities, claim and unclaim, and a quiet nudge when something is still needed.
Build the running order once, then put each person into their crews. The photographer gets the photographs, the wedding party gets the getting ready, and nobody scrolls past six hours of things that are not theirs. Try it:
An item with no crew belongs to everyone. That is the rule, not a default.
Everyone given an honour on the night gets their own link, carrying the event's own styling, sent by WhatsApp. For the honouree without a smartphone, a printable card in the same design.
Thank-yous to the people who came, in the same place the invitation already lives. Nothing to export, nothing to reconcile.
Bring in the people who are good at the parts you are not. Everyone sees the whole event, because two families organising one wedding are not tenants of a product. What differs is what each of them looks after.
Coordinator
A planner, or a very organised sibling, working alongside you on every part of the event rather than one corner of it.
Guests · Seating · Design · Day plan · Sending
Co-host
The other family. They add and manage their own households within a headcount you agree, and the cost report shows whose guests are whose.
Their households · An agreed headcount · Seat handover
Designer
For those of us who are not the creative type. Hand the invitation to someone with a better eye. They design; you keep the guest list.
The invitation · Images · Templates
JoynUs speaks the Model Context Protocol, so an AI assistant like Claude can drive it directly. Not a chatbot bolted to the side: the same capabilities the host portal has, exposed as tools.
Describe the wedding in a sentence. Watch the event, the theme, the scenes, the two languages and the music appear, then open it and change whatever you like by hand.
› Create a wedding invitation for Ariel and Maya, 7 June 2026, The Old Mill in Riverside. English and Hebrew, with music. Ask everyone for a meal choice, then import my guest list.
Done. 3 scenes, 2 languages, 71 links ready to send.
We take privacy seriously: no marketing, no data selling, word of mouth only. Guest email is optional, every guest-directed message carries an unsubscribe link, and guest data is purged when the event is. Read our data pledge →
The music on our sample invitation is by Aharon Berk, with thanks.