The platform · 05
Your event’s own site — wearing your invitation.
Not a template with your names dropped into it. Your event site is dressed from the invitation you approved — that artwork at the top of the page, and its colour and its lettering carried through the rest — so a guest who received the invitation recognizes the page the moment it opens. Private, and reachable only by the people you invited.
What your guests find there.
The evening, arranged
Date, place, timings and the run of the day. What to wear, when to arrive, where the ceremony ends and the dinner begins.
Getting there and staying
Directions, parking, transport, and the hotels and room blocks you recommend — where your out-of-town guests sleep, answered once instead of one text at a time for six weeks.
Their own reply
The same private link as their RSVP card. They answer, change their mind, or add a plus-one’s name without leaving the page.
Anything else you add
A registry section with claimable items, a note about children, the playlist request, the dietary form. You decide what appears; nothing is mandatory.
It is dressed from your invitation, automatically.
This is the part that is hard to do any other way. The moment you approve your invitation, the site is dressed from that file itself: the invitation is what a guest sees first on the page, and the colour and the heading lettering read off it are carried through the rest. The page is our own layout wearing your design, not a redrawing of your whole suite — and that is what a guest recognizes.
That continuity is the whole argument for one connected system. A separate wedding-website service cannot do it, because it has never seen your invitation.
The site is private. It is reachable by the guests you invited and can be closed to everyone else, so an event address is not something a stranger stumbles onto.
It reads from the same guest list and the same replies as everything else. A change made once is a change made everywhere — there is no second copy of your event to keep in step.
The design your site is dressed from.
These are printed pieces, not screenshots — they are shown because the approved invitation among them is what the site is dressed from. Your event website carries that invitation, and takes its colour and its heading lettering from the same file.
One delivered event — the direction the event site is built from
Worth saying plainly.
The website is built by Evorrah, not assembled by you.
Most hosts expect to pay a second company for an event website, and a good number of them have already done so by the time they find this page. Here it comes with Whole Event and Fully Handled, and is a $99 add-on on Essentials — once per event, added from your portal. Either way it is the same guest list, the same replies, and the same approved invitation on the page.
One event, one address, one truth.
When the ceremony time moves, it moves on the site, in the reminders, and on the timeline at the same moment. Nothing has to be updated in a second place, which is where wrong information reaches guests from.
As delivered.
The event website as a guest found it, on four delivered events — a brand launch, a wedding, a corporate anniversary and a baptism.
Rendered from the file each event ran as — its own guests, dates and colour. Open any one to see it full size.
What it will not do.
An event website is a private address for private people. These are standing rules, not settings.
- Be found by a stranger — it is reachable by the guests you invited
- Wear a template — it inherits the direction you approved
- Keep a second copy of your event — the schedule, the replies and the counts are read from the one record
- Ask a guest to log in
- Show a guest anything but their own reply
One event, one address, one truth. When the ceremony time moves, it moves here at the same moment it moves everywhere else.
The rest of the platform
Three more services,
reading from the same event.
Reminders & Chasing
Late replies followed up for you, counted back from the deadline, only to the guests who have not answered or left something out.
Explore → 07Seating & Tables
The seating plan builds itself from the replies, and re-resolves when someone declines.
Explore → 08Timeline & Deadlines
What is due next, always. Every milestone counted back from your date.
Explore →