Beyond a wedding website.
Most wedding websites are a page. What Astelia builds is a private guest management system with a considered front door — running on the family’s own guest list rather than holding it. This is the full account of what that means.
What this actually is
A typical wedding website — a free platform, or a paid subscription — is a page with a form on it. A guest fills out an RSVP, it lands in an inbox or an exported spreadsheet, and from there someone, usually the couple and sometimes the planner, manually reconciles it against whatever guest list already exists elsewhere. The website and the guest list are two different things that have to be kept in sync by hand.
What Astelia builds is different in kind, not just in polish: the website and the guest list are the same system. There is one live record — the actual working guest list, the one used for seating, catering counts, and day-of logistics — and the website reads from it and writes back to it directly, in real time, with no manual step in between. When a guest responds, that is not a message someone has to go transcribe. It is already there, already correct, the moment they submit it.
Everything else — the personalized schedules, the guest-code privacy model, the automated notifications — is built on top of that one fact: there is a single source of truth, and both the guest and the people planning the wedding are always looking at the same, current information.
How it works, in practice
A private code, not a public link.
Each invited household receives its own unique code — not a shareable link anyone could forward, not a generic form open to the internet. Entering it reveals only that household’s own information: their names, their RSVP status, their own party’s details. No guest ever sees anyone else’s.
A page that is different for every guest.
A member of the wedding party sees their photo-shoot arrival time and slot. A general guest sees the ceremony details relevant to everyone. A family driving in from out of town sees lodging information. The system knows who is logging in and tailors the page accordingly — automatically, from data already in the guest list, not from a second system someone has to maintain.
RSVPs that write straight back to the real guest list.
A guest’s response — attending or not, headcount, dietary notes, a mobile number with proper consent — is written directly into the same guest-list record the planner and caterer will ultimately work from. There is no export, no copy-paste, no updating the spreadsheet from a stack of RSVP cards.
Headcounts and dietary needs that are always current.
Because every response lands in one place immediately, how many are we at and who needs a vegetarian plate are always answerable on the spot — not a count that has to be manually tallied from a stack of replies the week before the wedding.
A guarded process for lost invitations.
A guest who cannot find their code submits a short recovery request — but the system deliberately never confirms or denies who is or isn’t on the guest list through that form. It queues the request for a real person to review and reply to individually. That is a genuine privacy protection, not a convenience shortcut, and it means the guest list itself can never be probed or guessed at by a stranger.
A design that is actually theirs.
The palette, the typography, the tone of every sentence on the site is built around one family specifically — not selected from a dropdown of stock themes. The site looks and reads like their wedding, because it was designed for their wedding.
How this elevates the guest experience
For a wedding at this level, the guest experience is judged the same way every other detail is — by whether it feels considered, personal, and unhurried. This system was built to meet that bar digitally, not just on the day itself.
It feels personally considered, because it is.
A guest who logs in doesn’t wade through a generic itinerary looking for what applies to them — they see exactly their own schedule, their own arrival time, their own party’s status. That is the same instinct behind a hand-addressed invitation or a seating chart done by name, applied to the one part of the wedding that is usually the most impersonal: the website.
It is private by design, not by accident.
An invitation-gated, code-based site with no public RSVP form reinforces exactly the feeling an intimate, curated guest list is supposed to convey — that this was thought through, not thrown together on a template everyone else’s wedding also uses.
It removes friction instead of adding it.
The RSVP form arrives pre-filled with what’s already known, is easy to revisit and change, and says so warmly — plans change, come back any time — rather than treating a guest’s response as a one-shot transaction. That tone, carried consistently through every page, is doing real work: it’s the same warmth a guest would expect from the wedding itself.
It looks like nothing else the guest has seen.
Every other wedding website a guest has visited this year almost certainly came from the same handful of free platforms and looks like it. This one doesn’t — because it wasn’t built from one.
How this makes a planner’s job easier
Every benefit above is visible to a guest. This section is the one that matters most to a planner, because it addresses the part of the job that never shows up in a mood board: the operational grind of keeping a guest list accurate across months of changing answers, competing spreadsheets, and last-minute questions.
Put simply: the parts of a planner’s job that are invisible to the couple but consume real hours — reconciling data, chasing updates, fielding the same question from forty different guests — are the parts this system was built to absorb. A planner working with a family on this system isn’t handed a prettier website.
She’s handed a guest list that keeps itself current.
Why this isn’t just a nicer wedding website
On most event platforms the page exists for as long as the account does, and the guest data it gathers lives wherever that platform decides to put it. An Astelia family holds something different, and it is worth being exact about what. The domain is registered in their name from the first day. The guest list is their own spreadsheet, in their hands throughout — it is never inside our system; ours reads from theirs. What stays with Astelia is the connective work between the two: the live record that keeps the site and the list the same thing. That is what we build, maintain, and are answerable for.
So a family is never locked in, and never left holding something they cannot run. A site can be handed over at the end as a standing record of the occasion, without the live connections behind it, and the domain and the list go with them regardless. Because the address and the list persist, what comes next — an anniversary, a christening, a reunion of the same hundred people — begins from something rather than from nothing. That is the premise: infrastructure a family keeps, elevated for the people living it, and quietly, materially easier for the planner running it.
Two engagements, one system underneath.
The Foundation Suite is the semi-custom path. The Bespoke Commission is the fully custom path. Both run on the infrastructure described above.