Orkesta
A multi-tenant SaaS for digital event invitations, guest management and live check-in — designed, built and shipped end to end, and running in production.
Hosting an event means juggling three things at once: a spreadsheet of guests, a chat thread full of “did you RSVP?”, and a notebook for the seating chart. The day of the event, none of it helps you at the door. Orkesta turns that whole mess into one platform — digital invitations, guest management and live check-in — and it’s live in production at orkesta.com.mx.
The problem
Event organizers don’t have a software problem in their heads — they have a coordination problem. Who’s coming? Plus-ones? Kids? Who’s at table 6? Who actually walked in? Every one of those questions usually lives in a different tool, and they all fall apart the moment the event starts and a real human is standing at the entrance with a phone and a guest list.
Orkesta’s job is to make all of that one continuous flow — from the moment an invitation goes out to the moment a guest is checked in at the door.
What it does
Invitations & RSVP. An organizer designs a digital invitation and shares it as a link — over their own WhatsApp or any channel they like. Guests RSVP through a smart flow with validation, and the guest list updates itself in real time: confirmed, declined, still pending, adults vs. kids.
Seating. Tables are planned with capacity in mind, so the seating chart stays honest against who’s actually coming instead of drifting out of sync.
The door. This is where most tools quit. Orkesta has a companion check-in experience: hostess devices are registered and assigned to a specific event, and staff check guests in live, with real-time stats — total confirmed, kids and adults, and how many have actually arrived.
Wallet passes. Guests can add their event pass straight to Apple Wallet and Google Wallet, generated on demand.
The organizer’s cockpit & admin. Organizers manage their events, guests, tables and templates from their own dashboard, while a platform admin oversees organizers, plans and operations from a separate one.
Under the hood
Orkesta is a real multi-tenant SaaS, not a single-event site — and that’s the part that matters technically.
Roles enforced on the server. There are four kinds of actor — platform admin, organizer, check-in staff and guest — and each only ever sees what their role allows. Those rules live in the API behind role guards, not just in the UI, with a dedicated auth context even for guests so an invitation link can’t be turned into access it shouldn’t have.
A serious data model. 28 data models across 30 feature modules — events, guests, tables, check-ins, hostess devices and assignments, plans, top-ups, audit logs, support tickets and more — all typed end to end with Prisma over PostgreSQL.
Built to not fall over. Heavy and slow work runs off the request path on Redis-backed queues — reports, notifications and housekeeping happen in the background. Auth uses JWT access + refresh tokens, and the surface is hardened with Helmet, rate limiting, structured logging and health checks.
Fast front end. The client is server-rendered Angular, so the public invitation loads fast on a phone — which is exactly where guests open it.
The stack
- Frontend — Angular 19 with server-side rendering, Angular Material + CDK, RxJS; QR codes and calendar (ICS) generation.
- Backend — NestJS 11 in strict TypeScript, REST API documented with Swagger / OpenAPI.
- Data — PostgreSQL with Prisma ORM; Redis for caching and Bull job queues.
- Auth & security — JWT access/refresh with Passport, role-based access control, Helmet, rate limiting, bcrypt.
- Integrations — Apple Wallet (PassKit) & Google Wallet passes, Resend for transactional email.
- Ops — Docker, structured logging (Winston), health checks; deployed on Railway.
Worth noting
Orkesta was designed, built and shipped end to end by one engineer — frontend, backend, database, security, infrastructure and deployment — and it runs in production on its own domain (orkesta.com.mx), today. Payments are handled manually for now (Stripe is the next step), which is a deliberate call: ship the product that creates value first, automate the billing once there are customers to bill.
If you want to see what owning a full product looks like — not a demo, a live SaaS — this is it.
Coffee & talk?
Like what you just read? I build products like this end to end — and I'm always up for a conversation. Let's talk about yours, or just trade notes over coffee.