Post-production Scheduling for your whole facility:
from booking to invoice.

freispace is priced per facility, not per seat: every plan includes unlimited users, projects and resources, so adding a coordinator or a freelancer costs nothing. Plans start at £299 / €349 / $399 a month on an annual agreement.

The full price list, including the SSO, shifts and physical media modules, is published on the pricing page — you do not need a sales call to find out what it costs. There is also a payback calculator for working out what idle suite time is currently costing you.

Yes — most facilities that come to us are already mid-migration. Two routes work well:

• A dated cutover. Home Post Production moved its whole operation off a legacy scheduling system in 30 days, from 1 October to the end of that month, with no disruption to client delivery and no dual-running phase.
• A clean rebuild. Bumblebee Post set a go-live date and rebuilt rooms, resources and kits inside freispace rather than carrying a legacy data model across — a system configured for how the team wants to work now.

What transfers and what does not is set out on the ScheduALL, farmerswife and spreadsheet comparison pages.

Anything in the facility that can be double-booked:

• Edit suites, grading and dubbing theatres, studios and workstations
• Staff, freelancers and shifts
• Cameras, kit and physical media
• Software licences and floating seats
• Storage and server space

All of it on one schedule, with utilisation reporting drawn from the same bookings. See resource management. Drives, camera cards and LTO tapes are tracked separately in physical media tracking.

No. Every plan carries unlimited users, projects and resources, and pricing is per facility. That means the freelancer booked for a single day, the producer who only wants to look at the schedule, and the accountant who only touches invoices all cost the same as each other: nothing extra. It also means nobody is left off the system to save a licence.

Both, and deliberately in one place. A booking carries its rate, so the hours worked against it become quote lines and then invoice lines without anyone re-keying them into a second system. Invoicing is multilingual, adaptable to your own templates and EU e-invoice ready.

The same bookings feed live plan-versus-actual budgets and per-project CO2e reporting. See quoting & invoicing.

In ISO/IEC 27001-certified German data centres. There is no transfer of customer data to countries outside the EU, traffic is encrypted with SSL/TLS, and freispace is GDPR and PECR compliant. Sub-processors and the DPA are published rather than supplied on request. See data security & GDPR.

Yes. Because every booking sits in one system, utilisation is a live view rather than a report someone has to assemble — by room, by department, by client or by period, alongside plan-versus-actual on each project.

Olly Strous, CTO at Zinc Media Group, put it this way: “We have got much more clarity and visibility than we have ever had. In fact, I have been taking screenshots of the utilisation graphs and putting them in my monthly board report.”

Mostly that the data is in one place and reachable. Bookings, timesheets, budgets and invoices share one data model, so an assistant gets a complete answer rather than four partial ones. On top of that:

• orgAI answers on your live schedule, respecting each user's existing permissions
• Processing is self-hosted — no data goes to an external AI service
• An open MCP (Model Context Protocol) server for your own assistants and agents
• A documented REST API, plus Make, qibb, Helmut and Strawberry integrations

Yes. The MCP server lets an enterprise AI read the schedule directly, under the same permission model as a human user:

• Bring your own AI: connect your internal models and agents
• MCP (Model Context Protocol) server for standardised AI integration
• RESTful APIs and webhooks for custom automations
• Make, qibb, Helmut and Strawberry integrations for no-code automation

No. freispace will never use customer data to train AI models. The AI only accesses the data needed to answer a given request, in line with that user's permissions, and every interaction is recorded in the audit trail. Our model was trained on manually curated datasets.