There is a common pattern in event software that we decided not to follow. You build your event, design your emails, set up your door, and then discover that removing the vendor's logo — making the whole thing look like yours rather than theirs — sits behind a higher tier. Your brand on your own event becomes an upsell. We thought about that model for a while and concluded it had the priorities backwards, so we made branding the default and built the product around that decision.
This is not a small product choice dressed up as a principle. It changes what a guest sees at the door, what an organiser pays for, and what we are implicitly saying the platform is for. The short version is that we think the event belongs to the organiser, and the software should know its place — which is in the background, making your brand look good, not putting its own name on your front door.
The guest should see your event, not our software
An attendee at the door is forming an impression of your organisation, not ours. When the confirmation email comes from a vendor's address, the check-in page carries a vendor's logo, and the badge has someone else's branding in the corner, that impression is muddied. The guest is subtly reminded that you outsourced the front of house, and the seam shows at exactly the moment you most want to look in control.
Branding the event as the organiser's removes that seam. The email comes from you, the page is yours, the kiosk wears your colours, and the guest never thinks about the software at all — which is precisely how it should be. Good infrastructure is invisible. A guest who notices the check-in vendor is a guest who has been distracted from the event you actually invited them to.
The software running your door should be the one thing at your event nobody remembers seeing.
Charging to remove a logo is charging for the wrong thing
When you put white-labelling behind a paywall, you are effectively charging organisers to make the vendor less visible. Framed plainly, that is an odd thing to sell. It means the default product carries advertising for the platform on the organiser's own event, and the organiser pays a premium to stop advertising for someone else.
We did not want to be in that business. The events on the platform are not a marketing channel for us, and treating the organiser's door as our billboard felt like a quiet tax on people who simply wanted their event to look like their event. So the default is unbranded-by-us and branded-by-you, across the surfaces that matter:
- The registration and check-in pages your guests land on.
- The confirmation and reminder emails, sent from your address rather than a shared noreply.
- The kiosks and self-service screens at the door.
- The badges and passes guests carry.
None of that is a tier. It is what the product does. The wider case for consistent branding across every guest-facing surface is in one brand, every surface guests touch.
Custom domains belong in the same place
The same logic extends to the address bar. A check-in link on a generic vendor domain works perfectly well technically, but it tells the guest, again, whose software this really is. A link on your own domain — your event living at your address, with a valid SSL certificate so the browser shows it as secure — completes the impression that this is your operation end to end.
Treating custom domains as a routine capability rather than an enterprise extra follows directly from the branding decision. If the principle is that the event belongs to the organiser, then the organiser's domain on the door is not a luxury feature; it is part of letting the event be fully theirs. We explain the mechanics in your domain on the door: custom domains explained, but the philosophy is the same as everything above: your name, your address, your event.
What this looks like in practice
The difference between the two models is clearest side by side.
| Surface | Branding-as-upsell | Branding as default |
|---|---|---|
| Check-in page | Vendor logo unless you pay more | Your logo and colours, standard |
| Emails | Generic shared sender | From your address |
| Domain | Vendor subdomain by default | Your custom domain, with SSL |
| Badges | Vendor mark in the corner | Clean, your design |
| Guest's impression | "They used some platform" | "This is their event" |
Read the right-hand column and the through-line is that the guest never has to think about the tooling. That is the whole intent. The organiser gets an event that looks like theirs at every touchpoint, and the guest gets an experience with no visible seams, with no decision to make and no upgrade to buy to get there.
Defaults are a statement of values
The features a product gives away for free say more about its values than any of its marketing. By making branding and custom domains the default rather than the upsell, we are saying something specific: the event is yours, and our job is to run quietly underneath it, not to stamp our name on your front door and charge you to remove it.
It is a decision we are comfortable with, because it aligns what is good for the organiser with what the product does by default — no negotiating with a pricing tier to get your own brand back. An event should look like the people who made it. CheckInHub is built so that, from the first confirmation email to the badge a guest pins on, the only brand anyone sees is yours.
