1. Home
  2. Pricing
Pricing

Cinema software pricing: from $200 to $20,000 a year

Filmgrail is a flat price per screen, with no per-ticket fees and no share of your sales: from $200 a year for a single-screen cinema up to $20,000 a year for a large circuit. A mid-size international film festival pays about $5,000 a year. Most cinemas are live within a few weeks.

$200
per year

Single-screen cinema: the entry point. Flat per screen — no per-ticket fees.

$20,000
per year

The top of the range, for large multi-site circuits.

~$5,000
per year

A mid-size international film festival.

Weeks
to go live

A few weeks if we already integrate your box office and payment provider; about a month for a new one.

How the Filmgrail price is set

By screens, and nothing else that matters. The annual price scales with the number of screens you operate. A single-screen town cinema starts at $200 a year. A multi-site circuit sits towards the top of the range at up to $20,000 a year. Everything in between is priced on the same scale, so a cinema that adds a screen knows what it adds to the bill before it asks.

Festivals are priced on the size of the edition — screenings, venues, passes and accreditation. A mid-size international festival with a public programme and an industry section pays about $5,000 a year, and the site rolls forward from one edition to the next rather than being rebuilt and re-bought.

Setup is fast. If we already integrate your box office and payment provider, you are typically live within a few weeks. If we need to build a new integration for your provider, allow about a month. Either way, you can see your own cinema running on Filmgrail before you talk to anyone — build a free prototype of your website from your current address.

Compare that with what the big platforms charge a mid-size cinema, and with how long their implementations take. Then ask us for your exact number.

The standard shape of a cinema software deal

Almost every vendor in this market prices in two parts. Filmgrail does not: we charge one flat annual price per screen, with no per-ticket fee and no percentage of your sales.

A platform fee. A recurring charge, usually monthly or annual, covering the software itself, hosting, updates, support and the apps in the stores. It normally scales with the size of the operation, most often by screen count or by site.

A transaction fee. A per-ticket amount or a percentage of the online sale. This is where a vendor's revenue tracks your success, and it is also where two quotes that look similar can diverge enormously once you put real volume through them.

On top of those there is usually a one-off implementation charge covering the integration with your box office, the design and build, content migration and launch. Whether that is a large number or a small one depends almost entirely on what your existing box office system exposes.

What actually moves the number

These are the six variables that decide where a cinema lands in the range. Two cinemas with the same screen count can be a long way apart on all of them.

Screens and sites

The primary scaling factor almost everywhere. A single hall, a four-screen independent and a twelve-site circuit are three different products from an operations and support point of view, whatever the feature list says.

Online ticket volume

Where a transaction fee applies, this is the number that matters most, and it is the one to model at three-year volumes rather than today's. A percentage that looks cheap at current volume can become the largest line in the deal after a good year.

What your box office exposes

A documented API is a short integration. An undocumented database or a vendor who does not want to help is a long one. This single factor causes more variation in implementation cost than anything else.

How much of the platform you take

Website only, website plus native apps, plus loyalty, plus the planning tool, plus festival sites. Each is a real piece of software with its own cost to run.

Languages and markets

A bilingual cinema, a festival running in three languages, or a group operating across borders all carry more content and more testing than a single-language single site.

Payment and local requirements

Local payment methods, tax and invoicing rules, accessibility legislation and data protection obligations vary by market and carry real work.

What is normally included, and what normally is not

The gap between two quotes is usually in this table rather than in the headline number.

ItemUsually includedUsually extra
The software, hosting and updatesYes
Support and incident responseYes, at a stated levelFaster response tiers
Apple and Google developer account feesPaid by the cinema, to Apple and Google
Payment processing feesPaid to your payment provider, not the software vendor
Integration with your existing box officeScoped as implementationExtra if the other vendor charges for access
Design and brand workA configured themeBespoke design beyond it
Content migration from the old siteBasic pages and redirectsLarge archives and bespoke data
TrainingYesOn-site training and travel
New features you specifically requestQuoted separately

This is the pattern across the market rather than a description of one vendor's contract. Get every line of it in writing before signing with anybody.

Seven questions that make two quotes comparable

  • Model it at three-year volume, not today's. Ask each vendor for the total cost at your current online volume, at 1.5x and at 2x. Percentage deals and flat deals cross over somewhere, and you want to know where.
  • Ask what the implementation number assumes. Specifically, which box office system, which interface, and what happens to the price if that assumption turns out to be wrong.
  • Separate the software fee from the payment fee. A quote that blends them is hiding one of them. Payment processing is a cost you pay your bank or PSP, and it should be visible separately.
  • Ask about the annual increase. Uplift clauses are normal and negotiable. An index-linked rise you agreed to in year one compounds quietly across a five-year term.
  • Price the exit before you price the entry. Contract length, notice period, transition support and a full data export in a usable format. All negotiable now, none of it negotiable later.
  • Count the internal cost. Staff time during implementation, training, and whoever has to run the CMS afterwards. It is real money and it never appears on a quote.
  • Ask what happens in year two. Who you call, how quickly they answer, what a change request costs, and how often the product actually ships anything.

Why we quote after a demo rather than before

Because the honest number depends on things we cannot know from a form: which box office system you run, what it exposes, how many screens, how much of the platform you want, what volume goes through it and which market you operate in.

What you get instead is specific. Book a demo, we run a session against your own programme, and afterwards you receive a written cost assessment for your cinema and a three-year return-on-investment estimate. Both are free, both are yours to circulate internally, and neither obliges you to anything. Most cinemas take the ROI estimate into the budget conversation before there is a budget line at all.

If what you need right now is a rough order of magnitude for a board paper, say so in the demo request and we will give you a range for your screen count before the session rather than after it.

The number that actually decides this

Not the fee. The delta.

Cinema software is one of the few operating costs that is supposed to increase revenue, so the only sensible way to evaluate it is against what it moves: online share of total admissions, checkout completion rate, repeat visit frequency, and spend per moviegoer once loyalty and concession pre-order are in play.

Across cinemas on this platform, nine out of ten end users create a profile, engagement runs about four times the industry benchmark for standard ticketing sites and apps, and the average yearly increase in digital ticket sales is 89%. Those are our published figures and you should treat them the way you would treat any vendor's: as a reason to test it on your own cinema with a free prototype, not as a forecast for yours.

Run the arithmetic on your own admissions. If a realistic improvement in online share and repeat frequency does not clear the annual cost by a comfortable margin, do not buy it from us or from anybody else.

Answers

Frequently asked questions

How much does Filmgrail cost?

From $200 a year for a single-screen cinema to $20,000 a year for a large circuit, priced by number of screens. A mid-size international film festival pays about $5,000 a year.

How long does it take to go live?

A few weeks when we already integrate your ticketing and payment provider; about a month when we need to integrate a new provider.

How much does cinema ticketing software cost?

Across the market it is normally a platform fee plus a per-ticket or percentage transaction fee. Filmgrail is a flat price per screen, $200 to $20,000 a year in total, with no per-ticket fee. The spread across the market is wide because a single-screen independent and a national circuit are genuinely different products. Get a written quote modelled at your own volume rather than relying on any published figure.

How much does a cinema app cost to build?

A bespoke native app built from scratch is a six-figure project in most markets, plus ongoing maintenance, store compliance and OS updates every year. A platform app is a fraction of that because the engineering is shared across every cinema on it. The trade is customisation, and for most exhibitors that trade is worth making.

Why will nobody in this market publish prices?

Partly because the variables genuinely are large, and partly because vendors prefer to quote after they know your size. The first reason is real. The defence against the second is to insist on the cost modelled at your own three-year volume, in writing, with the assumptions stated.

Is there a setup or implementation fee?

Usually yes, covering the integration with your box office, the build, content migration and launch. Its size depends mostly on what your existing box office exposes, which is why any implementation quote given before somebody has looked at your specific system is a guess.

Do we pay a percentage of ticket revenue?

Not on Filmgrail: the price is flat per screen, so a record year costs you nothing extra. Elsewhere, a per-ticket fee or a percentage of the online sale is the normal model, and it is worth modelling carefully. A percentage that looks small today is the line that grows fastest if the platform does its job.

Are payment processing fees included?

No, and they should not be. Payment processing is paid to your own payment provider under your own merchant agreement. Any vendor blending it into their fee is obscuring one of the two numbers.

Can we start small?

Yes. Many cinemas take the website first and add native apps once content and checkout are running well, because the CMS is shared and the integration is done once. It keeps the first commitment small.

What is the cheapest way to fix a bad cinema website?

Almost always by replacing the digital layer rather than the box office beneath it. A box office migration means retraining, data migration and counter downtime; a digital layer project means none of those, and it is the part your audience actually sees.