Event control software
The log that holds up afterwards
Every incident, radio check and routine check logged as it happens, timestamped and append-only. Built for UK festivals, concerts and public events, and for the debrief that follows.
No card required. Set up an event in ten minutes.
01
The log gets written afterwards
When it's busy, entries get scribbled on a pad and typed up later. Times drift, detail goes missing, and the record becomes a reconstruction.
02
Nobody can prove the checks happened
Toilet checks, capacity counts and seating sweeps get done and never recorded. When someone asks for evidence, there isn't any.
03
The debrief takes a week
A licensing return assembled from a notebook, a spreadsheet and three people's memories, a fortnight after the event.
9s
From the radio call to a logged entry with a reference you can read back, on a wet screen, while still talking.
Step 01
Set up the event
Zones, stages, facilities, call signs and the checks your licence requires. Reuse a venue's setup from last time in two clicks.
Step 02
Run the shift
Log incidents in seconds, run radio checks and routine checks on your own intervals, dispatch and track tasks. It keeps working when the wifi doesn't.
Step 03
Prove it afterwards
Sign the handover, generate the debrief pack, export the log. The record is append-only, so it holds up when someone asks.
The platform
Eight modules, one record
Control Room is live today. The rest is being built outward from it, on the same record, so a licence expiry in staffing stops a sign-in at a gate and an ejection on the ground lands in the log within seconds. Status is stated plainly on each block — no dates until they're real.
Available now
Control
The running log, radio checks, routine checks on your own intervals, task dispatch, registers and the decision log. Append-only, works offline, and generates the handover and the debrief pack rather than leaving you to assemble them.
9s
From radio call to logged entry with a reference
In build
Staffing
Directory, digital screening packs completed on a phone, SIA and qualification tracking that blocks an expired badge before it reaches a gate, rota import, shift offers and sign-in.
In build
Ejections management
Warnings, refusals and ejections recorded at the point they happen, on a form you configure per event, with a required welfare assessment and a court-ready record produced in one click.
In development
Deployments & planning
Requirement, roster and deployment plan in one place. Positions, zones, coverage and gaps against your licence minimums, with the site map showing where everyone is.
0
Positions left uncovered before doors, or it tells you
In development
Compliance and ACS
Every policy, certificate, risk assessment and training record with version history and expiry, and the evidence pack for an ACS assessment generated rather than assembled.
ACS
Evidence pack generated from the record, not assembled
In development
Subcontracting
Supplied staff tracked alongside your own, with each supplier's insurance, ACS status and compliance evidence held against them. Supplied-to-own ratio reported per event.
In development
Reports
Incidents, ejections, check compliance and staffing across every event you have run. Rates per thousand attendees, year on year at the same venue, and the licensing return ready to send.
In development
Client platform
A read-only login for the promoter or venue. Their events, staffing delivered against contracted, an incident summary with personal data stripped, documents and the debrief pack.
1
Login for the client, with personal data stripped out
The running log
Log an incident in seconds
Type it the way you would say it on the radio. The bar reads the type, the location, the call sign and the priority out of the line, gives you a sequential reference you can read back, and puts it at the top of the log.
- Sequential references — LOG-0042, spoken back over the radio without spelling anything.
- Append-only. A correction is an attributed amendment underneath, never an edit.
- Both times recorded: when it happened, and when it was logged.
Routine and radio checks
Checks on your intervals, not ours
Every check type is yours to configure: what gets checked, how often, which questions get asked and what priority a failure raises. The board counts each one down separately and turns red when one goes past due.
- Own intervals per check type and per location.
- Own questions, with a failure priority set per question.
- Overdue is visible from across the room, not buried in a list.
The whole shift
The shift, hour by hour
From the radio check before doors to the moment the log locks. Scroll this row and the clock advances through the night with the log filling under it — which is exactly what the screen does on a live event, only slower.
- One record from set-up through to close.
- Handover signed by both controllers at shift change.
- Closing the event locks the log permanently, including to us.
On the ground
Tasks that land in a pocket
Dispatch a task from control and it arrives on the phone of the person who has to do it. Acknowledged, on scene and resolved are stamped as they happen, so the timings in the debrief are measured rather than remembered.
- Acknowledged, on scene and resolved, each timestamped.
- Works offline — entries queue on the device and sync in order.
- Everything the field does lands in the same log.
Ejections
Ejections, recorded properly
The form is configured per event and completed at the point it happens, on the tent's own device. The welfare assessment is a hard stop: the record cannot be filed without it, because that is the part that gets asked about afterwards.
- Configurable per event — the sections you need, not a generic form.
- Welfare assessment required before an ejection can be recorded.
- A court-ready record produced in one click, with the photographs attached.
Afterwards
Proof, the morning after
The figures, the charts, the decisions and the full log come out of the record itself, so the summary and the log cannot disagree. Nobody assembles it from a notebook and a spreadsheet on Monday.
- Generated from the record, not typed up from it.
- Excel with real dates and figures, not a locked PDF.
- Redacted version for a client, full version for your licensing authority.
Two-screen control room
The wall on one monitor, the entry form on the other
Launch the second screen from the first and they stay in step. Close it and everything carries on where it was. Works perfectly well on one.
How it's done now
- A paper day book, filled in when there's a gap.
- Entries typed up on Monday from a pad.
- Check records that exist only if someone remembered.
- A debrief assembled from a notebook, a spreadsheet and three people's memories.
- A licensing request that takes a fortnight to answer.
With Vantra
- Entries logged as they happen, in seconds.
- The time it happened and the time it was logged, both recorded.
- Checks on your own intervals, with what failed and what was done about it.
- A debrief pack generated from the record, the morning after.
- An export in one click, append-only and timestamped.
How we build it
Three decisions that are hard to undo, made deliberately
Append-only, enforced in the database
Not a setting and not a policy. There is no update or delete permission on a log entry, so an application bug cannot rewrite one. A correction is an attributed amendment underneath the original.
We cannot read your log without your approval
Support access is requested with a reason, approved by someone at your end, expires on its own, and shows a banner to your team the whole time it is open. Every screen we see lands in your audit trail.
Everything exportable at any time, in open formats
Excel and CSV for records, PDF for documents, JSON for the audit trail. No export fee, no notice period, no locked archive. If you leave, you take the lot.
Security and data
We cannot read your log
Support access is time-limited, requires your approval, shows a banner to your team while it's active, and is fully audited. Nobody here has standing access to an event log.
- Records are append-only and enforced in the database, not the interface.
- Every change, and every access to sensitive records, is logged with who and when.
- The audit trail is hash-chained, so tampering is detectable rather than merely prohibited.
- Closing an event locks its log permanently.
- Role-based access down to the field.
- Data held in the UK or EU.
- Retention policies you set, with automatic deletion and a report of what was removed.
- A data processing agreement available before you sign, not after.
- Everything exportable at any time. No lock-in.
Built for UK events
Set up the way the paperwork expects
- 24-hour clock and UK date formats throughout.
- Licence conditions, capacity limits and staffing minimums configured per event.
- Wind thresholds set per structure, from the supplier's own plan rather than a standard figure.
- Screening modelled on BS 7858, with SIA licence expiry blocking a sign-in before it reaches a gate.
- Exports built for a licensing return and for an ACS assessment.
Support
Support is answered by the person who writes the product.
From a company this size that is a feature, not an apology: there is no first line, no triage, and nobody who has to go and ask.
- Hours. 07:00 to 01:00 UK time every day an event is running, and 09:00 to 18:00 otherwise. Event days are covered because that is when it matters.
- Response. Under an hour during event hours, same working day otherwise. If your event is live and the log is not, you get a phone number rather than a ticket.
Afterwards
The debrief pack is generated, not assembled
The figures, the charts, the decisions and the full log come out of the record itself, so the numbers in the summary and the numbers in the log cannot disagree. In the safety officer's inbox the morning after, not the fortnight after.
Who's building Vantra
I built Vantra because of a notebook. Ours lived on the desk, and on a busy Saturday it got three lines while everything else went on the radio and stayed in somebody's head. On Monday two of us sat down and typed it up, arguing about whether the pit medical was at ten past nine or half past.
The checks were worse. The toilets were checked all night — I know they were, because I sent people to do it — and there was no record of a single one. When the licensing officer asked for the check records afterwards, the honest answer was that they existed as a memory. That is not an answer you want to give twice.
So this is the log I wanted at 21:14 on a wet Saturday: fast enough to use while you're talking on the radio, impossible to quietly rewrite on Monday, and able to produce the whole thing the morning after.
Founder — name to be added
Founder
Has worked event control rooms in the UK and built Vantra out of the parts of that job that were being done on paper. Writes the product, answers the support email, and takes the demo calls.
One person builds Vantra. There are no advisors listed here because there are none to list.
Pricing
Figures are placeholders while we finish pricing. The tiers are settled.
Single event
One-off events and organisers running their own show.
£—
Placeholder figure
- One event, with as many controllers on the log as you need.
- Running log, radio checks, routine checks and registers.
- Full export of the event file when it closes.
- Email support while the event is live.
Season
Security companies running events across a year.
£—
Placeholder figure
- Unlimited events across the season.
- Company staff directory, call sign libraries and event templates.
- Role-based access for owners, managers and controllers.
- Reporting across every event you have run.
Enterprise
Multi-site operations, SSO, custom retention, API access.
£—
Placeholder figure
- Single sign-on and provisioning for your staff.
- Retention periods and data residency set to your policy.
- API access to pull events into your own reporting.
- A named contact and an onboarding session for your control room team.
Questions
Resources
Useful whether or not you ever buy anything
Nothing gated. No email required.
- A control room log templateThe columns a day book needs to make sense later.
- A pre-event checklistWhat should be settled before doors.
- What a licensing officer asks forA plain list of what gets requested after an event.
Early access
Tell us which module would help most and we'll bring you in early
See it running before your next event
Twenty minutes on a call, with your event and your licence conditions in front of us. Or start the trial and set one up yourself.