EventusOS/About
A decade in Built with operators in nursing, LGBT+, and lifestyle charter

Built by operators, for operators. The operating system for events, born in the hardest place on earth to run one.

EventusOS grew up on themed charter cruises: 3,500+ guests, dozens of venues, schedules that change by the hour, communities that span years. If a platform works there, it works pretty much anywhere.

/01, WHY

Generic event apps don't understand events with loyal communities.

The big event-tech vendors were built for one-off conferences. Their products treat every event as anonymous, every guest as a name on a list, every sailing as if it were the first. The operators we admire, NurseCon, VACAYA, Bliss, run the same event year after year, with guests who come back for a decade.

Those operators were stuck building their compass in spreadsheets, paying for Wi-Fi packages they couldn't depend on, and watching Facebook groups try to do community work the tools weren't built for. EventusOS exists because they deserved better.

/02, HOW

Built for the hardest case, easy on everything else.

The hardest event environment we know is a themed charter cruise: 3,500+ guests, multiple venues, day-of changes, paid-event upsells, and communities that carry across sailings. We built EventusOS for that. Everything else (conferences, festivals, stadium series, expos) is a gentler version of the same problem on top of the same engine.

That's why it scales cleanly to a 50,000-person festival. We built it for the environment where it had to work, with operators who depended on it.

/03, WHAT

You own your guests. You own your revenue. You own your community.

EventusOS is white-labeled by default. The app carries your brand, the guest data is yours, and the revenue is yours. We don't get between you and your guests, and we don't take a cut of your ticket sales.

Our customers market their own brand. Most of their guests have never heard of us, and that's the way we like it.

Where we've been

Building this with operators who run it, every year.

2014–2018

The first sailings

We built the first version with one charter operator. We replaced their printed compass with a real-time mobile schedule, and learned that offline-first wasn't a nice-to-have, it was the whole product.

2019–2021

RezMagic, PassengerID, real payments

We integrated RezMagic so reservation lookup just works, and added PassengerID billing across Holland America, Royal Caribbean, and Celebrity. We launched the paid-events module, and one sailing earned $36K in the first 24 hours.

2022–2023

The community engine

Profiles, one-to-one chats, group chats, and event chats, built with operators serving every kind of community. Pronouns, ally settings, and discreet modes were designed with the operators who needed them most, not invented in a vacuum.

2024–2025

From CharterOS to EventusOS

What worked at sea worked on land. We rolled the same engine out to festivals, conferences, stadium series, and hospitality groups, and pulled the whole product together under EventusOS. One platform, two audiences.

2026

The OS for events

The platform is live with NurseCon at Sea, VACAYA, and Bliss Cruise, with land-event customers in onboarding. We're hard at work on the next chapter.

How we work

Six things we hold ourselves to, on every release.

Operator-first, not vendor-first

Every product decision answers to a real operator running a real event. We don't build features in a vacuum and go looking for users afterward.

Your brand, never ours

EventusOS is white-labeled by default. Your guests see your brand, your colors, and your app icon. Never our logo.

You own your data

Your guest data is yours. Export it any time, take it with you when you want. We never resell it, repackage it, or compete with you on it.

Built with affinity communities

Pronouns, ally settings, discreet modes, opt-in identity. Designed with the operators who serve those communities, never assumed for them.

Live in 48 hours, not 48 weeks

A branded app in the stores within two days of signing. Real onboarding, not a six-month implementation cycle dressed up as service.

The boring fundamentals, handled

GDPR-aware data handling. PCI scoped to Stripe. Role-based access. Audit logs. Multi-region failover. Independent security review on the roadmap. The unglamorous work, done well.

Want to work with us?

Whether you're an operator or an engineer, we'd love to hear from you.