FAQ
Questions event teams ask before they switch systems.
These answers follow the product model in Eventberry: self-serve setup, event-first scope, launch-triggered billing, and operational depth across public, attendee, and onsite surfaces.
FAQ section
Product model
Answers anchored in the Eventberry product model and how conference teams actually operate.
Is Eventberry a membership or association platform?+
No. Eventberry is event-first only. It is designed for conferences and event operations rather than memberships, renewals, chapters, committees, or dues workflows.
What does Eventberry cover?+
The platform is meant to cover event websites, registration, speakers, sponsors, attendee experiences, onsite operations, reporting, archive, and future-edition duplication from one workspace.
Does each event get its own public experience?+
Yes. The product model treats each event as a first-class entity with its own public portal, registration flow, and optional custom domain when launched.
FAQ section
Billing and launch
Answers anchored in the Eventberry product model and how conference teams actually operate.
When do we start paying?+
Billing begins when an event is launched or otherwise made public. Workspace creation and unlimited draft-event planning stay free before that point.
Can we create multiple draft events before deciding what to launch?+
Yes. Unlimited draft events are part of the model, so teams can plan future editions or parallel event concepts without turning billing on.
Is Eventberry self-serve or do we need a sales process?+
The core model is self-serve from signup through workspace creation and draft-event setup. Higher-touch operator and support surfaces exist in the platform, but they do not define the default onboarding path.
FAQ section
Delivery and operations
Answers anchored in the Eventberry product model and how conference teams actually operate.
Does Eventberry support multilingual event delivery?+
Yes. Multilingual foundations are treated as a day-zero architecture requirement across admin and public surfaces rather than as a late bolt-on.
Can Eventberry handle speakers, sponsors, and attendee-facing features too?+
Yes. The intended product scope includes speaker workflows, sponsor workflows, attendee portal experiences, communications, and related public pages as part of the same event stack.
What about onsite operations?+
Onsite work is launch-critical in the Eventberry model. Check-in, badging, scanning, and operational tooling are part of the product direction rather than an afterthought.
Get started
Still evaluating the fit?
Start with the pricing model and docs, or create a workspace and see how the event-first setup feels in practice.