Built to Perform
A CMS your teams can run and your developers can extend across venues, brands, and websites.
Choose who builds each website
Build in-house, keep your current agency, or bring another development partner. Basker does not tie the CMS to one delivery team.
Whoever builds the site, the platform stays the same.
Build a custom theme or connect a headless front end. Content, integrations and hosting stay in Basker either way.
Discuss your projectAdd the fields and content types your organisation needs
Create custom attributes and data objects for memberships, artists, sponsors, venue resources, and programme-specific content.
Extend the content model yourself.
Add structured metadata to events, posts, settings, and other records. When standard collections do not fit, create a custom object that editors can manage in the CMS and developers can use through the APIs.
Compare plans A CMS shaped like
your season
-
Hosting is our job
Basker handles hosting, updates, and support. Your team runs the content.
-
Publish a season without a deploy
A block editor with live preview. Editors build season and event pages themselves and publish when they are ready.
-
Designers and editors work in parallel
Designers ship custom themes. Editors keep the same tools, whichever theme is live.
-
One API for every front end
Use the GraphQL and REST APIs to feed mobile apps, kiosks and digital signage from the same content.
-
A content model built for live events
Events, performances, people, works, seasons, series and venues are built in, along with the links between them.
-
Keep ticketing data current
Prices, holds, and booking links stay in sync with your configured ticketing integration.
App ecosystem
Apps for ticketing, asset management and analytics. Install the ones you use.