A fortieth of a second. Then the hard part.

Anyone can take the photograph. SnaptureX runs everything after the shutter — the cameras on the ride, the pipeline that renders what they catch, the till, the printer, the hand it ends up in — across every venue you operate, from one console.

HARBOUR POINT / GATE 3 / CAM-07

Live capture, LIVE21:47:06.412

A wooden coaster train cresting the lift hill, a family with their hands up and faces to the camera
FRAME 004182f/2.0 · 1/2000 s · ISO 3200

Frame record

004182 · 2026-09-22

  1. CapturedCAM-07 · Gate 30 s
  2. Matched4 riders0.31 s
  3. RenderedRide print + digital38 s
  4. Priced€18.00 · venue catalogue38 s
  5. On screenShop 2 · print queued52 s

On the shop screen 52 s after the shutter. The guest reaches the door in four minutes.

The face is lit for one frame.

Attraction photography is not a photography problem. It is a timing problem wearing a camera — and the whole budget is the walk to the shop.

0 s
38 s
52 s
240 s
0 s
Shutter · matched in 0.31 s
38 s
Rendered and priced
52 s
On the shop screen
240 s
Guest at the door
Shutter to shop screen in 52 seconds. The rest of the walk is margin.
One frameat 0 s
A dark ride at sixty kilometres an hour gives you a single usable exposure per guest. There is no retake — the train has already gone.
Four minutesto 240 s
The walk from ride exit to shop door. The render has to be finished, priced and on a screen before they reach it, or it sells to nobody.
Sixteen hourson repeat
Gates open to gates closed, every day of the season, at every venue at once. The pipeline never gets a maintenance window.

Five stages. Everyone else sells you three.

A device manager stops at capture. A render farm lives in the middle. A point-of-sale system has never heard of a camera. The seams between them are where a park’s media revenue leaks, and nobody owns the seam.

0102030405

Devices

Render

POS

SnaptureX

  1. 01

    Capture

    Cameras are owned by a venue and deployed to the leaf that uses them. Capture settings are versioned per location and pushed to the box in the park.

    CAM-07 → Gate 3 · v14

  2. 02

    Render

    Frames come out as products — profiles, composition layers, generated video. The queue is visible while it runs; failures are addressable, not silent.

    queue 12 · 0 failed

  3. 03

    Sell

    Products, packages and prices per venue. Point of sale with its own staff, payment methods and tills — part of the system, not a bolt-on beside it.

    Till 2 · €18.00 · card

  4. 04

    Deliver

    Printer pools resolve to the leaf that uses them. A print knows which counter it is going to before anyone walks to it.

    Shop 2 · Printer 1

  5. 05

    Reconcile

    Takings, closing, media mix, upload health — and what never arrived, which nobody else can tell you because they never held the capture end.

    closed · 2026-09-22

It opens on what broke.

Not a wall of every metric. A ranked queue of what needs a decision, each item a link to the place it gets fixed. Underneath it, the count nobody else can run, because nobody else was holding the camera.

Decision queue2 NEED YOU
  • 4mCamera offline for 4 minCAM-07 · Gate 3 · Harbour Point
  • 6dLicence lapses in 6 daysLIC-0418 · Till 2 · Harbour Point
  • 12m3 renders failedRND-2291 · Dusk overlay profile
  • 1hPrint pool reroutedPRN-12 · Shop 2 · Ridge Park
ReconcileCAM-07 · 2026-09-22

4,182frames

  • Sold1,59038%
  • Previewed, not bought2,05249%
  • Never reached a screen54013%

540 frames never reached a screen — every guest in them left without seeing the picture. A till cannot see that number.

One console. Every venue. No crossed wires.

Multi-tenant is easy to claim and expensive to get wrong. These three are enforced in the data layer, not in a review checklist — the only version of the promise that survives a busy Saturday.

  • Scope is explicit, every time

    Every read carries the operator and the venues they may see. There is no ambient current tenant, so a screen cannot quietly serve one operator another’s data.

    { userId, role, tenantIds }

  • Assets cannot cross a venue

    A camera is owned by a venue and deployed to a leaf beneath it. A deployment into another venue’s location is refused at the write, not caught in a report later.

    InvalidCameraDeploymentError

  • Yesterday stays yesterday

    A transaction freezes its site, business date and configuration version at capture, and they are never recomputed. Last season’s numbers do not move.

    FrozenAttribution

Bring us your estate.

Every park runs its media differently — different rides, different tills, different rules about what a print costs on a wet Tuesday. An evaluation starts with your operation in it, not a sandbox that proves nothing.

  1. 01Your estate tree loaded — countries, venues, sites, the leaves your cameras hang from.
  2. 02Your catalogue and prices in it, per venue, in your currency.
  3. 03A day of your captures run through match, render, till and print.