Event services marketplace
EventOS
An event-services marketplace and operations platform for finding suppliers, comparing quotes, managing bookings and contracts, tracking payments and coordinating event delivery.
Product work and architecture overview by Savi Saluwadana.
What it does
- Who it serves
- Guests, event buyers, suppliers and administrators.
- Product purpose
- Quick provider matching and full event procurement.
- Service requests, supplier profiles and quote comparison.
- Bookings, contracts and event execution workflows.
- Manual payment submission and administrative reconciliation.
- PostgreSQL sessions, row-level authorization and persistent uploads.
How it works
- A guest requests a provider or a buyer defines an event and service requirements.
- Suppliers submit quotes; the buyer compares and accepts an offer.
- Database transactions coordinate booking, contract and commercial state.
- Authorized users share files and track execution; administrators reconcile submitted payment records.
Architecture
Next.js → PostgreSQL → transactional workflows + file storage
| Component | Responsibility |
|---|---|
| Next.js | Public marketplace and buyer, supplier and admin workflows. |
| Database adapter | Authenticated requests and domain transactions. |
| PostgreSQL | Sessions, row-level authorization, functions and lifecycle state. |
| File adapter | Public supplier assets and access-controlled event documents. |
Current scope
Payments are submitted and reconciled manually in the current MVP. This is a Next.js and PostgreSQL application; a Supabase service is not required for the documented runtime.
Architecture summary reviewed . The repository is private; this page provides a public product summary.