Home / Tribal Gaming

Your data stays on your land.

How Doradus Labs works with tribal Class II and Class III properties.

Every Doradus product runs on the property's own hardware, inside the property's own perimeter. For most buyers that is a security feature. For a tribal operator it is a sovereignty position, and we treat it as one.

Data Sovereignty

Our commitments, in plain terms.

These are policy, not marketing. They apply to every product and every engagement.

  • The tribe owns its data. Everything our products read, compute, or store on your property belongs to the tribe. We claim no license to it, no aggregate rights, no derived datasets. When an engagement ends, the data stays with you.
  • Everything runs inside your perimeter. Our products install on hardware the property controls, on the property's network. There is no cloud tier and no vendor-hosted copy.
  • Nothing leaves without written authorization. No telemetry, no phone-home, no support upload. If we need a log file to diagnose a problem, we ask in writing, and you decide.
  • Your gaming commission can audit what runs. It can inspect what is installed, what it reads, what it writes, and who has touched it. We will walk your regulators through it as often as they ask.
Class II and Class III

Two kinds of floor. We know the difference.

The team behind Doradus has engineered casino IT, security, and surveillance since 2011, and has held master certification on Aristocrat Oasis 360 since 2011. That work covers both operating contexts, and they are not interchangeable.

Class II

Bingo-based games and server-driven floors carry their own math, machine accounting, and federal oversight. Monitoring, reporting, and surveillance coverage all follow from that, and a tool designed only for a compact floor gets it wrong.

Class III

Compact floors answer to the compact's terms and to the tribe's own internal controls at the same time. The details differ property to property, so we start by asking how yours works instead of assuming.

Your Commission

The commission is a counterpart, not an obstacle.

We build to be inspected. Every finding our products produce is explainable: each one can show its evidence. None of our products take automated action against people; findings go to your staff, and your staff decide. Our policy: operate under your internal controls, document our footprint, and complete whatever vendor review your ordinances require.

One more policy: we do not name tribal clients, commissions, or compacts in public.

Procurement

A briefing that respects how you buy.

Tribal procurement is deliberate, and it should be. Our briefing process fits it. A request is confidential by default. You get one written reply from a senior engineer within one business day, and nothing else: no mailing list, no follow-up sequence, no sharing or selling of your information. Steve Golter, founder and senior engineer, answers every briefing request personally.

References are available in private, with the client's permission, never in public. Take the reply to your commission, your council, or your review committee on your own schedule. We will still be here.

The Architecture

On-premise is the sovereignty answer.

All four Doradus products, Doradus Vantage, OptiFloor, Argus, and VaultLine CageOps, run on your hardware, inside your perimeter. That is a design rule, not a pricing tier. Data that never leaves the property never sits in someone else's cloud contract, someone else's jurisdiction, or someone else's breach report. Sovereignty questions get simple when the answer to "where is our data" is a room you hold the keys to.

Doradus Labs is based in Golden, Colorado, serves tribal Class II and Class III properties and commercial casinos, and has been on casino floors since 2011.

Start with a conversation.

Confidential by default. One reply from a senior engineer within one business day. We will explain what runs, where it runs, and what your commission can inspect.