The challenge
Small event hosts tend to run on separate tools: one for a profile page, one for tickets, one for payments and something else for promotion. Each works on its own, but together they look fragmented to guests and leave the host doing the joining-up by hand. Evntt starts from a different idea: you don’t need to be a big organisation to host events that look professional.
That set the brief: give any creator a branded presence plus the operational basics of hosting, and give guests one place to find events from hosts they trust. Because the product is two-sided, both groups read and write the same records. Hosts need dashboards, editing tools and payments that reach them; guests need quick discovery and a booking path that doesn’t make them think. The data model had to serve both from day one.
- Branded host profiles that hosts can customise themselves, without a designer
- Ticketing and booking in the same place guests discover the event
- Promotion that works the moment an event is published
- Merchandise, galleries and simple analytics in the host’s own account, not in extra apps
What I built
I designed and built Evntt end to end: React with TypeScript and Tailwind CSS on the front end, Node.js on the back end, PostgreSQL for data, Stripe for billing and AWS for hosting. It is a deliberately conventional stack. A young platform gains more from code any competent engineer can pick up than from novelty, and every part of it is proven in production elsewhere.
The profile editor works with live preview. Hosts change their branding and see the result as they work, rather than saving, refreshing and guessing. For a non-technical host, that is the difference between a page they are happy to share and one they give up on. What the host sees while editing is what guests see when they arrive.
PostgreSQL suits the shape of the product. Hosts own events, events carry tickets and guests book against them, so the relationships are the heart of the data. A relational model keeps those links explicit and consistent, which matters most where money changes hands.
Payments run through Stripe billing. Keeping card handling with a specialist provider, and out of Evntt’s own infrastructure, reduces the security and compliance load on a young platform and lets the product focus on the host experience.
Promotion is built in rather than left to the host. Every event gets a QR code and share links, so a host can publish and start promoting straight away. Event dashboards, lightweight analytics, merchandise and galleries sit in the same account, so a host’s whole event business lives in one place.
Hosting on AWS gives the platform room to grow. Events traffic is uneven, quiet for a while and then busy when a popular host announces something, and cloud hosting lets capacity follow demand rather than being bought for the peak.
Architecture and stack
- Front end
- React · TypeScript · Tailwind CSS
- Back end & data
- Node.js · PostgreSQL
- Payments
- Stripe
- Hosting
- AWS
Outcome
Evntt gives small hosts the kind of presence that used to take a designer and several separate tools: a branded profile, ticketing, billing, promotion and reporting in one product. Guests get one place to discover events from hosts they trust and book them.
For the business, one codebase and one data model across both sides means a new feature reaches hosts and guests together, instead of being patched between third-party tools. The stack is standard enough that the platform can be handed to another team or grown in-house without a rewrite.
- One product in place of separate profile, ticketing, payment and promotion tools
- Branding hosts control themselves, with a live preview
- Instant promotion through QR codes and share links
- Card payments handled by Stripe, outside Evntt’s own infrastructure
Last updated 2026-10-03