For festivals, promoters and venues

Lineup to landing page to live campaign.

Backline is the operating system for event brands. One workspace where your lineup, your website, your audience and your paid campaigns run off the same record — without opening WordPress admin, Ads Manager or a spreadsheet.

Studio
Search Backline… ⌘K
Lineup & running order
Quick-add, by-day order, timetable grid, release waves.
21:00MainKesslerWave 1
22:30MainVela SoundWave 1
23:45HangarNils AroWave 2
01:00HangarTBAUnannounced
Artist archiveReturning-artist approvalArtist PA overlaysIntake links

Lineup, artists and every asset — with approval links that need no login.

LINEUP WAVE 2 · PUBLISHEDARTIST PA · AWAITING MANAGEMENTTICKETS PAGE · SCHEDULED FLIPPUSH · QUEUED FOR OWNER APPROVAL12 CAMPAIGNS · DRY RUN RESOLVEDMELBOURNE · BEHIND ON-SALE PACE27,300 METRIC ROWS · INGESTEDLINEUP WAVE 2 · PUBLISHEDARTIST PA · AWAITING MANAGEMENTTICKETS PAGE · SCHEDULED FLIPPUSH · QUEUED FOR OWNER APPROVAL12 CAMPAIGNS · DRY RUN RESOLVEDMELBOURNE · BEHIND ON-SALE PACE27,300 METRIC ROWS · INGESTED
What it is

Backline is one workspace for everything around an event. The lineup and the artists, the website they appear on, the fans who follow them, and the campaigns that sell the tickets.

Each of those is a tool you switch on separately, per client and per person. A festival that only needs a lineup and a website never sees the rest. Nothing is bundled you didn't ask for.

What connects them is one identity per event, carried into every system downstream. That is why the website, the audience and the ad reporting finally tell the same story.

0 × 90

Shows by days of metrics, reported in 0.30 seconds. Measured, not estimated.

0 shows

Launched from one template in 1.5 seconds — and launching twice creates nothing twice.

5 tools

Switched on per client and per user. You see and pay for what's on.

WCAG 2.1 AA

Audited pages, immutable approval logs, everything confirmed before it happens.

The real problem

It isn't too many tools.
It's that none of them agree on what an event is.

The join key

One ID.
Everywhere.

Every show gets a permanent code the moment it exists — brand, date, city. Cross-platform reporting stops being a data project and becomes a naming convention the software enforces.

Solstice · Berlin · 27 Junsolstice-260627-ber
Campaign & ad names
solstice-260627-ber_prospecting_v1
Written by the system, never by a person on a Friday.
Audiences
aud_solstice-260627-ber_lookalike
Every audience traceable back to its event.
Landing page
/events/solstice-260627-ber
Published from the same record that made the campaign.
Tracking
utm_campaign=solstice-260627-ber
One taxonomy across every channel, enforced in software.
Reporting row
solstice-260627-ber · spend vs ticket curve
Which is how spend and sales finally sit on one line.
Studio

The lineup, the artists, and every asset around them.

Studio is where the content of an event gets made — the running order, the artist profiles, the artwork, and the approvals that always take three weeks longer than they should.

Lineup builder

Quick-add bar, running order by day, a timetable grid, and release phases so an announce wave is a thing you plan rather than a thing you survive.

  • By-day running order and timetable grid
  • Announce waves as first-class objects
  • Adapts to festival or events cadence
Artist archive that survives seasons

Profiles are owned by your organisation, not by an edition. Bios, socials, images and embeds persist, with history per artist across every year they played.

  • One profile, every edition
  • Wikipedia image autofill with strict matching
  • Returning artists auto-flag for re-approval
Approvals without logins

Agents, managers and designers get a tokenized link. They upload or approve; you keep a versioned asset and an immutable log of who said yes and when.

  • Public intake links, file or Drive/Dropbox
  • Per-link open and submit tracking
  • Change-request notes back to you
Artist PAs, composed in-app

Branded artist images built with per-format overlays — square, portrait, story — then sent to management for approval on the same kind of public link.

  • Per-format overlays
  • Management approval loop
  • Feeds artwork slots downstream

The announce stops being a day you dread and becomes a button you press.

Sites

A real website, built by an agency, fed by your own data.

This is the part people underestimate. Sites is not a widget you embed — it is a custom, themed website built by Project BANG, wired so that your lineup, your artists and your news publish into it straight from Backline. Your team never opens WordPress admin again.

Publishing that behaves

Lineup, artists with featured images, news and pages push from Backline into your site. Re-publishing updates in place rather than duplicating, and it never blanks a field someone wrote by hand.

  • Idempotent — no duplicate posts, ever
  • Never downgrades a live post
  • Proven against a real production site
Edit pages without the admin

A block editor inside Backline — columns, a slash menu, SEO fields, and module blocks for lineup grids, news lists, newsletter and app CTAs. A page tree with subpages, and preview across devices.

  • Block editor with module blocks
  • Page tree, subpages, SEO fields
  • Device preview before anything ships
Announce waves in one click

A phase release publishes an entire wave to the site with throttled progress, so twelve artists going live at noon is one action rather than twelve.

  • Whole wave, one action
  • Throttled progress you can watch
  • Tickets page with scheduled status flips
Every client site looks different

Theme Studio gives each client a base theme, its own design tokens and a component library — customised on our side, so nobody gets a template that looks like the last one.

  • Per-client theme and tokens
  • Feature flags per client in the editor itself
  • Media library with public unguessable URLs

Your site stops being a queue you wait in and becomes an output of the work you were already doing.

Fanbase

The audience is yours. So is what it tells you.

Fanbase turns registered fans and their artist favourites into something you can actually book and market against — instead of leaving that signal on a ticketing platform you don't control.

Demand, before you book

A full demand table per artist: share of favourites, 30-day heat, and whether they're live, hidden or not booked at all. Announce signal per wave, so you know what your wave is worth before it goes out.

  • Share and 30-day heat per artist
  • Demand by wave, announce signal
  • Growth and source charts
Push with adults in the room

Owners send directly. Everyone else queues for owner approval. A 30-minute cooldown and a three-a-day cap stop the accidental spam, with an emergency override behind a hard confirm.

  • Approval queue for non-owner roles
  • Cooldown and daily caps
  • Emergency override, deliberately awkward
Fan tools on your own site

My Lineup and My Friends live on the public site and feed straight back into the same fan record — the reason the demand data exists at all.

  • My Lineup and My Friends
  • Per-artist favourites
  • One fan record across editions
Yours to take

CSV exports of fans with their favourites and per-artist favourite counts, available whenever you want them. No negotiation, no ticket to support.

  • Fans with favourites, exportable
  • Per-artist counts
  • No lock-in on your own audience

Everyone else rents your audience back to you. This one is just yours.

Campaigns

Forty shows, one template, nothing typed by hand.

The newest tool, and the one that changes the arithmetic. A show becomes a launched, tracked, reported paid campaign without anyone opening Ads Manager — and without anyone being able to spend money by accident.

Templates that resolve per show

A reusable recipe: budget, schedule offsets anchored to each show's on-sale date, ad sets with audiences and splits, and copy with tokens that fill themselves in. Build it once, apply it to forty shows.

  • Schedule offsets from each on-sale date
  • Token copy — {brandname} — {city}
  • Brands and tours roll up separately
Dry run before anything moves

One click resolves the entire campaign — every name, budget, schedule, audience, creative and landing URL — into a preview that touches nothing. Warnings surface missing artwork, missing ticket links and broken budget splits.

  • Complete resolved preview
  • Warnings before, not after
  • Launching twice duplicates nothing
Three gates, then paused anyway

A launch needs a per-run human confirmation, a per-client live flag we control, and verified credentials. Even then every object is created paused — spend requires a separate, deliberate action.

  • Per-run confirmation
  • Per-client live flag
  • Created paused by design
Spend against the ticket curve

Scheduled ingestion normalises spend, impressions, clicks, conversions and ROAS across platforms, alongside daily ticket-sales snapshots. Reporting runs per show, brand, tour, template and platform.

  • Spend and sales in one store
  • Alerts for shows behind on-sale pace
  • Sold-out shows still burning budget, flagged
Built to not fall over

Automatic retries with backoff, per-client rate budgets, a circuit breaker per platform and a dead-letter queue. A stuck launch is parked for one-click replay rather than lost in silence.

  • Retries, rate budgets, circuit breaker
  • Dead-letter queue with replay
  • Credentials health-checked daily
Meta-ready today

The Meta driver is built and verified against the Marketing API — campaigns, ad sets, ads, audiences, creatives, batch operations and spend guardrails. Live spend switches on with your own credentials. Klaviyo and TikTok are next.

  • Meta driver verified against the API
  • Per-run budget and object caps
  • Klaviyo and TikTok in progress

You find the show that's underselling three weeks early, not the week of.

The workspace

Built to be handed to someone who didn't ask for software.

The people who run events are not systems people. So every page opens with a plain-language twenty-second explanation, the dashboard shows what still needs a human, and nothing irreversible happens without a confirmation.

Guided home

Numbered steps with live status — what's done, what's missing, what's next.

Roles that mean something

Owner, web editor, studio user, reviewer, marketing. Each sees only their tools.

One activity feed

Publish outcomes, approvals, push activity and campaign alerts in a single bell.

No seats for outsiders

Agents and managers work through public links. You don't buy them a login.

Season rollover

Festivals roll into a new edition without losing artist history.

⌘K everywhere

A command palette, because the people using this are fast.

Who it's for

Four people, four different Mondays.

Festival marketing lead

The lineup lives in a spreadsheet, website changes go through an agency queue, and announce day is chaos.

Studio and Sites turn the announce into one action, on-brand and on time.
Touring promoter, several brands

Dozens of near-identical campaigns built by hand, naming chaos, and no idea which show is underselling until it's too late.

Templates, Event IDs, dry runs and on-sale alerts across every brand and tour.
Artist liaison

Press kits and artwork approvals chased over email, in threads nobody can reconstruct later.

Tokenized intake and approval links, versioned assets, an audit log that answers for itself.
Owner or agency

Every client is a bespoke snowflake and nothing is reusable between them.

Per-client themes and feature flags, one admin cockpit across every workspace.
Pricing

Clear prices, per tool.

Switch on only what your team uses. Every price below is what you pay.

Sites— your festival website, built and managed by Project BANG. Fanbase included: registered fans, favourites and push.
Starter
€1.800 / year
billed per quarter · €450 / quarter
+ €750 one-time set-up
Our proven festival template, in your identity
Essential
€3.600 / year
billed per quarter · €900 / quarter
+ €2.000 one-time set-up
Lightly customised design
Pro
€6.000 / year
billed per quarter · €1.500 / quarter
+ €3.000 one-time set-up
Bespoke design + a yearly refresh
Signature
€9.600 / year
billed per quarter · €2.400 / quarter
+ €4.000 one-time set-up
Fully bespoke, refreshed every edition
Minimum term two years — we build the site up front, so the commitment protects that work. You can move up a tier during the term, not down.
Studio
€240/ month
billed per quarter · €720 / quarter
3 users included · extra user €18/month
  • Lineup, phases & timetable
  • Artist archive & management approvals
  • Branded artist PAs
  • Asset intake links & approvals
Campaigns
€320/ month
billed per quarter · €960 / quarter
3 users included · extra user €18/month · ad spend goes straight to your own Meta account, no commission
  • Campaign templates per brand
  • Dry run before every launch
  • Show, tour & portfolio reporting
  • On-sale pace alerts
Bundle
−25%
on the software total from two tools
Studio + Campaigns: €560 → €420 / month, billed per quarter.
Always included: the Dashboard, your team with a role per person, and set-up by our team.

All prices in euro, excluding VAT. Everything is billed per quarter in advance: software can be cancelled per quarter; Sites: the one-time set-up is invoiced separately (bank transfer), then a quarter of the yearly price per quarter. Pay by card, SEPA direct debit, iDEAL or Bancontact. Upgrades are charged pro rata for the rest of the quarter; a smaller plan starts at the next quarter. No free trial — we set your workspace up with you.

Questions

The ones everybody asks.

Do we have to give up our website?

The opposite — you get a better one. Sites is a real agency-built site, themed per client, fed by your event data. You stop opening WordPress admin; the site itself stays yours.

Isn't this just another all-in-one suite?

Every tool is switched on per client and works standalone. A festival that only wants lineup and website never sees Campaigns. You pay for what's on.

Can an ad account be suspended for using an API?

No — the platforms publish and support these APIs. Suspensions come from policy breaches or grey-market tools that scrape or share credentials. Backline runs on your own verified app inside published limits.

What stops someone launching a campaign by accident?

Three gates. A per-run human confirmation, a per-client live flag we control, and verified credentials. On top of that every ad object is created paused — spend needs a separate deliberate action.

Who owns the data?

You do. Your event database, your fan records, your ad accounts. Exports are one click and always available.

Can external people upload artwork without an account?

Yes. Agents, artist managers and designers get a tokenized link — they upload or approve, you keep the audit log. Nobody outside your team needs a seat.

Walk through a live workspace.

Thirty minutes on a real demo workspace, then the same thing shaped around your own calendar. You'll know within ten whether it fits.

Tools switched on per client Your data, your ad accounts No media-spend commission

Book a demo, or get the one-pager.

Tell us who you are and we'll set up thirty minutes on a live workspace — or send the one-pager if you'd rather read first.

We only use this to answer you.