01 / The platform
BetSystem CMS separates the customer experience from the core engine. Operators can choose how they build and present their brand while accounts, wallet, betting, games and controls run through the platform API.
Three routes into one platform
Use the existing WordPress and Elementor integration to compose player journeys with platform widgets. Designers shape the experience while accounts, wallet and game decisions stay in the API.
Explore the builder routeUse the browser widget engine in a compatible web page. Choose the functions and presentation your customer needs, backed by the same account and operator platform.
See the delivery toolsBuild a bespoke web or application experience against the versioned API. Kestrel already demonstrates a custom sportsbook without the shared widget engine.
Open the custom API demoWordPress/Elementor is the existing native site-builder integration. Other builders require a compatible HTML/JavaScript embedding route or a bespoke API integration, with hosting, authentication and browser behaviour accepted for that deployment.
Modern architecture, practical value
A brand can change its layout, content hierarchy and customer journey while continuing to call the same account, wallet and game services.
Limits and permissions are checked at the server decision point. A bespoke front end uses the platform’s rules and account records.
Static web delivery, a WordPress integration and application codebases offer several routes for customer experiences. The selected channel has its own acceptance work.
Player journeys and operator administration use connected platform records. Product, trading, support and finance can work from the same account and transaction evidence.
Product architecture
The customer front end renders the platform’s responses. It does not determine the balance, authorise a bet or replace a server-side financial limit. Provider adapters connect the system to external services; a tested interface still needs a contracted, accepted live integration.
The operator proposition
Identity, balances, account history, limits, exclusions and recovery paths provide the account foundation.
Pricing strategies, selections, betting flows, cash-out and exposure management sit behind configurable customer surfaces.
In-house game engines and a seamless-wallet integration route support multiple content strategies, subject to independent approvals.
Tenant policy, player administration, promotions, campaigns and reporting support the daily operator workflow.
Documented APIs let a customer commission a distinctive front end and integration without adopting every bundled screen.
Automated checks, readiness reporting and audit records make the next stage of evaluation concrete.
Where flexibility lives
Brand identity, enabled surfaces, supported features, player policies, content selection and operating workflows. Configuration is subject to the chosen jurisdiction and operator obligations.
Customer-specific integration, migration, additional content, security requirements and new product behaviour. These are estimated and accepted explicitly.
A skin preset is a starting point. It does not determine the customer’s information architecture, acquisition journey or operational model.
Build a demo specificationPortfolio scope
Beavercomps provides raffle and lottery product capability. Starsgames provides free-to-play acquisition and standalone engagement, including fantasy leagues. The platforms can inform future customer propositions, but shared identity, wallet, billing or deployment integration is not represented as completed.
Help take the engine to market
Explore the working engine, meet the team and discuss the investment that advances independent testing and first customer deployments. Bring your questions; we’ll show you the product behind the proposition.