One fixed price.
Sized to the event.
A 3-guard wedding and a 200-guard festival shouldn't cost the same, and a roster that existed for one weekend shouldn't bill you monthly. Standby prices by the size of the event, as one fixed number you see before it starts. Put it on the bid.
How the size is set
When you build the event, you've already told Standby the posts and the hours. We add that up into agent-hours, the total staffed time across the whole event, and that lands you in a category. You see your category and your number when you plan. Tracking one more walk-up or breaker never costs you a cent.
a wedding, a club night, a small show
- One full event, start to finish
- Unlimited posts and people
- Live board, breaks, relief, gear
- Credentials tracked with expiry dates
- Incidents, notes, after-action
- Full coverage-of-record reporting
a multi-day, a large single-day, a tour stop
- Everything in Single day
- Standard schedule import
- Clone a past event onto new dates
- Multiple areas, shifts, and days
- Client planning workflow
a multi-stage, multi-week festival
- Everything in Production
- Hundreds of posts across the grounds
- Custom scheduling software integration and contract upload
- Priority support from an operator
- Bigger than this? That's Enterprise.
Run events back to back all year? Buying them one at a time stops making sense somewhere around six or eight. The Season plan is a flat annual that covers your whole calendar, white-labels under your own brand, and handles multiple teams. If your company's name is going on the bid, your company's name should be on the board. Let's talk numbers.
These are real prices, but early customers can lock in lower rates now and they won't move on you later. If you run events and want in, request access and let's talk.
The admin you save is the
small part.
The night-before hours you stop spending on spreadsheets are the easy savings to count. They're also the floor. The real value shows up the night something goes wrong.
Your 1am back
Standby lines the contract grid up against the schedule export, so that time and stress go back into walking the site and briefing your leads, the things that need you. That alone pays for most events.
The dispute you win
When a client questions the invoice, you have coverage of record, post by post, against what they signed off on. One contested invoice on a big show is worth more than the tool.
The post that didn't go dark
The system catches the open post the moment it opens. In security, an uncovered post during an incident is a liability event and a lost contract.
The bid you win
Plan live with the client, and show them what a real post-event report looks like, something nobody else on the bid can offer. That lands contracts.
Straight answers.
How much does Standby cost?
Standby is priced per event, not per user per month. Single day is $100, Production is $600, and Festival is $2,500. Each tier covers a size band, and you see your category and your number when you plan the event, before it starts.
Why is Standby priced per event instead of per user per month?
Event work spikes for a weekend and then disappears. Per-user monthly billing charges you for a roster that was gone by Monday. Pricing by event size means the cost matches the work, and you know the number before you say yes to the client, so you can put it on the bid.
What are agent-hours?
Agent-hours are the total staffed time across the whole event. When you build the event you've already told Standby the posts and the hours, and it adds those up to place you in a price category. It's sizing logic, not a meter: tracking one more walk-up or breaker never costs extra.
Does Standby work without a signal?
Yes. Reception dies in the back corners of most sites, so the live board works offline. Moves save on the device and sync the moment the signal comes back.
What does Standby replace?
The whiteboard in the trailer, the schedule spreadsheet, the sign-in sheets, and the radio clipboard. The contracted plan, the live board, incidents and notes, and the final reporting all sit in one place instead of across tools that disagree.
Can my client see the coverage plan?
Yes. You build the contracted coverage with the client, and they review it in a read-only view and sign off. That sign-off becomes the baseline your coverage of record is measured against at the end of the event.
Is my event data used to train AI?
No. Your data is never sold, never shared, and never used to train AI. It's processed for one purpose, which is running your events.
Why not per-user?
Because I spent years watching software bill us per head, per month, for a roster that was gone by Monday. Event work spikes for a weekend and disappears. The price should do the same, and you should know it before you say yes to the client.