Going to IAAPA? Come see us at booth #W2283, located at the First Time Exhibitors Pavilion in the West Concourse.
Turntable Ops

Turntable Ops

How we connect.

Every system you run holds part of the weekend. These are the routes we reach for most, cheapest first. If your system offers something else, we use that.

  1. Your system read-only key Turntable Ops

    API

    Your vendor's own interface. The cleanest route, and the first one we try.

    You do
    Create a read-only credential inside your own system, and hand it over.
    We do
    Pull your history once, then keep it current every night.
    You keep
    The credential. Revoke it and we are out.
  2. Your vendor Mon · Tue · Wed Turntable Ops

    Scheduled delivery

    Some vendors will not open an interface but will send files on a schedule.

    You do
    Ask your vendor to switch it on. We give them the address.
    We do
    Set up a folder only your venue can write to, and load each file as it lands.
    You keep
    A dated copy of every delivery, so a night that never arrived is visible.
  3. Your building HTTPS out Turntable Ops

    On-premise collector

    For a system that lives on a server in your building, with no interface at all.

    You do
    Give us one session on that server to install a small program.
    We do
    Read the tables nightly, in a maintenance window, and post them out over HTTPS. Nothing opens a door inward, and anything personal never leaves the building.
    You keep
    A kill switch. The program checks in before every run and stops when told to.
  4. Your report on arrival Turntable Ops

    Report emails

    A last resort, for a system that offers nothing else.

    You do
    Schedule the reports your system already emails, to an address we give you.
    We do
    Read each one on arrival.
    You keep
    The schedule. Stop the emails and the feed stops.

Where does my data go?

  • Into a warehouse built for you on Google Cloud. Your venue gets its own container in BigQuery, holding only what came from your systems. Never mixed with another venue's, and deleted if you leave.
  • The original records, not just totals. Every check, every play, every hour on the door counter, at the grain your system keeps them, so any figure can be traced back to the rows it came from.
  • We build you one model. Your systems are joined into a single picture of your venue: sales, play, traffic and labor side by side, on one business day, so Saturday means the same hours in all of them.
  • We define your terms. What "Total Sales" adds up at your venue, what counts as an entry, what a card load is. Written down for your account, used the same way on every page and in every answer.
  • We check it against your vendor's own totals. A figure that drifts from what your system prints gets caught before you see it.
  • We never log in to your systems. No passwords, no screen scraping, no bots.

Questions we get.

What if I have a system you've never connected to before?

Then it's the next one. We look at what your system offers, pick the route, and tell you what it needs from you before anything starts.

Who makes the connections?

We do. You create a credential, or give us one session on a server. Your monthly working sessions are where we walk through it together.

Do you need a login to my systems?

No. A read-only credential you create, or a program that reads and posts out. We never sign in as you.

What about my customers' personal details?

We don't take them. Names, phone numbers and email addresses are left out before anything leaves your building or your vendor.

What happens first?

We pull your history. The first question you ask already has years behind it.

How long does it take?

An API is days. A vendor delivery or a collector depends on the vendor, and we tell you where it stands rather than guess.

Can I turn it off?

Yes. Revoke the credential, flip the collector's kill switch, or stop the emails. Your data stays yours, and is deleted if you leave.

Who can see it?

The people you give a login to. Our own staff can read your account when they're working on it, and every question they ask on it is marked as ours, never counted as yours.

Do you share it or sell it?

No. Your figures are never shown to another venue. The only thing that leaves your container is a daily total, and only if we're building a benchmark across many venues, which is never identifiable as you.

How fresh is it?

Most systems are read every night, and the pages are rebuilt when the data lands. Weather is live. Every page says when its figures were built.

Do you use AI?

Of course. We use the best tools there are for extracting, transforming and analyzing data: BigQuery and Cloud Run on Google Cloud for the warehouse and the pipelines, Python and SQL for the arithmetic, Gemini on Vertex AI for the language, and AWS S3 for vendor deliveries. The one rule: AI writes the sentences, never the numbers. Every figure you see is computed in code from your own records, and the answer names the system it came from.

What happens to it if I leave?

Your container is deleted, along with everything we computed from it. We don't keep a copy.

Your venue, your questions.

Got a system we haven't seen? Tell us what it is and we'll find the way in.

Book a call Email us

Nothing on the calendar that works? Email us and we'll find a time.