Skip to content
Sign-in
Back to gallery

/ 05

Evora

SaaS platform · event planner

An event planner for companies and their clients: weddings, birthdays, parties. Guests and RSVP, budget, day plan, tasks, seating, gift list and photos — in one panel.

Role
Product / UX / UI / Built with AI
Tools
Next.js · React · TypeScript · Postgres (RLS) · Vercel
Year
2026
Reading
2 min

[ 01 ]

Challenge_

Event companies sell packages (weddings, birthdays), but planning with the client then happens across emails and spreadsheets. They needed one system for the company and its clients — with a hard guarantee that one company's data never reaches another.

Company dashboard

[ 02 ]

Overview_

Evora (working name Wedly) is SaaS for companies that sell event packages. The company manages events, packages and its team, while each client gets their own panel to plan the whole day.

  1. 01Guest replies as they come in: invitations, confirmations and declines.
  2. 02One link and a QR code to print on the invitations.
  3. 03The menu splits what guests see from what only the organisers see.
  4. 04Diet and allergy questions right in the form.

What's inside

  • 01

    RSVP with a QR code

    One link or code for every guest, no account needed.

  • 02

    Guests and seating

    A guest list grouped by household and table seating.

  • 03

    Budget

    Categories and payments in one place.

  • 04

    Overview, day plan and tasks

    A countdown to the event, a schedule with PDF export and tasks scheduled from the event date.

  • 05

    Menu, gifts and photos

    Menu and diets, a gift list, guest photos and a moodboard.

  • 06

    Operator panel

    Companies, plans, revenue and an access log; every company's data isolated in the database (Row Level Security) and verified by tests.

Guests

[ 03 ]

Process_

  1. 01Decision

    Three roles, three panels

    the platform operator, the company (events, packages, team) and the client (planning their day).

  2. 02Decision

    Data isolation in the database (Postgres Row Level Security, separate database roles for the app, guests and system) and tests that try to break it.

  3. 03Decision

    Client activation via an emailed link; an email queue in a separate worker with retries and visible delivery status.

  4. 04Decision

    The client panel revolves around the event date

    tasks are scheduled from it, and RSVP, guests, budget, seating and menu are modules to switch on.

[ 04 ]

Gallery_

  • 01 — Sign-in
  • 02 — Company dashboard
  • 03 — Event budget
  • 04 — Guests
  • 05 — RSVP with a QR code
  • 06 — Day plan
  • 07 — Tasks
  • 08 — Gift list

[ 05 ]

Outcome_

A work in progress: the foundation (companies, packages, activation, tasks), guests and RSVP and further planning modules are done. Screens come from the local build on test data.

Event budget

[ 06 ]

Details_

Tech & tools

  • Next.js 16, React 19, TypeScript
  • Postgres with RLS and separate database roles
  • an email queue worker
  • data-isolation tests

Work in progress — screens from the local build on test data.

Next project

Toolkit