Questions,
straight answers

Most customers go to production within 5–7 business days. Complex configurations involving custom integrations, multi-language content, or non-standard ticketing flows typically take 2–3 weeks.

A nominated point of contact, brand assets (logo, color palette, typography), and event content (sessions, speakers, sponsors). Total customer effort averages four hours across the implementation.

No. The platform is configured through the admin interface and structured imports. A REST API is available for customers who wish to automate workflows on their side.

Fivras submits iOS and Android builds to the App Store and Google Play. Submissions may be filed under your developer accounts or under Fivras's, at your discretion.

Yes. The web hub deploys under your domain. The mobile applications are published with your event's name, screenshots, and metadata. The Fivras brand is not present in the attendee experience.

Yes. The web hub is deployed at a domain you own. SSL certificates are issued and renewed automatically.

Yes. We support both arrangements; the choice is yours and can be revisited per event.

Two pricing models: per-event pricing for organizations running one to two events per year, and an annual subscription covering unlimited events. Pricing scales with attendee volume and feature tier. See the pricing section for current rates.

No hard cap is enforced during the event. Usage is reconciled on the next billing cycle, never during your event window.

Monthly plans terminate at the end of the current period without penalty. Annual plans terminate at renewal; we provide a 30-day reminder before any renewal.

Attendees populate a structured profile that captures role, industry, interests, and stated objectives. The engine generates ranked introductions using configurable matching weights, and proposes mutually free meeting slots inside the app.

Sponsors receive scoped dashboards covering banner impressions, profile views, QR scan counts, and lead capture. Branded PDF reports can be generated at the end of each event.

Yes. Customers on annual plans run unlimited events on a single workspace. The branded platform is reused across events; only content changes between cycles.

Native integrations exist for HubSpot, Salesforce, Mailchimp, and Zapier. A REST API and signed webhooks cover additional systems.

You retain full ownership. Fivras processes data on your behalf as a sub-processor under a standard data processing agreement.

In EU regions on infrastructure operated by tier-one cloud providers. Region selection can be configured for enterprise customers.

Yes. A DPA is available on request. Attendee data can be exported or deleted on demand from the admin interface.

English, Romanian, and French in the base product. Additional languages can be added on annual plans.

A dedicated point of contact is available via Slack or email for the week leading up to and the duration of your event. Average response time during event hours is under 10 minutes.

Fivras targets 99.9% uptime. Status and incidents are published on a public status page.