1. Home
  2. Integrations
  3. MyCloudCinema
Integration

Filmgrail + MyCloudCinema

Cloud box office systems removed the server from the back office. They did not, on their own, give independents a digital presence worth the name.

What running Filmgrail on MyCloudCinema means

MyCloudCinema solves the operational half of a small cinema's software problem: scheduling, ticketing and reporting without a machine in a cupboard. That is the right foundation, and there is no reason to move off it.

The half it does not solve is the one the audience judges you on. Filmgrail reads your programme and seating from MyCloudCinema and gives you a branded website, native iOS and Android apps, a CMS, a conversion-focused checkout, loyalty and audience analytics, with the completed sale written back so your reporting stays whole.

What moves between the two systems

Nothing is re-keyed. The integration reads what your box office already knows and writes back what the moviegoer just did.

Films and metadata

Titles, synopses, running times, certificates, cast, genres and release dates, enriched with artwork and trailers so film pages are not a line of text and a poster.

Sessions and showtimes

Every performance with its screen, format, language, subtitle and accessibility attributes, updated as the schedule changes rather than overnight.

Seat maps and availability

Live hall layouts with holds, house seats, wheelchair spaces and companion seating rendered exactly as they exist in the box office.

Ticket types and pricing

Adult, child, concession, member and loyalty pricing, plus surcharges and booking fees, applied by your own rules rather than duplicated in a second price list.

The completed order

Seats, ticket types, amounts and payment reference written back so the sale appears in your daily reports alongside the counter.

Reconciliation

A matching report on both sides so finance can tie the digital channel to the box office totals without a spreadsheet.

What your moviegoers get

  • A website built to sell, not to inform. Programme, film pages, showtimes, seat selection and checkout on one fast, mobile-first site you control through a CMS rather than a ticket iframe bolted onto a brochure page.
  • Native iOS and Android apps. Not a wrapper around your booking page. Autoplaying trailers, stories, watchlists, personalised showtimes and push — the things that make somebody open the app in a week when they are not buying.
  • One CMS for both. Films, showtimes, articles, carousels, banners, gift cards, push campaigns and loyalty edited once and published to web and app together.
  • A checkout that finishes. Seat maps, ticket types, fees, gift cards, value cards and saved payment in a flow measured on completion rate rather than on feature count.
  • Moviegoer identity. Nine out of ten end users on the platform create a profile, which turns anonymous transactions into a customer base you can segment, target and measure.
  • Audience data you can act on. Demographics, engagement, watchlists, ratings, sessions and digital box office in one view, joined across site and app.

What stays in MyCloudCinema

Programming and scheduling, ticketing, counter sales, and every report you rely on. The cloud system you chose keeps doing the job you chose it for.

Who owns what

The division of responsibility between MyCloudCinema and Filmgrail, written out so nobody discovers it in month three.

AreaMyCloudCinemaFilmgrail
Programme and schedulingSource of truthReads and publishes
Seat maps and inventorySource of truthReads and renders
Ticket types and pricing rulesSource of truthApplies at checkout
Counter and kiosk salesOwnsNot involved
Website and native appsNot involvedOwns
Online checkout and payment flowReceives the completed saleOwns the experience
Content, campaigns and pushNot involvedOwns
Moviegoer profiles and loyaltyWhere the system provides itOwns the digital layer
Box office reporting and settlementSource of truthReconciles against it

The point of the split is that your finance and operations reporting never moves. Every online sale lands back in your box office as an ordinary transaction, against the same ticket types and the same price rules the counter uses.

How a project actually runs

First we look at what your deployment exposes. That is a short technical conversation, not a discovery workshop, and it ends with a straight answer about whether the integration is a week of work or a quarter of it.

Then the build: your branding, your content model, your seat maps, your ticket types, your checkout rules. You review it on a staging site against your real programme, not a demo dataset.

Then launch, with your old URLs redirected rather than dropped so the search visibility you have built comes with you. Apps follow the site, usually a few weeks behind, because the CMS and the content are shared and there is no point shipping an empty app.

Nothing in that sequence requires you to touch the box office, which is why the risk of trying it is so much lower than it feels.

Answers

Frequently asked questions

Is this overkill for a two-screen cinema?

Independents and single screens are a core part of the platform, not an afterthought. The cost assessment is sized to your screens and your volume.

Do we lose anything by adding another system?

You gain a layer rather than swapping one. The risk profile is low precisely because your box office is untouched: the worst case is the website you had before.

Does the online sale show in MyCloudCinema?

Yes. Completed orders are written back so your session performance, ticket mix and takings stay in one system.

Who maintains the website afterwards?

You do, through the CMS, without needing a developer. Films, showtimes, articles, banners, carousels, gift cards and push campaigns are all editable from one admin panel.

Can we start with just the website and add apps later?

Yes. Many cinemas do the site first and add native apps once the content and the checkout are running well. The CMS is shared, so the apps inherit what you have already built.