Krenno
All projectsCase study
Web AppiGaming2026webmobile-web

KrBets

Launch a branded sportsbook with live markets, wallets, and operator-grade control.

A white-label sportsbook operators can brand, launch, and run as their own.

Client

KrBets

Engagement

White label product

Krenno roleProduct strategyUX and interface designFull-stack engineeringBetting operations architecture+2 more
Positioning

Why this product exists

KrBets turns sports betting into a deployable product. Operators get a polished betting experience for users and a serious operations platform for leagues, odds, settlement, payments, compliance, and brand — delivered as one white-label system rather than a patchwork of vendors.

KrBets shows that Krenno Labs can design and ship a complete iGaming product, not just a marketing site. The work covers real-time market ingestion, wallet and payment architecture, settlement integrity, compliance workflows, and a white-label admin that operators can actually run. For the next client, it is evidence that Krenno can take a high-stakes consumer product and deliver both the public experience and the operational system behind it.

Built for

  • Sportsbook operators launching or rebranding a betting product
  • iGaming groups that need a white-label sports vertical
  • Entrepreneurs entering regulated or emerging betting markets
  • Operators who want API-fed odds plus manual event control
  • Product owners who need deposits, KYC, referrals, and support in the same platform
The story

Challenge, approach, solution

01

The Challenge

Launching a sportsbook is rarely a front-end problem. Operators need live and upcoming events, dozens of market types, odds that stay trustworthy as prices move, a wallet that never loses a stake, payments that work across fiat and crypto, and an admin team that can open games, declare results, review KYC, and pay winners without relying on engineers. Most betting builds either look commercial and fail operationally, or they are internally capable and impossible to brand. KrBets had to solve both sides of that gap: a product bettors will use, and a system operators can run.

02

Our Approach

Krenno treated KrBets as an operating system for a sportsbook, not a catalog of matches. The public product is organized around sports, leagues, events, and a persistent slip. The backend is organized around ingestion, market state, wallet ledgers, settlement, and operator controls. Odds can arrive from a commercial sports data provider or from the operator's own desk. Every stake writes a transaction, every result moves through a settlement pipeline, and brand, language, currency, and payment methods stay configurable so the same platform can be issued as a new label.

03

The Solution

KrBets is a complete white-label sportsbook. Bettors browse categories and leagues, switch between upcoming and in-play, open full market sheets, and place single or multi bets from a live slip. Operators manage categories, teams, leagues, games, and more than eighty market types, declare outcomes, and settle wins, losses, and refunds through automated jobs. Finance, KYC, referrals, notifications, CMS, SEO, and support sit in the same console, so the product can be launched, branded, and operated as a finished sportsbook.

Experience

The Experience

A bettor arrives on a dark, high-contrast sportsbook: sport categories on one side, league navigation across the top, and event cards in the center showing moneyline, three-way, spread, and totals. They can switch decimal, fractional, or American odds, move from pre-match to in-play, and open a full market page for player props, period markets, outrights, and custom lines. Selections drop into a slip that calculates returns as stakes change. After login — email, mobile, or social — the same person funds a wallet, confirms the bet against current balance, then tracks pending, won, lost, and refunded tickets from an account hub that also holds deposits, withdrawals, referrals, KYC, two-factor security, and support. Operators work a different surface: a command dashboard for bettors, live games, pending outcomes, deposits, and withdrawals, with dedicated desks for leagues, markets, settlement, finance, content, and system configuration.

Product

What we built into the product

White-Label Sportsbook Launch

Operators deploy KrBets as their own brand, with configurable site identity, logo, colors, currency, languages, SEO, legal pages, and frontend content. The betting engine stays shared; the public product looks and reads like a dedicated sportsbook.

Live and Pre-Match Betting

Bettors move between upcoming fixtures and in-play games without leaving the sportsbook. Event cards surface core markets immediately, while a dedicated market view opens the full board for a match.

Deep Market Catalog

The platform supports moneyline, three-way, spreads, totals, outrights, draw-no-bet, both-teams-to-score, exact score, toss winner, team totals, quarter and half markets, innings lines, and a wide set of player props such as points, rebounds, touchdowns, shots, and more.

Single and Multi Bet Slip

A persistent slip lets users add, update, or clear selections, set stakes per selection or across an accumulator, preview potential return, and place the ticket only when balance, limits, and market availability all check out.

Global Odds Presentation

Prices can be shown as decimal, fractional, or American odds. Bookmaker regions can be selected from the US, UK, EU, and AU so the same event can be priced for different operator markets.

Automated Sports Data Ingestion

Scheduled jobs pull leagues, events, and odds from The Odds API, create teams and games, refresh in-play prices, and open fixtures when betting should begin. Operators can also run the same jobs on demand.

Manual Trading Desk

When an operator wants local events, custom markets, or tighter control, they can create categories, teams, leagues, games, and outcomes by hand, lock markets, and declare winners without waiting on an external feed.

Settlement and Outcome Control

Admins declare market results; the platform then settles winning tickets to the wallet, records losses, and refunds voided bets through idempotent settlement jobs with notifications to the bettor.

Wallet, Deposits, and Withdrawals

Every stake, win, refund, deposit, withdrawal, and referral commission writes to a ledger with post-balance history. Operators approve or reject financial requests and configure automatic or manual payment methods.

Global Payment Coverage

The platform includes adapters and instant payment notifications for a wide payment mix, including Stripe, PayPal, Razorpay, Mollie, Flutterwave, Paystack, Authorize.net, Checkout, 2Checkout, Skrill, Perfect Money, SSLCommerz, Paytm, Payeer, Instamojo, Mercado Pago, Aamarpay, Cashmaal, NMI, plus crypto rails such as BTCPay, CoinGate, Coinbase Commerce, CoinPayments, NowPayments, Binance, and Blockchain.

KYC and Account Trust

Operators define dynamic KYC forms, review pending identity submissions, and can require verification before withdrawal. Email, mobile, and Google Authenticator two-factor flows protect accounts, with login history by browser, OS, and country.

Operator Command Center

The admin dashboard concentrates live games, pending bets, pending outcomes, KYC queues, tickets, and deposit or withdrawal volume, with financial trend reporting across chosen date ranges.

Also included

Multi-Level Referral Growth

A configurable referral program pays level-based commissions on deposits, bet placement, and winning tickets, with tracking links, referred-user lists, and commission reporting for both bettors and operators.

Bettor Account Hub

Users manage dashboard balance, bet history by status, deposit and withdrawal history, transactions, profile, password, two-factor settings, KYC status, referrals, and support tickets from a dedicated account area.

Multichannel Notifications

Templated email, SMS, and Firebase push messages cover registration, verification, bets, deposits, withdrawals, and referral commissions, with SendGrid, Mailjet, Twilio, Vonage, MessageBird, and related providers available to the operator.

Localization and SEO Control

Operators add languages and translation keys, configure meta data, sitemaps, and robots rules, and publish news, policy pages, banners, FAQs, and contact content from a frontend manager.

Support, Safety, and Site Operations

In-product support tickets, GDPR cookie consent, captcha, social login, maintenance mode, custom CSS, and extensions such as analytics and live chat give operators the surrounding product surfaces a commercial sportsbook needs.

Gallery

Product surfaces

Visual placeholders mark where final screens and captures will live. Drop assets at the paths shown on each tile.

Engineering

How it's built

KrBets is a modular, API-assisted Laravel application with two primary surfaces and one shared domain. Public traffic hits the sportsbook: categories, leagues, events, market sheets, and a session-backed bet slip. Authenticated bettors then move through wallet, KYC, bet history, and support flows. Operators use a separate admin application to configure brand, ingest or create sports data, open and close games, declare outcomes, and manage finance. Incoming sports data is normalized into Category, League, Team, Game, Market, and Outcome records. A place-bet request validates slip contents, stake limits, and wallet balance, writes a ledger transaction, and stores a Bet with BetItems. Cron jobs keep the catalog fresh, move games into betting windows, refresh in-play odds, and settle wins, losses, and refunds in bounded batches so payout work stays idempotent. Payment providers talk to the platform through a common deposit service and dedicated IPN endpoints, so the wallet does not care which processor funded it.

modularAPI-drivenMVCwhite-labelsecure authledger-basedcron-automatedadapter-based payments

Decision

Keep a shared betting domain with both API-fed and manual event control.

Operators need global coverage and the ability to list local or exclusive events. A feed-only product is brittle; a manual-only product cannot scale.

The same sportsbook can run Premier League prices from a data provider and a regional tournament from the operator's desk.

Decision

Treat the wallet as a ledger, not a mutable display number.

Stakes, winnings, refunds, deposits, withdrawals, and commissions all change money. Each change has to be reconstructable.

Finance disputes and settlement bugs can be traced to a transaction, a remark, and a post-balance.

Decision

Settle results through batched, idempotent cron jobs.

Declaring a winner and paying every ticket in the same request does not survive volume. Settlement has to retry safely.

Payouts scale in controlled batches and will not credit the same winning ticket twice.

Stack

KrBets is a Laravel 11 application on PHP 8.3 with a server-rendered, responsive sportsbook and a modular operations backend. The stack is chosen for financial-grade request handling, a large payment adapter surface, scheduled ingestion and settlement, and white-label configuration that operators can change without a rebuild. It is the architecture of a production sportsbook, not a brochure site with betting screens attached.

Laravel BladeBootstrap 5JavaScript and jQueryViteDynamic Theme EngineLaravel 11PHP 8.3Laravel SanctumLaravel SocialiteMySQL 8 / MariaDBCron-Driven OperationsLaravel Cache and Optimize ControlsProduction Hosting CompatibilityLayered Account SecurityKYC Middleware and Review QueuesHTMLPurifier and Secure File HandlingOperational Audit TrailsThe Odds API
Process

From brief to shipped product

  1. 01Discovery

    The work started from the real operating loop of a sportsbook: how events get listed, how prices stay current, how a stake leaves a wallet, and how a result comes back as a payout. That loop shaped the information architecture for both bettors and operators.

  2. 02Design

    The sportsbook is designed as a three-zone workplace — sports navigation, event board, and slip — so density never becomes noise. The admin follows the same idea: betting, finance, settings, and support are separate desks with queues, counters, and filters.

  3. 03Development

    Engineering centered on a Laravel domain for games, markets, bets, and money, then wrapped that domain with ingestion jobs, payment adapters, notification templates, and a configurable frontend. Manual and API-fed paths write to the same models so the operator never maintains two sportsbooks.

  4. 04Testing

    Critical paths were treated as financial workflows: slip validation, stake limits, insufficient-balance rejection, settlement idempotency, deposit callbacks, KYC gates on withdrawal, and cron logging when a feed or payout job fails.

  5. 05Launch

    The product launches as a complete operator install: sportsbook, admin, cron pipeline, payment methods, brand settings, and documentation for sports configuration, game control, settlement, and finance.

Challenges

Hard problems, clear outcomes

Keeping prices trustworthy without drowning the operator in API cost

Problem

A sportsbook that shows stale odds loses user trust. A sportsbook that refreshes every market, region, and prop without discipline burns quota and still feels slow.

Approach

We separated catalog sync from price sync, split pre-match and in-play refresh, and let operators choose bookmaker regions and market families. Games also have explicit betting windows so the board does not expose events the desk is not ready to trade.

Outcome

Operators get live-feeling prices on the markets they actually offer, with a control surface for cost, coverage, and when a fixture opens.

Settlement that can be trusted like a ledger

Problem

A won ticket has to pay once, a voided ticket has to return the stake, and a lost ticket has to close cleanly — even if a job retries or an admin revisits a result.

Approach

Outcome declaration is separated from cash movement. Win, loss, and refund processors run in bounded batches, mark tickets settled, and skip payouts that already have a matching transaction.

Outcome

The platform can process results continuously without double-crediting wallets, and every payout leaves a reconstructable history.

Market breadth without a chaotic bettor interface

Problem

A competitive sportsbook needs moneyline, spreads, totals, outrights, period lines, and player props. Showing all of that on the home board would make the product unusable.

Approach

Home cards keep the four decisions most bettors make. The full catalog lives one click deeper on a market sheet, with the slip as the constant workspace for building singles and accumulators.

Outcome

KrBets can offer a deep book and still feel like a focused sportsbook rather than a spreadsheet of prices.

White-label delivery without forking the product

Problem

Each operator wants their own brand, currency, language, payment mix, and legal pages. Custom forks would destroy the engineering advantage of a shared betting engine.

Approach

Identity, theme color, CMS, SEO, languages, gateways, KYC fields, and notification templates were designed as configuration. The betting domain stays shared.

Outcome

Krenno can launch another label by configuring the product, not by cloning the codebase.

Proof

What this work proves

KrBets gives an operator a finished sportsbook they can brand and run: live and pre-match betting, a full market catalog, wallet and payment operations, KYC, referrals, and a settlement pipeline that treats money as a ledger. The product demonstrates that Krenno Labs can deliver both the consumer experience and the operational system required to take a betting brand to market.

White-label product designiGaming and sportsbook engineeringReal-time data integrationWallet and ledger architectureMulti-processor payment systemsKYC and trust workflowsAdmin operations designCron and settlement automationMultilingual and SEO productizationResponsive consumer UXFinancial auditabilityHigh-density information architecture

What's next

Intelligent betting guidance

Extend KrBets with recommendation and insight layers that help bettors understand form, price movement, and accumulator construction without changing the core slip and market model they already use.

Risk and liability desk

Add operator views for exposure by event, market, and outcome so trading teams can adjust limits or lock lines with the same authority they already have over games and settlement.

Native companion applications

Carry the existing account, wallet, and slip model into iOS and Android companions so operators can offer a branded mobile sportsbook on top of the current API-ready backend.

Have something in mind?

Tell us about your product and we'll help you ship something worth putting on this page.

→Start a project

Next project

LoveCyc

You’ll never ride alone.

View case study