EarnBrawl Ops Stack
Operator-ready Brawl Stars tournament backend

Detailed one-page brief for teams that want tournament operations without building from scratch

EarnBrawl centralizes onboarding, matchmaking, dispute handling, wallet accounting, and payout operations inside one production-oriented workflow built for Telegram-native tournament ecosystems.

Request Async Review Pack Review package options
Async Python runtime Webhook signature checks Structured test suite Config-driven payouts Staff moderation workflows

Async-first process. Documentation and visuals are shared by email or Telegram, no live call required.

Business context

Community tournaments usually start with manual operations and then hit scale limits. This product targets that transition point with a structured and auditable ops layer.

Typical manual setup
  • Spreadsheet-based queue and payout tracking
  • Inconsistent host and readiness handling
  • Ad-hoc dispute resolution with low traceability
  • High admin effort for recurring events
With EarnBrawl infrastructure
  • Structured queue-to-match orchestration
  • Defined report and moderation workflows
  • Wallet and payout accounting consistency
  • Operational controls for staff and admins

End-to-end operational flow

From first user interaction to resolved settlement in six practical stages.

1

Onboarding

User starts in Telegram, selects language, accepts terms, and enters guided setup.

2

Profile link

Brawl Stars profile is linked and validated through OCR-assisted and API-backed checks.

3

Queue and match

Users enter buy-in queue; system orchestrates match groups and tracks readiness state.

4

Session control

Host and players move through controlled lifecycle states with timeout and error paths.

5

Disputes

Reports are submitted, reviewed by staff, and resolved with structured actions.

6

Settlement

Wallet updates, fee logic, and payout accounting are applied with auditable records.

Architecture at a glance

A compact visual model of runtime components and data flow.

Operational readiness and control points

Built to support recurring tournament operations with clearer governance and lower manual load.

Integrity safeguards

  • Webhook signature validation and source checks
  • Controlled flow transitions for match lifecycle
  • Event and transaction traceability across key actions

Staff governance

  • Structured dispute intake and resolution workflow
  • Role-based staff and admin operational controls
  • Penalty and moderation pathways for repeated abuse

Production baseline

  • Async runtime with isolated webhook surface
  • Schema-backed persistence for core state
  • Config-driven payout and fee behavior

Integration surface

Key external and internal interfaces that make the stack operator-ready.

Telegram Bot API

Primary runtime interface for player, staff, and admin interaction flows.

Role: user operations interface

Brawl Stars API

Validation layer for game profile and result consistency checks.

Role: gameplay verification signal

Google Vision OCR

OCR-assisted extraction pipeline used in profile linking workflows.

Role: onboarding automation

WooCommerce Webhooks

Order-status event ingestion with signature checks for financial triggers.

Role: payment event bridge

MariaDB / MySQL

Persistent state for users, wallets, matches, reports, settings, and events.

Role: core operational persistence

YAML payout config

Fee tiers and payout behavior managed through configurable rules.

Role: business rule configurability

Capability matrix

Operational modules mapped to buyer outcomes.

Layer Included Business outcome Current status
Tournament flow Queue, match lifecycle, host/player readiness, timeout logic Lower manual coordination effort Ready
Dispute and moderation Report intake, staff actions, escalation and traceability Higher player trust and cleaner governance Ready
Wallet and settlement Multi-balance accounting, fee rules, payout distribution Consistent financial operations Ready
Payments Webhook validation, order ingestion, settlement triggers Reliable event-driven deposit flow Ready
Admin operations Staff/admin controls, management workflows, logs Faster intervention and oversight Ready

Deal structure and delivery

Simple package options with predictable handover milestones.

Package A - Asset Only

EUR 9,900 equivalent

  • Source snapshot transfer
  • Database schema and payout configuration
  • Documentation set
  • 90-minute handover + 60-minute async Q and A
Best for fast internal integration No recurring fee

Package B - Asset + Transition

EUR 14,900 equivalent

  • Everything in Package A
  • 30-day transition support window
  • Weekly sync and async blocker support
  • Deployment runbook alignment
Best for operational go-live support Structured post-transfer path

Payment options

  • Fiat: 70% signature / 30% acceptance
  • Stablecoin: upfront or escrow split
  • Network and transfer fees on buyer side

Delivery milestones

  • M1: signature and upfront confirmed
  • M2: repository transfer initiated
  • M3: handover completed
  • M4: acceptance and final release

Due diligence pack

  • Architecture and product one pager
  • Schema and payout configuration
  • Technical and workflow notes
  • Commercial terms draft

Scope boundary: this offer covers technical tournament infrastructure only. Jurisdiction-specific legal, licensing, KYC/AML, tax, and consumer-law compliance remain under buyer responsibility.

Post-transfer execution path

A practical transition sequence to reduce onboarding friction after acquisition.

Phase 1 - Access and orientation

Day 1-3
  • Repository and document transfer
  • Architecture walkthrough and environment map
  • Key operational assumptions clarified

Phase 2 - Technical alignment

Week 1-2
  • Deployment baseline and configuration alignment
  • Payment and moderation flow verification
  • Priority backlog for buyer-specific adjustments

Phase 3 - Operational readiness

Week 3-4
  • Staff/admin workflow rehearsal
  • Dispute and settlement edge-case checks
  • Go-live handoff and support closure

FAQ

Is this sold as SaaS access or code transfer?

Current commercial model is one-time code transfer with optional transition support.

Can this be reviewed without meetings?

Yes. The full review process is async via documents, visuals, and written Q and A.

Can payment be handled in crypto?

Yes. Stablecoin settlement can be arranged upfront or via escrow milestones.

What happens after transfer?

Either handover only (Package A) or 30-day transition support (Package B), depending on selected scope.

Is source code shared before commercial commitment?

Pre-signature review uses documentation, visuals, and structured due-diligence material. Full source transfer is milestone-based.

Can the stack be adapted to another game or market?

Yes. The core operational model is modular enough for adaptation, with integration and policy work handled in buyer scope.

Request the async pack

Share your target market, expected event volume, and preferred package. You will receive a structured review bundle with product details, visuals, and commercial terms.

Email: brandogiuffrida@protonmail.com Telegram: @brandodev
What you receive in the async pack
  • Commercial one pager and package summary
  • Architecture and workflow visual set
  • Deal and milestone template
  • Due-diligence document checklist

Typical first response window: within 24 hours.