How does ScoreEngine isolate competition data?

ScoreEngine uses a Database-per-Tenant architecture. Every competition (tenant) receives its own physically isolated database, ensuring zero cross-tenant data leakage and maximum performance.

What event formats does ScoreEngine support?

ScoreEngine natively supports dynamic competition builders for combat & sumo brackets, precision maze/obstacle challenges, and time-based trials with flexible age and skill categories.

Event infrastructure

Infrastructure designed around the weak points of a live venue.

ScoreEngine separates referee input, tenant data, public displays and background jobs so a busy spectator view does not become the same problem as a score write.

Compare competition engines→View Case Studies→

System boundaries

Architecture overview

Referee input:Authenticated write path

Competition data:Tenant-isolated schema

Public updates:Realtime event channel

Arena queue:Read-only display view

Connection interruption:Local pending-action queue

Score changes:Named audit records

Referee writes

Authenticated and logged

Tenant data

Separated by competition

Public displays

Read-only event views

Background work

Queued outside score entry

[01] DATABASE SOVEREIGNTY

Isolated Tournament Databases

Every championship instance connects to an independent, isolated database schema. Zero shared tables, zero query contention during peak playoff brackets, and full European data isolation.

ISOLATED SHARDS ARCHITECTURE

TENANT_DB_CHAMPIONSHIP_01 // RO_EU_CLUSTER[ISOLATED]

TENANT_DB_CHAMPIONSHIP_02 // RO_EU_CLUSTER[ISOLATED]

TENANT_DB_CHAMPIONSHIP_03 // RO_EU_CLUSTER[ISOLATED]

[02] WEBSOCKET MESH

Real-Time WebSocket Mesh

Referees record points on their tablets; arena call-up monitors, tournament brackets, and spectators' phones update immediately without page refreshes or polling lag.

EVENT FLOW // REDIS PUB-SUB

REFEREE TAP

0.3ms

REDIS PUSH

0.8ms

CALL-UP SCREEN

1.4ms E2E

[03] RESILIENCE & FALLBACK

Arena Offline Fallback Buffer

Designed for real venues with intermittent Wi-Fi. Local storage buffer queues point updates on referee devices and flushes them securely the moment connectivity resumes without losing a single scoring event.

OFFLINE BUFFER RETRY QUEUE

WI-FI LINK STATUS:[INTERMITTENT]

LOCAL CACHE QUEUE:14 EVENTS ARMED

DATA LOSS RISK:0.00% GUARANTEED

[04] ARENA QUEUE & TOURNAMENT BRACKETS

Automated Brackets & Call-Up Screens

Automatic Swiss, Round-Robin, and Double Elimination bracket draws that seed teams and calculate advancements without spreadsheets. Paired with live arena call-up displays to eliminate match delays entirely.

CALL-UP & BRACKET ENGINE

ACTIVE BOUT // RING 1

Vortex Robotics vs IronClaw

Next up: the scheduled match for Ring 1

BRACKET: SWISS STAGE (ROUND 3/5)AUTO ADVANCE ACTIVE

[ FREQUENTLY ASKED TECHNICAL QUESTIONS ]

Infrastructure FAQ

Referee devices keep pending actions in local browser storage when connectivity is interrupted. The interface identifies unsynchronized work and retries it after the connection returns.