09:41
local
Doors open
Staff open the venue workspace, review today's reservations, resource readiness, and anything that needs payment or waiver attention.
GridMagik connects public booking, scheduling, customer records, venue operations, and racing. Stripe-connected payments, multi-tender settlement, secure gift vouchers, and the first Square foundation are in controlled beta; unproven providers and hardware remain clearly labeled rollout work.
GridMagik brings public booking, customer records, staff operations, and racing into one workspace. Payment, waiver, gift, and external integration capabilities show their rollout status instead of pretending every module is already complete.
Real-time view of what's running where. Stays in sync even when your venue's Wi-Fi has a moment.
Bay/room/lane map, queue, current session, session timer, incident log. The board your floor manager actually wants on the wall.
The current foundation connects public booking to venue and racing operations. Each handoff shows what is available now and what still requires a rollout milestone.
Guests choose a real server-generated slot on the hosted booking site. Capacity is rechecked inside the same transaction that creates the reservation.
The vocabulary changes. The mechanics don’t. GridMagik runs the same operating system underneath every experience venue we serve.
View all industriesStaff open the venue workspace, review today's reservations, resource readiness, and anything that needs payment or waiver attention.
A group booking carries guest, product, time, and capacity data into the staff view. The team checks guests in and assigns the resources that are actually available.
Front desk creates or updates a reservation. Approved Stripe-beta venues can collect a card payment; other venues record cash or an externally processed tender explicitly.
The booking and operations core is usable now. Beta and planned modules are labeled so operators can evaluate the product they will actually receive.
Bay/room/lane map, queue, current session, session timer, incidents. The wall the floor manager actually wants.
ExploreOnline and staff bookings are live. Stripe checkout, Terminal, deposits, multi-tender settlement, partial refunds, and secure gift-voucher redemption are controlled beta.
ExploreGridMagik separates its own subscription billing from each venue's guest payments. Approved venues charge through their connected Stripe account; webhook, tenant, amount, and currency checks protect the booking record before it is marked paid.
GridMagik models timed sessions, capacity, rigs, participants, and venue resources directly. The differentiator is not a long checklist of imagined integrations; it is a booking record that can continue into live race and floor operations.
GridMagik will publish customer names, ratings, and measured outcomes only with verified evidence and permission. Until then, prospects see the release gates we use.
Concurrent public, staff, and race bookings must acquire the same resource locks before inventory is committed.
A signed Stripe event must match the connected tenant, transaction, expected amount, and currency before payment state changes.
Loading, empty, error, retry, cancel, and expired-session states are exercised alongside the happy path.
Available, beta, partial, and planned capabilities remain visible throughout evaluation and onboarding.
Stripe is the active payment foundation. Square has a mocked OAuth, Terminal, webhook, and settlement foundation awaiting real credentials and reader acceptance. The other brands below are delivery targets, not production connectors.
Tell us how your venue books, collects payment, and runs the floor. We'll demonstrate the current release, identify gaps, and put any rollout scope in writing.
Profiles, booking history, racing results, and leaderboards where they make sense. Staff can recognize returning guests without rebuilding context.
Hosted booking and capacity-safe reservations are available now. Stripe-connected online and Terminal payments are in controlled beta.
Staff find the booking, review guest, payment, and waiver status, then make the operational assignment. Automatic team assignment is still planned.
The venue and racing workspaces carry reservation, rig, participant, and session state through the operating day.
Booking and racing history remain attached to the customer and operational reports. Automated re-book and campaign flows are roadmap work.
Room scheduling, group bookings, success-rate tracking.
A rig or bay reports an issue. Staff update its operational state and adjust the session or assignment with an audit trail.
Staff run the event and racing workspaces from the same tenant. Advanced team assignment and automated messaging remain visible as rollout work where unavailable.
Operational reports summarize bookings, utilization, and activity. Immutable tender and refund reconciliation is controlled beta; payout, dispute, and settlement reporting remains planned.