Dench Core · Dedicated infrastructure
Dedicated where the licence asks. Shared where cost decides.
The same platform either way, with high availability, encrypted backups and four disaster-recovery tiers to choose from, under an information security management system certified to ISO/IEC 27001 since 2017.
01 · The back office
The operational side, in the back office.
Three screens from the Management menu, with demo data: the scheduled jobs and their log, which our team runs, and the incident record your team sees. Search the jobs, open a failed run and read its error, log an incident and move it along. The servers underneath have no screen; on a call we open the real back office.
Scheduled Jobs
Monitor system job execution status and schedules
| Executed At | |||||
|---|---|---|---|---|---|
| Bonus Expiry | ✓ Success | 1.84s | 31/10/2026 10:00 | 31/10/2026 10:15 | Every 15 minutes |
| Daily Reports | ✓ Success | 41.27s | 31/10/2026 02:00 | 01/11/2026 02:00 | Daily at 02:00 |
| Exports Cleanup | ✓ Success | 620ms | 31/10/2026 03:30 | 01/11/2026 03:30 | Daily at 03:30 |
| Game Library Sync | ✓ Success | 2m 14.06s | 31/10/2026 04:00 | 01/11/2026 04:00 | Daily at 04:00 |
| Inactive Sessions Cleanup | ✓ Success | 95ms | 31/10/2026 10:12 | 31/10/2026 10:13 | Every minute |
| Inactivity Report 168h | ✓ Success | 8.12s | 31/10/2026 00:00 | 01/11/2026 00:00 | Daily at 00:00 |
| Monthly Wallet Report | ✓ Success | 6m 2.51s | 01/10/2026 01:00 | 01/11/2026 01:00 | Monthly on day 1 at 01:00 |
| Payment Status Sync | ✕ Failed | 30.00s | 31/10/2026 10:10 | 31/10/2026 10:15 | Every 5 minutes |
| Pending Withdrawals Auto Processing | ✓ Success | 3.41s | 31/10/2026 10:10 | 31/10/2026 10:15 | Every 5 minutes |
| No data found for your search criteria | |||||
Scheduled Jobs Log
View historical job execution logs and results
| ID | Name | Status | Execution Time | Execution Duration | Stack Trace |
|---|---|---|---|---|---|
| 482931 | Inactive Sessions Cleanup | ✓ Success | 31/10/2026 10:12 | 95ms | No errors |
| 482930 | Payment Status Sync | ✕ Failed | 31/10/2026 10:10 | 30.00s | |
Run 482930 · Payment Status Sync Payment Status Sync did not complete. Read timed out after 30000 ms waiting for the payment provider’s status response. 3 deposits stay Pending. The next run, at 10:15, checks them again. | |||||
| 482929 | Pending Withdrawals Auto Processing | ✓ Success | 31/10/2026 10:10 | 3.41s | No errors |
| 482927 | Payment Status Sync | ✓ Success | 31/10/2026 10:05 | 1.12s | No errors |
| 482926 | Bonus Expiry | ✓ Success | 31/10/2026 10:00 | 1.84s | No errors |
| 482924 | Payment Status Sync | ✓ Success | 31/10/2026 10:00 | 980ms | No errors |
| 482910 | Game Library Sync | ✓ Success | 31/10/2026 04:00 | 2m 14.06s | No errors |
| 482904 | Exports Cleanup | ✓ Success | 31/10/2026 03:30 | 620ms | No errors |
| 482898 | Daily Reports | ✓ Success | 31/10/2026 02:00 | 41.27s | No errors |
| No scheduled jobs log found on your criteria | |||||
Incident Records
Track and manage system incidents and reports
| ID | Subject | Event Date/Time | Report Date/Time | Reported By | Severity | Status | Affected Service | Attachments | Details | |
|---|---|---|---|---|---|---|---|---|---|---|
| 2041 | Login slowdown at evening peak | 30/10/2026 21:40 | 30/10/2026 21:52 | ops.manager | High | IN PROGRESS | Authentication Service | |||
| 2038 | Replication lag alert on the reporting replica | 27/10/2026 03:12 | 27/10/2026 03:15 | it.support | Medium | RESOLVED | Database Service | |||
| 2033 | Repeated failed logins on a back-office account | 22/10/2026 14:05 | 22/10/2026 14:20 | it.security | High | CLOSED | Authentication Service | |||
| 2029 | Support inbox unreachable for 12 minutes | 18/10/2026 11:02 | 18/10/2026 11:10 | support.lead | Low | CLOSED | Customer Support | None | ||
| No incident records found | ||||||||||
Everything the platform does on a clock, run by our team. Each scheduled job with its last result, how long it took, when it ran and when it runs next, with the schedule in words. Sort by any column, search by name.
Every run, with its result. Each execution of each job, newest first, with its time and its duration. A failed one carries its error, and our team picks it up.
Incidents go on the record, in your back office. What happened and when, who reported it, how severe, which service, and where it stands from Open to Closed. Attachments stay with the record.
02 · Disaster recovery
Four recovery tiers. You choose one.
- 01Backup and RestoreBackups to cloud, replicable to more than one location. Nothing stands by: recovery is a restore.Lowest cost · longest recovery
- 02Pilot LightThe core services always running and syncing the data that changes. The rest of the environment is provisioned around them when the plan is invoked.Costs more · recovers much faster
- 03Warm StandbyA scaled-down but fully working copy of the environment, always running.For high-scale operators who carry the cost
- 04Multi-SiteCloud and on-site infrastructure, active-active.Most cost · our dedicated DevOps team
They cost different amounts and recover at different speeds. The recovery objective is set per tier and per engagement.
03 · Standard, and ours
Every platform keeps backups. Here is what you decide on this one.
Standard. Here too.
- Every service on at least two nodes
- PostgreSQL primary and hot-standby replica on separate servers
- Synchronous replication, write-ahead logs synced in real time
- Encrypted full backups, kept offsite and checked for consistency
- Monitoring that escalates by email, SMS and phone
- Restores under a business continuity plan
- Hosting, releases, monitoring and support, run by us
Different here.
- Dedicated or shared is a cost decision, not a lesser platform.
Dedicated is your own environment and your own database, on dedicated hardware, virtual servers or cloud. Shared is the same platform at a lower cost. Where it runs changes; the high availability, the backups and the back office do not.
- Your data leaves in the format you choose.
Every list in the back office exports to CSV, XML or JSON. Reporting →
- The operational record is in the back office.
Our team runs the scheduled jobs and watches every run. Your team sees the incident record in the Management menu, beside the audit trail: what happened, how severe, and where it stands.
04 · The record
Ten years, measured.
Ran on it
- 138.comUnited Kingdom, 2017 to 2020, under our UK Gambling Commission licence.
- Bet99Canada from 2020, licensed in Ontario when the regulated market opened.
- KlondaikaLatvia, the full platform including CRM, until Entain acquired it in 2022.
- GGPokerA global poker brand, on the platform in 2019.
Running on it now
- Spins.lvLatvia
- EverbetBulgaria
- SlotinoBulgaria, the brand we built and ran ourselves
- AladinsBulgaria
- QbetBulgaria
- Slots99Canada, Europe and Latin America
- ISO/IEC 27001 since 2017
- UKGC licensed software supplier
- GLI certified in three jurisdictions
- Bulgarian manufacturer licence
05 · How it is bought
Four ways to take it. One price list.
Platform
You hold the licence and run the operation: marketing, support, payments relationships, compliance. We deliver and run the technology: the platform with its CRM and gamification suite, integrations, front end, hosting, releases, support. Your provider contracts or ours.
Enterprise
The platform built out to your market and your specification: dedicated environment, custom front end, features against your requirements. The way the largest accounts have been delivered for ten years.
White label
Our infrastructure end to end, run under the group’s Curaçao setup: licensing, provider contracts, payments. You bring the brand and the marketing.
Giselle Cloud
The engagement suite, journeys, loyalty, jackpots, tournaments, bonusing and the analyst, on the platform you already run.
A platform fee, a revenue share, and one-off costs for integrations and environment setup.
The mix moves with volume, and we are flexible on the model depending on the case and the size of the operation. The platform comes whole: the CRM and gamification suite and every module are in it, not a lighter edition.
To quote, we need four things
- The market you want to launch in.
- What you run on today, if anything.
- Whether the licence exists, is pending, or is the question.
- The studios and payment methods your players expect.
06 · Asked first
The three questions that arrive before the demo.
Do we need a dedicated environment?
Where a regulator or your own policy has a view on where player data sits, or needs isolation to be a fact of the architecture, yes: your own environment and your own database. Where neither does, shared runs the same platform at a lower cost, and most of the choice comes down to cost.
Dedicated costs more and takes longer to stand up than shared. In most markets the licence is still the long pole.
What are the recovery objectives?
They are set per tier and per engagement, because a single-region deployment and a hot standby do not recover the same way. Tell us the tier, or the requirement you have to meet, and we tell you the objective for it, in writing.
How far back do the backups go?
Encrypted full database backups and write-ahead logs are kept at 24-hour, 7-day, 30-day, 6-month and 1-year granularity, and synchronised offsite to a dedicated cloud bucket. Once two higher granularities exist, the redundant lower backup is erased.
The backups themselves are checked for consistency.
Tell us your recovery requirement. We send back the shape and the tier.
The market, what your licence or your policy says about where player data sits, and how fast you need to be back after a failure. It comes back as dedicated or shared, the tier, and the objective for it.