MASOUD BAHRAMIPRODUCT / FULL-STACK / AUTOMATION
CASE / 025Gaming and competition platform rebuild

TORNOLANDTornoland

Rebuilt Tornoland's existing backend on self-hosted PostgreSQL, reconciling wallet, withdrawal, referral and competition rules. The engagement covered preserving the existing game catalogue, reconstructing server logic and launching the platform publicly, connecting financial workflows with competition management.

View projectDiscuss a project
My responsibilityBackend rebuild, catalogue migration and deployment
StatusLive; payment gateway, SMS and email integrations pending
AccessPublic platform and administration
ProductIndependent competition and financial backend
PUBLIC WEBSITE / OCT 2026TORNOLAND
Tornoland homepage introducing tournaments and game selection.
Public project view

Public homepage of the Tornoland gaming tournament platform.

Starting pointThe client's existing platform codebase
Data and serverSelf-hosted PostgreSQL
Product rulesWallets, withdrawals, referrals and competitions
MigrationPreserved the existing game catalogue
PRODUCT WORKFLOW

The product workflow

  1. 01 / 04

    Understand the existing platform

    The existing code, database and business rules informed the rebuild so product behaviour could be preserved.

  2. 02 / 04

    Rebuild the server layer

    Authentication, registration, administration and competition operations were connected to the independent backend.

  3. 03 / 04

    Reconcile finance and competition

    Deposit recording and approval, wallets, withdrawals and prizes were reconciled with competition and referral rules.

  4. 04 / 04

    Migrate and launch

    The existing game catalogue was transferred to the new infrastructure and the public platform launched with backups.

SCOPE & DESIGN

Scope and key decisions

  1. 01

    Rebuild an existing product while preserving continuity

    Tornoland came into the engagement as an existing codebase. I reviewed its structure, rebuilt the backend and moved it to independent infrastructure while preserving the game catalogue and aligning server behaviour with the product's actual rules.

  2. 02

    Connect competition and financial rules

    Wallets, bank-transfer recording and approval, withdrawals, prizes and referrals are tied to the competition lifecycle. I rebuilt these operations on PostgreSQL so user requests, administrator review and the financial effect of each action remain connected.

  3. 03

    Independent deployment and delivery scope

    The public platform launched with an independent backend and new database. Infrastructure, authentication, access control and backups are part of the delivery; online payment, SMS and email integrations remain part of the project's next connection phase.

PRODUCT COMPONENTS

Product components

  1. 01Rebuilt the existing platform's backend
  2. 02Independent PostgreSQL database
  3. 03Wallet, withdrawal, referral and prize rules
  4. 04Migration and preservation of the game catalogue
  5. 05Public deployment and backups

Let’s discuss your project.

Describe the problem and scope so we can work out how to design and build it.

Talk on Telegram