Codelabs — full-cycle engineering company
RU|EN|KK

16+ years · 297 code repositories · systems running right now

Systems that cannot afford a mistake

We are an engineering team. We build and maintain products that must not lose a payment, show a wrong balance or fall over at peak load: payment gateways, crypto exchange, gaming and betting platforms, cash register networks, live video, wearable electronics.

We do the whole chain ourselves — from the circuit board drawing and the firmware inside the device to the servers, the database and the site your customer actually sees. That way no part of the project ends up belonging to nobody.

Member of the Astana Hub international technopark

~1.5M
money operations per day
that is the throughput of a platform we built and maintain
2.18M
players on a single platform
and 1.24M deposits over 30 days
85M+
operations in the crypto gateway
deposits and withdrawals across 10 blockchain networks
16+ years
the team has worked together
the earliest code in our repositories dates back to 2009

Ways to work with us

01

Build a product from scratch

You come with a task and get a working system: design, development, launch, handover to your team. That is how we made a payment gateway, a crypto exchange, a lottery platform, a device for tracking athletes and a dozen other products.

02

Fix and speed up what already runs

The system is slow, loses money or falls over under load — we find the real cause and take the fix all the way into production. One such investigation made bet settlement 15 times faster; another removed 267 double payouts from a platform.

03

Take over the operations

Servers, updates, monitoring, backups, on-call duty during incidents. This is not a side activity for us: we run our own infrastructure for 300+ projects and five independent monitoring systems, and we take every serious incident down to its root cause.

What we do

6 of 11 areas
01

Systems that count money

High-load transactional systems

Wallets, payments, accruals, bets — everything where an error in a single line of code turns into a real loss. We build them so that a payment cannot go through twice and a balance cannot fall below zero, even when thousands of people pay in the very same second. And if an operation gets stuck somewhere between your system and the bank, it will not hang there: the system either drives it to completion or returns the money.

The platform we look after handles about 1.5M money operations per day. After we rewrote payout settlement, 267 double payouts disappeared along with a queue of 437 thousand stuck jobs.

02

Taking and sending money in any form

Payment integration and fintech

We connect your product to whatever your customers actually pay with: bank transfers, mobile money, cryptocurrency, cash over a counter or through a terminal. Every payment provider speaks its own way, and half of them speak a dialect a decade old. For us that is routine. If the market has no suitable gateway, we build our own — ours already has 21 payment systems connected.

More than 20 integrations across the Caribbean, Latin America and the CIS. Plus our own money transfer network: a person hands in cash in one country and the recipient collects it in another with a PIN code.

03

Accepting crypto and turning it into ordinary money

Crypto processing

A client pays you in USDT, bitcoin or another coin — you receive the amount in local currency and never think about the blockchain. The rate is picked automatically from real orders on exchanges, incoming payments are screened for dirty origin, and wallet keys are stored encrypted and decrypted only at the moment of the transfer.

Our gateway works with 10 networks — Ethereum, TRON, Solana, TON, Bitcoin and others. More than 85M operations have gone through it, and the database has grown to 283 GB.

04

Data that updates instantly

Real-time systems and streaming data

Betting odds, market quotes, sensor readings — everything that changes several times a second and has to reach thousands of screens at once. Simply moving the data is not enough here: the numbers must not jump in front of a person, nothing may be lost when the connection drops, and events must not swap places. We wrote such a core from scratch and know where it breaks.

Our core takes a quote stream across 12 sports and distributes it to thousands of browsers at once. It has been in production since 2020.

05

Live video and operating machinery through a browser

Live video and remote equipment control

We show hundreds and thousands of live video streams in a browser — no plugins, with a delay of fractions of a second. Our most vivid project: a person plays a real slot machine from a browser while the machine physically stands in a hall. A tap on the screen reaches the board inside the cabinet and closes a contact, the machine responds, the camera shows the result. The same approach works for any equipment that has to be operated at a distance with the result visible to the eye.

About 1000 connected machines and roughly 2000 simultaneous video streams: a screen and a camera for every cabinet.

06

Electronics: from the board drawing to a finished device

Embedded systems and electronics

We make the hardware end to end instead of assembling a project out of parts made by others: we draw the schematic and the printed board, write the firmware, raise the server the device reports to, and the interface where a person sees that data. Separately we write drivers for industrial machinery — bill acceptors, cash dispensers, receipt printers, card readers.

Our own boards and firmware on ESP32, STM32 and AVR — including a network board for which we had to write our own network stack: the off-the-shelf one did not fit into the microcontroller memory.

Also: Analytics and reporting on large data · Gaming platforms and game mathematics · Mobile applications · Testing and speeding up slow systems · Servers and operations

All 11 services →

What we have already built

5 of 12 cases
CASE 01Turnkey iGaming platform

A gaming platform used by 2 million people

The operator needed not a single game but the entire business: a site for players, a cash desk in physical venues, an admin panel for staff, in-house games, third-party games, payment acceptance, an affiliate programme. We built it as one system — and 15 different brands are launched from that same system, each with its own look, without copying the code for every one of them.

PlatformPaymentsHigh load
Read the case →
  • 2.18M players
  • ~1.5M money operations per day
  • 15 brands from one codebase
  • the database is spread across 13 servers
CASE 03Real-time betting pipeline

Odds that keep up with the match

A bookmaker receives a stream of odds changes across 12 sports. They have to be sorted by match instantly and pushed to every open browser so that nobody sees a stale price and manages to bet on it. We wrote our own core in C++ and our own delivery protocol for this: if a player loses the connection, they get a correctly restored picture rather than garbage.

Real-timeC++Betting
Read the case →
  • 12 sports in one stream
  • in production since 2020
  • the same stream is sold to partners as a separate product
CASE 05Crypto payment gateway

Crypto payments across 10 blockchain networks

The task sounds simple: the client pays in crypto and the business receives money in local currency. Everything else hides behind that simplicity — give every client their own address, spot the incoming payment in the blockchain, wait for confirmations, check where the money came from, calculate the rate and not lose on it. We assembled all of that into one system.

CryptoPaymentsAML screening
Read the case →
  • more than 85M operations
  • 10 networks: Ethereum, TRON, Solana, TON, Bitcoin and others
  • the rate is calculated automatically from orders on exchanges
CASE 06Live video and remote equipment control

Playing a real slot machine from a browser

A person opens the site and sees live video of a real slot machine standing in a hall. They press a button on the screen — and it is pressed on the machine itself: the signal goes from the browser to the server, from the server to the board inside the cabinet, and the board closes the contact. The reels spin, the camera shows the result, the money is counted exactly as it is for a visitor standing in the hall. We did everything here: from the board firmware to the client that shows the video.

VideoElectronicsWebRTC
Read the case →
  • about 1000 machines online
  • 1998 simultaneous video streams
  • our own board and our own firmware inside the machine
CASE 07IoT tracking and local positioning

A sensor on a footballer and a heat map of the pitch

A coach needs to see how far a player ran, where they were on the pitch, how often they accelerated and what is happening to their heart rate. We developed a wearable tag — drew the board ourselves, wrote the firmware ourselves — placed receivers around the stadium and wrote a server that computes every player position from the radio signal. The coach gets a live map of the pitch during the match and heat maps after it.

IoTSportElectronics
Read the case →
  • our own board: radio module, motion sensors, ECG, GPS
  • position is computed from the radio signal of several receivers
  • the charging capsules for the tags are our development too
The other seven are on the cases page.All 12 cases →

What we can build for you

7 areas

These are not finished projects but tasks that map directly onto what has already been built. Each one names what the experience rests on — so you can check it instead of taking our word for it.

01

Analytics on top of a live production database

Reports and dashboards are computed on a separate store that data flows into from the main database. The production system does not slow down while a report is being built, and the history stays for all the years rather than the last ninety days.

Based on — A reporting store of 1.63 billion rows, a change stream out of the production database, reporting across several time zones without shifting the day boundaries.

For whom — Anyone who has outgrown reports that are run overnight straight on the production database.

02

A payment circuit and a wallet inside your service

Taking money through several providers, a user balance inside the service, payouts to contractors and a daily reconciliation. Pressing the button twice does not create a second payment, and an operation stuck between you and the bank does not stay hanging.

Based on — A money core that handles about 1.5M operations per day, with automatic reconciliation of discrepancies.

For whom — Marketplaces, delivery and service platforms, subscription products.

03

A turnkey IoT product: from the board to the dashboard

Schematic and printed board, firmware, radio link, server side, over-the-air updates and a web panel where all of it is visible. One team for the whole chain — no grey zone left between hardware and software.

Based on — A wearable device of our own design: our own board with a radio module, motion sensors, ECG and GPS, with firmware updates that need no visit to the device.

For whom — Manufacturing, agriculture, utilities, cold chain monitoring.

04

Collecting readings from industrial equipment

Meters, controllers, scales and sensors each speak their own protocol. We bring them into one picture with history, thresholds and an alert the moment a reading goes out of range.

Based on — Drivers for industrial peripherals written to the protocol specification, and network controllers on microcontrollers — down to our own network stack on the board.

For whom — Energy metering, utilities, manufacturing.

05

Remote access to a physical object through a browser

Low-latency live video plus control of the real equipment in the frame: inspect the goods, accept the work, start a test bench, bid on a live lot — without travelling there.

Based on — About a thousand devices online and 1998 simultaneous video streams, where a button press in the browser closes a contact on a board inside the cabinet.

For whom — Auctions, remote acceptance, showrooms, equipment servicing.

06

A pipeline for fast-changing prices

A stream of changes is sorted by object and pushed to thousands of open browsers. If a client loses the connection, they get a correctly restored picture rather than fragments, and they never see a price that no longer exists.

Based on — A quote-stream core in C++, in production since 2020: snapshot plus increments, with our own delivery protocol.

For whom — Exchange front-ends, auctions, dynamic pricing, dispatch rooms.

07

Rolling your product out for partners

One codebase, many brands: the look, the domains, the limits and the tariffs are set by configuration rather than by copying the project for every client. An update goes out to everyone at once instead of seven times in a row.

Based on — 15 brands from one codebase on a live platform, with the build and deployment of instances automated.

For whom — Anyone who has started selling their platform to other companies.

What we work with

production experience, not a job-ad checklist
What we write the backend with
The foundation of systems that count money and hold the load.
PHP (Symfony, Laravel, RoadRunner)C++ (Qt, CUDA)Node.js / TypeScriptJava (Spring, Kafka)PythonC (microcontrollers)
What the user sees
Sites, personal accounts, control panels, games in the browser.
ReactReact Router (SSR)Vue / NuxtEffectorTailwindMantine
Where we keep the data
From money operations to archives of billions of rows.
MariaDB / MySQL (Galera)ClickHousePostgreSQLRedisMongoDBMinIO
How we move data instantly
Live updates in the browser and queues between services.
RabbitMQKafkaCentrifugouWebSockets.jsWebSocketin-house TCP / UDP protocols
What we build devices from
Schematic, board, firmware, radio link.
ESP32 (ESP-IDF, FreeRTOS)STM32 (HAL, CubeMX)AVRRaspberry PiKiCad, ProteusUWB (Decawave)
What it all runs on
Servers, automated releases, monitoring, backups.
DockerAnsibleGitLab CInginxZabbixPrometheus / Grafana
The whole stack →

Describe your task — we will tell you what part of it we have already built

Tell us what needs to be done. We will tell you what part of it we have already built and keep running.