Pricing that scales with your faire

Just-budding and first-year faires. The goal is to lower the bar so a brand-new gathering can run a real digital companion without a budget conversation. After year one, you upgrade to Hamlet or above.

No. The Operations Suite stands on its own — many faires start with just Maps, Schedule, and the cast/vendor portals. The Quest Engine is added when you're ready to monetize stories.

Unique guests who activate the app on a given day, counted once per guest per day. That number is only used to size your tier (the caps above) and, if you opt into the ticket-price add-on, what that adds up to — your flat season fee doesn't change with the gate. Cast and vendors never count.

No. Cast members and vendors create their own pages and associate themselves with the faires they're working — operators don't pay per seat. Operators approve associations and own the data, but the accounts themselves are self-serve and free.

The schema and design system are open. The runtime is proprietary but tenant-portable — if you ever leave, your data goes with you in canonical export form.

The same engine powers them; the labels are tenant-configurable. Cast → Speakers, Faction → Track, Quest → Workshop. Same data model, different skin.