An event app
Shows the event to attendees: the programme, the map, who is there. It needs content, and a headless event platform is where that content comes from. Gatheratt Companion, our event app, reads the same API you get.
Headless event platform
Gatheratt is a headless event platform. Here is what that means, how it differs from an event app or a ticketing tool, and what you can build on it.
A headless event platform keeps everything an event is made of in one place, as structured data, and lets every place the event is shown read it through an API. Partners, speakers, sessions, stages and attendees are entered once; the event website, the event app, the digital signage in the venue, the badges and your other systems all read the same version.
Headless is how modern content systems are built: the content lives in one place, and the places it is shown, the heads, are separate and read it through an API. Gatheratt does that for events.
An example
They upload it in their own speaker portal. The screen outside the stage, the event app, the website and the badge all show the new one. Nobody on your team had to touch it.
How it works
Your team works in Backstage. Partners and speakers fill in their own parts in private portals with no login: logos, bios, photos, presentations and guest lists.
Everything is stored as connected data, not as documents. A session knows its stage, its time and its speakers. A partner knows its package, its logo and its stand. You decide what is published.
Every head reads the same data through the API: Gatheratt Companion, your website, the digital signage, the badges and your own systems. Change something once and they all follow.
Where it fits
Shows the event to attendees: the programme, the map, who is there. It needs content, and a headless event platform is where that content comes from. Gatheratt Companion, our event app, reads the same API you get.
Sells entry and knows who bought. Gatheratt sells tickets itself, or reads them from the provider you already use, and keeps the buyers in the same place as the partners, speakers and programme.
Where most event data lives today. Every copy goes out of date the moment someone changes a title or a photo. A headless event platform keeps one version, and everything reads that.
The heads
Programme, speakers and partners straight from Gatheratt, always the latest version.
Our event app is built on the same API. Yours can be too.
Now and next outside every stage, room signs and foyer screens, with the right speaker photos.
Names, companies and roles for the badge printer, ready when you print.
Places, stands and stages for maps and signage.
Partners, contacts and attendees where the rest of your team already works.
What event teams and developers ask about running an event headless.
Contact usA headless event platform keeps everything an event is made of in one place, as structured data, and lets every place the event is shown read it through an API. Partners, speakers, sessions, stages and attendees are entered once; the event website, the event app, the digital signage in the venue, the badges and your other systems all read the same version.
The same information is shown in many places at once: the website, the app, the screens by each stage, the badges, the partner’s own page. Every copy made by hand can be wrong. Entering it once means the speaker’s title on the badge matches the one in the app and on the screen outside the stage.
No. Gatheratt is the whole workspace: Backstage for your team, portals for partners and speakers, ticket sales, the registration desk, badges, Chase and the event app Gatheratt Companion. Headless means all of it is also open through the API, not that you have to build the front ends yourself.
No. The event app, the portals, the guest pages and the exports work as they are. Developers come in when you want your own website, digital signage or systems to read the same data.
The event and its programme days, sessions, stages, speakers and side events; partners with their packages, benefits, add-ons and stands; venues, floor plans and info pages. Badges and contacts are available to keys that are given that permission.
An admin of the event creates API keys in Gatheratt. A key reads the event; badges and contacts are extra permissions you give a key on purpose. The documentation is open at gatheratt.com/dev.
See it with your event
We will show you your event’s data, and the places it can show up.