01Specification
Casino software development
Custom modules, integrations and front-ends on a platform that already works. Most operators do not need a casino built from zero. They need a specific module, front-end or integration that no off-the-shelf product offers. Our custom iGaming development builds that on top of the Platform1 core: a written spec, an estimate you can take elsewhere, and a demo at the end of every sprint.
- Written spec and estimate before any sprint; the spec is yours either way
- Two-week sprints on a staging environment you can log into
- Full custom build: 6–12 months implementation; licence, PSP and studio contracts set the calendar date
- Custom work covered by the same SLA as the platform: 99.9% uptime, 4 hours critical response
Index: What we build · Custom vs configure · Process · The platform core · Integration services · Prefer a call? Book 30 minutes · Request a demo
02What we build
The work that usually lands on our desk.
All of it runs on the same player, wallet and game-round data as the standard platform, so custom work does not create a parallel system to maintain.
New platform modules
Loyalty schemes, agent and sub-agent networks, retail cash-in, custom KYC flows, jurisdiction-specific limits and reporting that the standard modules do not cover.
Bespoke front-ends
A player-facing site or app built to your design on the platform API. Multi-brand, multilingual, with the cashier and account area already handled.
Integrations
PSPs, KYC providers, game studios, sportsbook feeds, CRM and affiliate systems not yet on our list, or legacy systems you cannot replace.
Lobbies and mechanics
Custom game lobbies, tournaments, missions, jackpots and promotional mechanics layered over aggregated content.
Reporting and data
Regulator-specific reports, data-warehouse feeds, finance reconciliation and dashboards for teams that have outgrown exports.
Operator tooling
Internal tools for support, risk, VIP and finance teams: queues, case management, approval workflows and bulk operations.
03Custom vs configure
When custom beats off-the-shelf, and when it does not.
An honest decision guide. Custom code costs money twice: once to build, then every year to maintain. We will tell you when configuration gets you there.
| Situation | Configure the platform | Build custom |
|---|---|---|
| A regulator requires reporting, limits or flows no standard module provides | Not possible by configuration | Custom module, certified where required |
| The feature exists; only wording, layout or rules differ | Configuration ships in days | Not worth the maintenance |
| Your acquisition model depends on agents, retail or a loyalty economy | Standard modules stop short | Custom module on the shared wallet |
| The request comes from a competitor's screenshot, not from your players | Launch first, measure, then decide | Wait for player data |
| You run systems (CRM, finance, warehouse) the platform must fit into | Only if an equivalent provider is already connected | Integration against their API |
| The front-end is the brand and a theme would look like everyone else | Theme gets you live, not distinct | Bespoke front-end on the API |
| Budget covers the build but not the maintenance after launch | Stay on the standard release train | Custom code needs an owner |
| Migrating from a platform with features your players expect to keep | Where the equivalent exists | Rebuild what players will notice |
04Process
Five stages, a demo every sprint.
A full custom build is 6–12 months of implementation. Our implementation time. The calendar date depends on licence approval, your infrastructure readiness and how fast PSP and content contracts are signed. Single modules and integrations are shorter and estimated individually.
Platform1 / your workThird-party contracts: PSPs, studios, licence holder. They set the calendar date
What each stage produces
- Discovery: what the system must do, for whom, and under which licence rules, written down
- Spec and estimate: functional spec, integration map, dated estimate; yours to take to another vendor
- Sprints: working software on staging every two weeks, and a decision on what comes next
How it ends
- Acceptance: UAT against the spec with your team, regression on the rest of the platform, certification support where the regulator requires it
- Launch: scheduled release, documentation, handover
- Support: the custom work covered by the same SLA as the platform: 99.9% uptime, 4 hours critical response
05Engagement models
Three ways to contract the work. One team either way.
Pick by how predictable the scope is. Fixed scope when it is written down; retainer when it keeps changing; an addendum when you are already a client.
Fixed-scope project
A defined spec, a fixed price and a dated plan. Changes go through a written change request so the budget stays predictable.
Best for a new module, a migration, a front-end rebuild.
Retainer
Engineering capacity each month, prioritised by you. Suits operators with a steady stream of smaller requests and integrations.
Best for live brands that keep evolving.
Extend an existing contract
Already on a white label or turnkey agreement? Custom work is added as an addendum, with the same team and SLA.
Best for current clients adding scope.
Third parties
Certification labs, licence fees, PSP and studio onboarding are paid to the provider, not to us, and listed in the scoping document so the total is visible before you sign.
06Typical stack
Chosen for operability rather than fashion.
The exact components depend on where the platform is deployed and what your team can run. These are the typical choices; we document the real ones for your installation at handover.
| Part | Layer | Typical choice | Note |
|---|---|---|---|
| STK-01 | Services | PHP and Node.js services behind a REST API with webhooks for player, wallet, game-round and bonus events. | Typical |
| STK-02 | Transactional data | PostgreSQL or MySQL for accounts, wallets and game rounds; read replicas for reporting. | Typical |
| STK-03 | Cache & queues | Redis for sessions, queues and caching; background workers for payouts, bonuses and exports. | Typical |
| STK-04 | Deployment | Docker images on Kubernetes or managed containers; staging and production separated; releases scheduled with you. | Typical |
| STK-05 | Front-end | Mobile-first web front-ends on the platform API; native wrappers where app stores allow. | Per project |
| STK-06 | Hosting | ISO 27001-certified cloud providers in the EU, or your own cloud account or data centre. | Per route |
| STK-07 | Observability | Central logging, metrics and alerting; 24/7 monitoring under the SLA. | Both routes |
07Questions
Development questions.
The questions we hear on every first call about custom development. If yours is not here, book a 30-minute call and ask the engineers directly.
Book a 30-minute callWho owns the code you write for us?
How long does custom casino software development take?
Can you work alongside our in-house developers?
Do you develop casino games?
How are custom iGaming development projects priced?
08Send the brief
Custom development
Scope & estimate
Describe what you need. Get questions back, then a written scope and estimate.
Describe what you need in a few paragraphs. One form, one engineer, one business day. The reply contains the questions we need answered, then a functional spec, an integration map and a dated estimate with every third-party dependency on it. Reply within one business day, from an engineer; written spec and estimate, yours to take elsewhere; dated plan with every licence, PSP and studio contract on it; NDA on request, no newsletters.
Request a demo Book a call[email protected]