Event Registration & Ticketing
vivenu
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by vivenu GmbH · vivenu.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
vivenu at a glance
- Vendor
- vivenu GmbH
- Headquarters
- Not stated on the vendor’s pages as of 29 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 29 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 29 Oct 2026
- Panel verdict
- The AI panel rates vivenu 3/5, the mean of 6 judges. vivenu is a white-label event ticketing platform from vivenu GmbH of Düsseldorf. how scores are made
- As of
- Vendor pages captured 29 Oct 2026; evaluated by the panel 30 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
vivenu is a white-label event ticketing platform from vivenu GmbH of Düsseldorf. Its strongest areas are shop and registration, where scores cluster at 7-8, and attendee data ownership, also 7-8: the captured pages show a shop under the organiser's own domain with interactive seat maps, time slots, season tickets, multi-day passes and custom registration questions, and the privacy policy states 100% customer data ownership, that the organiser decides which data categories are collected, and that purchase data is passed to the organiser. Check-in and on-site scores sit at 6-7. Payments and fees at 4-6 and invoicing and tax at 4-6 are weakest: we found no public information on the per-ticket fee, who pays it, payout timing, refunds or chargebacks, nor on invoices in the organiser's name, VAT-ID capture, credit notes or e-invoice formats. Sovereignty scores 4-6: a German contracting entity with named subprocessors, but ticket emails run through the US service mailgun, buyers' addresses reach MapBox, and hosting location is not stated. Judge scores clustered closely; no public prices appear, with demo booking as the route in.
Speaks for it
- White-label ticket shop runs under your own domain, with interactive seat maps, time slots, season tickets and multi-day passes
- Entitlements apply rule-based member discounts and fee waivers automatically at checkout, with no promo code required
- The privacy policy states 100% customer data ownership, that the organiser decides which data categories are collected, and that purchase data is passed to the organiser
- On-site operations are documented with a badge accreditation app, RFID and NFC access, self-service kiosks, POS terminals and vivenu's own entrance hardware
- The contracting entity is vivenu GmbH in Düsseldorf with commercial register HRB 89527 at the Amtsgericht Düsseldorf and German VAT ID DE330631090, and SOC 2 Type II, PCI-DSS and GDPR compliance published
Held against it
- We found no public information on the per-ticket fee, who pays it, payout timing and conditions, refunds of single orders or a cancelled event, or chargeback handling
- We found no public information on invoices in the organiser's name with consecutive numbers, business buyers' VAT IDs and reverse charge, credit notes, or e-invoice formats
- Tickets and invoices are emailed through the US service mailgun, and buyers' home addresses are transmitted to the US geocoding service MapBox
- We found no public information on where attendee, order and payment data are hosted
Best for
- You sell under your own brand and need seat-map booking, season tickets, multi-day passes and member pricing that applies automatically at checkout
- You treat buyer data as a first-party asset and want native sync into Salesforce, HubSpot or Mailchimp, or export through the REST API and webhooks
- You run large on-site entry operations — RFID and NFC access, badge accreditation with printers, self-service kiosks and POS terminals
- You want a German-contracted vendor with SOC 2 Type II, PCI-DSS and GDPR compliance published and certifications available on request
Avoid if
- Your finance team needs documented payout timing, refund terms and chargeback handling before committing — the pages name the payment partners but give no figures for these
- Your accounts payable process requires invoices in your own name with consecutive numbers, validated VAT IDs, credit notes or e-invoice formats — the pages describe automated tax calculation and localized invoices but give no information on these
- You must guarantee that buyer data never touches US services — ticket and invoice emails run through the US service mailgun, and buyers' home addresses reach the US service MapBox
The scores
| Criterion | Panel median |
|---|---|
| Ticket shop, checkout & registration | 3.5 of 5 |
| Payments, payouts, fees & refunds | 2.5 of 5 |
| VAT, invoices & accounting handoff | 2.5 of 5 |
| Check-in, badges & on-site sales | 3.5 of 5 |
| Attendee data & the customer relationship | 3.5 of 5 |
| European sovereignty | 2.5 of 5 |
Ticket shop, checkout & registration
Show reasoningHide reasoning
How this is scored
How a ticket or a registration is sold: ticket types and categories, member and early-bird prices, discount codes, bundles and add-ons, a shop embeddable on the organiser's own website or under its own domain, custom questions per ticket and per attendee, group and company bookings, capacity limits and waiting lists, reserved seating with a seating plan, recurring dates and course series, several languages, and an accessible mobile checkout.
0 — Not a ticketing or registration tool; tickets cannot be sold and registrations cannot be taken in the product.
3 — An event page on the platform with a few ticket types and a fixed sign-up form; embedding, custom questions, capacity rules or seating are basic or not described.
5 — Several ticket types with prices, quotas and sale periods, discount codes, custom questions per attendee, a shop embeddable on the organiser's website as a widget or link, capacity limits with a waiting list, and a checkout that works on a phone.
8 — A white-label shop under the organiser's own domain and design, reserved seating with a seating-plan editor, add-ons and bundles, group and company bookings with several attendees per order, conditional questions, member prices by code or login, recurring dates and course series, several languages, and the checkout's accessibility stated.
10 — A shop that fits any event: multi-event and season tickets, timed entry and seat holds, a checkout that the organiser can extend (API, custom fields synced to a CRM), an accessibility conformance statement (WCAG level named), and the conversion and drop-off of the checkout reported to the organiser.
The Conference Organiser
A white-label shop on our own domain showing only our logo and URL, interactive seat maps, multi-day passes and time slots, membership-linked entitlements that give members their price without a promo code, plus session add-ons and ticket bundles cover most of my congress. We found no public information on group orders where one assistant registers several colleagues at once, on conditional questions per attendee, on shop languages, or on an accessible mobile checkout. 1 2 3 5 10
The Venue Promoter
The captured pages show white-label shops under my own domain with my logo and ticket assets, a shop builder, seat-map booking alongside time slots, multi-day passes and season tickets, custom registration questions before or after purchase, bundles, and a rule-based benefits engine that gives members and segments discounts without promo codes. We found no public information on checkout languages, an accessibility statement for the checkout, or group bookings with several attendees per order, so it sits just under the top described level. 1 2 3 5 10
The Course Provider
White-label ticket shops run under my own domain with only my logo and URL visible, my own registration questions and forms before or after purchase, seat-map booking and reservations, add-on options and bundles, and rule-based discounts or fee waivers for members — plus a headless API and SDKs. We found no public information on waiting lists that refill a cancelled seat automatically, on several languages, or on an accessibility statement for the checkout. 1 2 3 5 10
The Revenue Accountant
A white-label shop under the organiser's own domain and design, seat-map booking with interactive plans, season tickets, multi-day passes, bundles, add-ons and custom questions before or after purchase are all documented, and entitlements deliver member and segment pricing at the checkout with a headless API and SDKs to extend it. We found no public information on shop languages, an accessibility statement for the checkout, or waiting lists, which keeps it off the top step. 1 2 3 4 5
The Data Protection Officer
The captured pages show white-label ticket shops on the organiser's own domain, interactive seat maps with seat-map booking, free seating, time slots, season tickets and multi-day passes, custom registration questions, session add-ons and ticket bundles, membership-based pricing through entitlements alongside promo codes, and a headless API with SDKs for extending the checkout. We found no public information on checkout accessibility, shop languages, or group and company bookings with several attendees per order, which holds this below the top band. 1 2 3 5 10
The Skeptic
A white-label shop under the organiser's own domain and design, interactive seat-map booking embeddable with a few lines of code, time slots, season tickets and multi-day passes, custom registration questions, forms before and after purchase, and rule-based member discounts that need no promo code — most of the way to the top tier. We found no public information on checkout languages, accessibility of the checkout, or conversion and drop-off reporting. 1 2 3 5 10
Payments, payouts, fees & refunds
Show reasoningHide reasoning
How this is scored
How the money moves: payment methods offered to buyers (cards, PayPal, SEPA direct debit, invoice, local methods), whether the organiser connects its own payment account or the platform collects as merchant of record, when the revenue is paid out (continuously, before the event, or after it), the per-ticket and payment fees and whether they can be passed on to the buyer, refunds of single tickets and of a cancelled event, ticket transfer and resale, and chargebacks.
0 — No payment of any kind; the product only collects free registrations.
3 — Online card payment through the platform; payout timing, fee model, refunds or buyer-paid fees are basic or not described.
5 — Several payment methods including cards and PayPal or SEPA, the fee per ticket stated with the option to pass it to the buyer, the payout schedule stated, and refunds of single orders and of a cancelled event issued from the product.
8 — A choice between the organiser's own payment account (Stripe, PayPal, Mollie or similar) and platform collection, payouts before the event stated with their conditions, invoice and bank transfer for business buyers, partial refunds and refund policies set per event, ticket transfer or resale by buyers, and chargeback handling explained.
10 — Full control of the money: the merchant of record named for each set-up, payout timing and any reserve held published, every fee itemised per order, refunds, transfers and resale with the organiser's rules enforced, and the cancellation process for an event documented end to end.
The Conference Organiser
Cards through Stripe and Adyen, PayPal, Klarna and SEPA direct debit are documented, and we can either connect our own payment gateways and merchant accounts or use the managed payment solution with payouts. We found no public information on the fee per ticket, on payout timing, on refunds of single orders or a cancelled event, or on chargebacks, so I cannot budget my 900 registrations from these pages. 4 7 11
The Venue Promoter
The privacy policy names the money chain — Adyen, Stripe, Klarna and PayPal handling cards, SEPA and instant transfers — and the finance pages state I can integrate my preferred gateways and merchant accounts or use managed payment solutions with payouts. But we found no public information on when the revenue actually lands relative to the event, refunds of single tickets or a cancelled night, or whether the service fee can be passed onto the buyer's twelve-euro ticket, which is exactly what I need before I book a band. 4 5 7 11
The Course Provider
Cards, PayPal, SEPA direct debit and Sofort run through named partners such as Stripe and Adyen, Klarna is offered, and any payment system including cryptocurrencies can be wired in through a payments API; I can connect my own gateway and merchant account or use the managed payment solution with payouts, and a controlled secondary market under my own rules is described. We found no public information on the per-ticket fee, payout timing and conditions, refunds of single orders or of a cancelled event, or chargebacks — the details I need to write my cancellation terms. 1 2 4 5 7 11
The Revenue Accountant
Cards, SEPA and Sofort run through named partners (Adyen, Stripe Europe, Klarna) alongside PayPal, the organiser can connect a preferred gateway and merchant account or take the optional managed payment solution with payouts, and resale runs through a controlled secondary market under the organiser's rules. We found no public information on payout timing and conditions, the per-ticket or payment fee and who absorbs it, refunds of single tickets or a cancelled event, or chargeback handling. 1 4 7 11
The Data Protection Officer
Payment methods are documented through the named partners Adyen, Stripe Payments Europe, Klarna and PayPal, covering cards, SEPA direct debit and instant transfer, and the organiser can either connect preferred global gateways and merchant accounts or use the platform's managed payment solution with payouts; a controlled secondary market by the organiser's rules and configurable fee structures are also described. We found no public information on payout timing, the per-ticket fee and who pays it, refunds of single orders or cancelled events, or chargeback handling. 1 4 7 11
The Skeptic
Cards, SEPA and Sofortüberweisung run through Adyen, Stripe, Klarna and PayPal, an organiser can connect its own gateway or use managed payments with payouts, and resale runs in a controlled secondary market. But we found no public information on the fee per ticket, who pays it, payout timing and conditions, refunds of a single order or of a cancelled event, or chargebacks — the money mechanics the organiser gets blamed for when they go wrong. 1 4 5 7 11
VAT, invoices & accounting handoff
Show reasoningHide reasoning
How this is scored
How ticket revenue reaches the books correctly: the VAT rate set per ticket or product (reduced rates for concerts and culture, exemptions for education and seminars), gross and net prices shown, invoices to buyers in the organiser's name with consecutive numbers, business buyers with company name and VAT ID, reverse charge for cross-border events, cancellation invoices and credit notes, the platform's own fee invoice, e-invoicing, and exports to DATEV or named accounting systems.
0 — No receipts or invoices; the organiser has to produce every invoice outside the product.
3 — An order confirmation or simple receipt per booking; VAT rates, invoices in the organiser's name, business buyers or accounting exports are basic or not described.
5 — VAT rate configurable per ticket, invoices generated in the organiser's name with its tax details and consecutive numbers, company name and address captured for business buyers, cancellation invoices on refund, and a sales export as CSV or to at least one named accounting system.
8 — Several VAT rates in one order, net prices for business buyers, VAT IDs validated and reverse charge applied, e-invoices (XRechnung or ZUGFeRD) for public and business buyers, a DATEV export with booking data, the platform's fee invoice separated from ticket revenue, and whether the platform sells as agent or in its own name stated.
10 — Tax handled per country: VAT rules for events in several EU countries documented with the place of supply, invoices and credit notes stated as compliant with national invoice law, a reconciliation of payouts, fees and ticket revenue per event, and a GoBD-compliant archive or audit export.
The Conference Organiser
A tax engine automating tax calculation across jurisdictions, localized professional invoices for every attendee, and real-time exports into SAP, Oracle or Microsoft Dynamics are claimed, with invoices emailed to buyers. The captured pages give no information on invoices issued in our name with consecutive numbers, on capturing company name and VAT ID for business buyers, on credit notes or on e-invoice formats — exactly what my accounts payable department checks. 4 7 11
The Venue Promoter
The pages promise an invoicing and tax system with worldwide compliance, automated VAT across jurisdictions, localized invoices emailed to every buyer, and real-time feeds into SAP, Oracle or Dynamics with reconciliation. We found no public information on invoices carrying my club's name with consecutive numbers, reduced VAT rates for concerts, reverse charge, cancellation invoices or a DATEV export, so I cannot yet tell if my accountant gets what she needs. 4 7 11
The Course Provider
An invoicing and tax system with 'worldwide compliance', automated tax calculation across jurisdictions, localized invoices and real-time streams into SAP, Oracle and Microsoft Dynamics is advertised. We found no public information on setting a VAT rate or an education exemption per ticket, invoices in my own name with consecutive numbers, business buyers with VAT ID and reverse charge, credit notes on cancellation, or a DATEV export. For one shop mixing exempt courses and taxable workshops, the specific tax behaviour is not documented. 1 4 11
The Revenue Accountant
The pages document an invoicing and tax system claimed compliant worldwide, automated VAT and sales-tax calculation across jurisdictions, localized invoices, and revenue streamed into SAP, Oracle or Microsoft Dynamics with automated financial exports and revision-safe audit logging. We found no public information on invoices in the organiser's name with consecutive numbers, credit notes on refund, reverse charge with validated VAT IDs, e-invoice formats, a DATEV export, or the platform's fee invoice kept apart from ticket revenue — every one of which my books need. 1 4 8 11
The Data Protection Officer
The pages describe a global tax engine that automates tax calculations across jurisdictions with VAT and sales-tax compliance and localised invoices, plus data streaming into named accounting systems — SAP, Oracle and Microsoft Dynamics — with real-time reconciliation and automated financial exports. We found no public information on invoices numbered in the organiser's name, business-buyer fields with validated VAT IDs and reverse charge, credit notes, a DATEV export, or e-invoice formats such as XRechnung or ZUGFeRD. 4 11
The Skeptic
Tax calculation across jurisdictions, VAT and sales-tax management, localized invoices, and streaming into SAP, Oracle and Microsoft Dynamics are documented, with tickets and invoices emailed to buyers. We found no public information on invoices in the organiser's name with consecutive numbers, business buyers' VAT IDs and reverse charge, credit notes, e-invoice formats, or the platform's own fee invoice — worldwide compliance is promised, not documented down to the invoice. 4 7 11
Check-in, badges & on-site sales
Show reasoningHide reasoning
How this is scored
What happens at the door: a check-in app that scans tickets on phones or scanners, offline scanning and several devices at once, entrances and time slots, check-in lists by name, badge printing with attendee data and QR code, box office and on-site sales with card terminals, walk-in registration, session and room check-in at conferences, attendance certificates, and live attendance figures.
0 — No check-in; tickets cannot be validated at the event.
3 — Tickets with a QR code and a guest list to tick off by hand or in a simple app; offline use, several devices, badges or on-site sales are basic or not described.
5 — A free check-in app for iOS and Android that scans tickets on several devices at once, works offline and syncs, a searchable guest list, and live check-in numbers in the dashboard.
8 — Badge printing with attendee data and QR codes, access rules per entrance, session or day, box office sales on site with a named card terminal, walk-in registration, dedicated scanner hardware supported or rented, and attendance certificates for courses.
10 — On-site operations at scale: self-service kiosks or turnstile integration, session check-in feeding continuing-education credits, cashless or on-site payments reconciled with online sales, and the hardware, offline limits and failover documented.
The Conference Organiser
A badge accreditation app, connections to badge printers and CRM, RFID and NFC access, tiered access logic, self-service kiosks, POS terminals on site, the vendor's own entry hardware and live accreditation statistics are all documented. For session-level check-in of my twenty-seat workshops, attendance certificates for continuing-education points, and the scanners' offline behaviour we found no public information. 1 2 3
The Venue Promoter
What is documented is big-venue kit: vivenu's own entrance hardware, self-service kiosks that take buyers straight to the door, RFID and NFC access, POS terminals on site, and a badge accreditation app with live statistics. We found no public information on a phone check-in app, offline scanning or several volunteer devices at once — and in my basement with no signal, that undocumented piece decides the score. 1 2 3
The Course Provider
The pages describe an app for badge accreditation with badge printers and CRM synchronisation, RFID and NFC access, tiered access logic, self-service kiosks leading straight to the entrance, POS terminals and spontaneous box-office sales, live accreditation statistics, and tailored entrance hardware from vivenu. We found no public information on offline scanning across several devices, a searchable guest list by name, or attendance certificates for courses. 1 2 3
The Revenue Accountant
The on-site story is real: a badge-accreditation app with badge-printer connectors, RFID and NFC access, tiered access levels and time slots, self-service kiosks feeding straight to the entrance, POS terminals and spontaneous upgrades at the box office, live accreditation figures, and vivenu's own entry hardware. We found no public information on a named card terminal, offline scanning behaviour, session or room check-in, or attendance certificates. 1 2 3
The Data Protection Officer
On-site operations are broadly documented: an accreditation app, connectable badge printers with CRM synchronisation, RFID and NFC access, tiered access logic with access levels and VIP entitlements, live accreditation statistics and mobile live dashboards, tailored vivenu hardware for the entrance, kiosk sales that lead straight to admission, and POS terminals with spontaneous purchases at the point of sale. We found no public information on offline scanning behaviour with several devices, attendance certificates for courses, or a named card terminal. 1 2 3
The Skeptic
An accreditation app with badge printers and CRM sync, RFID and NFC access, tiered access logic, self-service kiosks straight to entry, POS terminals, live accreditation figures and vivenu hardware for the door. We found no public information on offline scanning and its limits, several devices scanning at once, or attendance certificates. 1 2 3
Attendee data & the customer relationship
Show reasoningHide reasoning
How this is scored
Who the ticket buyer belongs to: whether the organiser is the controller of attendee data and the platform its processor, or the platform a controller in its own right; whether buyers must create an account on the platform; whether the platform markets other events to the organiser's buyers or lists the event on its own marketplace; consent for the organiser's newsletter collected in the checkout; messages to attendees; attendee data exportable at any time; and deletion and anonymisation after the event.
0 — The organiser receives no attendee data at all; the platform keeps the buyer relationship entirely.
3 — A guest list visible to the organiser; who is controller, the platform's own marketing to buyers, export or deletion are basic or not described.
5 — Attendee data exportable by the organiser at any time, the organiser named as controller with a data processing agreement offered, buyers able to book without a platform account, newsletter consent for the organiser collectable in the checkout, and messages to attendees from the product.
8 — A white-label set-up in which buyers see only the organiser, the platform stated not to market other events to the organiser's buyers (or the opt-out explained), the platform's marketplace listing optional, deletion and anonymisation of attendee data after the event configurable, and attendee data synced to a named CRM or via API and webhooks.
10 — The organiser owns the relationship and can prove it: the controller and processor roles documented for every data flow, no platform account or platform marketing by default, retention set per event and enforced, and a complete export of orders, attendees and answers that a successor tool can import.
The Conference Organiser
The organiser is stated to hold one hundred percent of customer data and to decide which personal data categories are collected, with the vendor acting as processor under CCPA and purchase data passed to the organiser; buyer records sync natively to Salesforce, HubSpot and Mailchimp, a consents feature sits alongside email campaigns, and white-label keeps buyers seeing only us. Whether buyers need a platform account, whether the vendor markets its own events to them, and whether retention is configurable per event are points we found no public information on. 1 2 7 10
The Venue Promoter
The pages state one hundred percent customer data ownership, that my club decides which data categories are collected, that purchase data is passed to me as the organizer, and that vivenu acts as processor; auto-updating customer segments, email campaigns with a consents module, native Salesforce and HubSpot sync and a REST API mean last month's buyer list is mine to mail. We found no public information on whether buyers need a platform account or whether the platform markets its own events to my buyers. 1 2 5 7 9
The Course Provider
The vendor states one hundred percent customer data ownership with no third-party monetisation, that the organiser and not the platform decides which categories of personal data are collected, and that purchase data is passed to the organiser; in the white-label shop buyers see only my logo, URL and ticket assets. Attendee data synchronises to Salesforce, HubSpot and Mailchimp with webhooks, and a consents and email-campaign module exists. We found no public information on booking without a platform account, on whether the platform markets other events to my attendees, or on deletion and retention configurable per event. 2 4 7 10 11
The Revenue Accountant
Ownership is stated in cash terms: 100% first-party ownership, data never shared or monetised, buyers seeing only the organiser's brand, purchase data passed to the organiser, the organiser deciding which data categories are collected, and vivenu acting as processor for end users; consents and email campaigns ship as modules and data syncs to Salesforce, HubSpot and Mailchimp or via API and webhooks. We found no public information on retention configured per event or on defaults for platform marketing to the organiser's buyers, so provable ownership end to end is out of reach. 1 2 7 10 11
The Data Protection Officer
The privacy policy states that purchase data is passed to the organiser for the event and that the organiser, not vivenu, decides which categories of personal data are collected — controller language I want to see — and the marketing pages claim one hundred percent customer ownership of buyer data with full white-label control so fans see only the organiser's logo and URL. Personal data is routinely blocked or deleted once the statutory retention period lapses, a Consents module sits beside the email-campaign features, and attendee data syncs natively to Salesforce, HubSpot and Mailchimp or out via API and webhooks. We found no public information on whether buyers need a platform account, on any statement that vivenu does not market its own events to organisers' buyers, or on retention configurable per event. 2 5 7 10
The Skeptic
The privacy policy states vivenu acts as processor, that the organiser — not the platform — decides which categories of personal data are collected, and that purchase data is passed to the organiser; buyers see a white-label shop only, consent and email campaign modules exist, and data syncs to Salesforce, HubSpot and Mailchimp or leaves through the API. We found no public information on whether buyers must create a platform account, whether the platform markets other events to an organiser's buyers, or retention set per event — the parts that decide what leaving would cost. 1 2 7 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where attendee, order and payment data are hosted, and who the subprocessors are (hosting, payment providers, email delivery, analytics, support). Independently sourced by the sovereignty pipeline; attendee lists show who goes where and when, and a conference list holds names, employers and dietary or accessibility answers, so the whole chain counts, not only the database.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (payments, email, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, a self-hosted or on-premises option or data export and deletion documented, and certifications published with their scope rather than implied.
The Conference Organiser
The contracting entity is vivenu GmbH in Düsseldorf with a commercial register number and German VAT ID, SOC 2 Type II with its scope named plus PCI DSS and GDPR compliance are published, and subprocessors are listed with addresses — Adyen in Amsterdam, Stripe in Dublin, Klarna in Stockholm, but also the US services mailgun, which emails the tickets and invoices, and MapBox, which receives buyers' home addresses, with standard contractual clauses named for Google. Where attendee, order and payment data are hosted we found no public information. 6 7 8
The Venue Promoter
The contracting entity is vivenu GmbH in Düsseldorf with a German register number, the privacy policy lists subprocessors with their addresses — including US services mailgun for ticket and invoice emails and MapBox, which receives buyers' home addresses — and names standard contractual clauses for Google and data processing agreements with all processors, while SOC 2 Type II is stated with its scope. We found no public information on where attendee, order and payment data are hosted, which keeps the score mid-table rather than top. 6 7 8
The Course Provider
The contracting entity is vivenu GmbH of Düsseldorf with a commercial-register entry and a German VAT number, and the privacy policy names its processors with addresses: Adyen in Amsterdam, Stripe in Dublin and Klarna in Stockholm, alongside US providers CloudFlare, Google Analytics, MapBox and mailgun — the tickets and invoices themselves are sent by email through that US service. SOC 2 Type II with a stated scope, PCI DSS and GDPR compliance are published. Hosting location for attendee and order data is not stated, so the residency of my course lists remains open. 6 7 8
The Revenue Accountant
The contracting entity is provably European — a GmbH in Düsseldorf with commercial register number and German VAT ID — and the subprocessor list names locations: Adyen in Amsterdam, Stripe Europe in Dublin and Klarna in Stockholm for payments, but US services for ticket email delivery (mailgun), analytics and geocoding of buyer addresses (Google, MapBox), with standard contractual clauses and processing agreements cited plus SOC 2 Type II with its scope, PCI-DSS and GDPR published. We found no public information on where order and attendee data are hosted or on the ownership structure, which caps the score. 6 7 8
The Data Protection Officer
vivenu GmbH is registered at the Düsseldorf local court with a German VAT ID, and the privacy policy names its processors with addresses: Adyen in Amsterdam, Stripe Payments Europe in Dublin, Klarna in Stockholm, and the US services mailgun (sending ticket and invoice emails), CloudFlare, Google Analytics, LinkedIn and MapBox, which receives buyers' home addresses for geocoding; standard contractual clauses are stated for Google and a data processing agreement for mailgun, and SOC 2 Type II with its scope plus PCI-DSS are published. The hosting location for attendee and order data is not stated on any captured page, and for MapBox no safeguard is stated, which caps this in the middle band. 6 7 8
The Skeptic
The contracting entity is vivenu GmbH of Düsseldorf with a commercial register entry and German VAT ID, subprocessors are named with addresses — Adyen in Amsterdam, Stripe in Dublin, Klarna in Stockholm — and SOC 2 Type II with its scope, PCI DSS and data processing agreements with all processors are stated. But tickets and invoices go out by email through the US service mailgun, buyers' home addresses reach the US mapping service MapBox, and we found no public information on where attendee, order and payment data are hosted. 6 7 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether an organiser can compute the real cost of an event from public pages alone: the fee per ticket or per registration (fixed, percentage or both), payment processing fees, whether fees are charged to the organiser or added to the buyer's price, free events, subscriptions or credit packs, payout and refund fees, add-ons (seating, white label, badges, box office), hardware rental, minimums and term, and VAT on the fees.
0 — No public prices at all; every organiser is a sales call.
3 — A starting price or "free for free events" exists, but the fee for paid tickets, payment fees or who pays them is unclear.
5 — The fee per ticket and the payment processing fees are public with the main inclusions, but at least one commonly needed piece (refund fees, white label, seating, box office, hardware) is unpriced or "on request".
8 — Every fee published with its rule (per ticket, percentage, cap), the share paid by buyer and organiser stated, add-ons and hardware priced, payout and refund fees listed, and VAT treatment of the fees stated.
10 — Complete price computability: the cost of an event derivable for a given ticket price, ticket count and payment mix, with every add-on, hardware, support and payout fee and the cancellation and data-return terms published.
The Conference Organiser
We found no public fee, price or free-event term on any captured page — neither a per-ticket fee, nor payment processing fees, nor a subscription or credit pack — and the documented route is booking a demo, with a dedicated account team accompanying enterprise customers. The transparency claims that do appear describe breakdowns of my own ticket prices and fee structures for my buyers, not what the platform charges me. 1 3 4 11
The Venue Promoter
The pages promise 'total fee transparency', detailed breakdowns of ticket pricing and distribution costs, configurable fees, and a benefits engine that can waive service and add-on fees — but we found no public information on any actual fee figure, payment processing costs, who pays the fee, or what the entrance hardware and kiosks cost. The only path shown is booking a demo, so I cannot price a twelve-euro ticket night from these pages. 3 4 10 11
The Course Provider
No fee figure appears on any captured page — not a per-ticket fee, a payment processing fee, a free-event term, a subscription or an add-on price — and engagement runs through demo booking and a dedicated account team. The advertised 'total fee transparency' and fee-structure reporting describe my own ticket prices and distribution costs inside the product, not the vendor's own prices, so I could not estimate what selling an eight-week course would cost me. 1 3 4 11
The Revenue Accountant
We found no public information on any price — per-ticket fee, payment fee rate, free-event terms, subscription, hardware rental or refund fees — and the only commercial entry point the pages show is booking a demo. The advertised fee transparency is an in-product dashboard that breaks down the organiser's own price and fee structures, which helps at month-end but does not let me cost an event before signing. 3 4 11
The Data Protection Officer
The captured pages describe detailed price breakdowns and fee structures as an in-product analytics feature for organisers and route prospects to a demo booking. We found no public prices, per-ticket fees, payment processing fees or free-event terms on any captured page, so the real cost of an event cannot be computed from them. 3 4 11
The Skeptic
Every captured page markets features and ends at booking a demo; we found no public price of any kind — no fee per ticket, no payment fee, no statement of who pays, no subscription, no add-on or hardware prices. The only fee facts live inside the product: organisers configure fees, view detailed fee breakdowns and can waive service and add-on fees — transparency for customers already inside, not for an organiser trying to compute the cost of an event in advance. 3 4 10 11
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about vivenu
Is vivenu European?
Yes. whats-best.ai classifies vivenu as EU-Made.
Where does vivenu store data?
Not stated on the vendor’s pages as of 29 Oct 2026.
Does vivenu have a free plan?
Not stated on the vendor’s pages as of 29 Oct 2026.
What are the best alternatives to vivenu?
As of 3 Nov 2026, the panel rates pretix (3/5), Converia (3/5) and doo (3/5) highest among the other 13 Event Registration & Ticketing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is pretix (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: vivenu alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (vivenu.com/de, vivenu.com/de/product-overview, vivenu.com/de/solutions/conventions, vivenu.com/de/for/finance, vivenu.com/de/developers, vivenu.com/de/imprint and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 8 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage vivenu.com Checked 29 Oct 2026 Details →
- 2 Features page (product overview) vivenu.com Checked 29 Oct 2026 Details →
- 3 Features page (conventions) vivenu.com Checked 29 Oct 2026 Details →
- 4 Features page (finance teams) vivenu.com Checked 29 Oct 2026 Details →
- 5 Developer documentation vivenu.com Checked 29 Oct 2026 Details →
- 6 Legal notice vivenu.com Checked 29 Oct 2026 Details →
- 7 Privacy policy vivenu.com Checked 29 Oct 2026 Details →
- 8 Security / trust page vivenu.com Checked 29 Oct 2026 Details →
- 9 Ticket shop, checkout & registration — found from sitemap vivenu.com Checked 29 Oct 2026 Details →
- 10 Ticket shop, checkout & registration — found from sitemap vivenu.com Checked 29 Oct 2026 Details →
- 11 Payments, payouts, fees & refunds — found from sitemap vivenu.com Checked 29 Oct 2026 Details →