Client: RiverCard · iGaming & Betting · Gibraltar online poker network

Reducing Failed Releases for Online Poker

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supported the deployment pipeline of RiverCard’s C++ and Erlang poker platform. Over four months, the client’s GitLab CI records show failed releases falling from 24% to 9%. Release approval stayed with the client’s engineering lead.

Client and engagement facts

Client
RiverCard
Industry
iGaming & Betting
Business context
Gibraltar online poker network
Delivery model
DevOps support
Application
Poker platform with tournament scheduler
Supplied geography
Gibraltar

Application stack and tools

Application stack

  • C++/Erlang
  • Docker
  • Kubernetes
  • Terraform

Tools used

  • GitLab CI
  • Prometheus
  • Argo CD

Why Support Was Needed

A scheduler release interrupted play for 3,200 users. Deployment instructions lived in an unmaintained wiki, and engineers lacked a consistent first check when a release failed.

Technical Work

  • Converted wiki instructions into deployment runbooks with ordered first checks.
  • Validated the runbooks in a production-like staging cluster for one week.
  • Added pre-deployment checks for container image tags and Kubernetes ConfigMaps.

Representative Incident

The first release after the pipeline migration failed on a hard-coded image tag. The team reproduced the failure in staging and added the condition to the pre-deployment checklist. The next ten deployments completed without rollback.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Failed releases24%9%%4 monthsClient GitLab CI; Scope: One release failure during a cloud-region outage was excluded.
MTTR52 min16 minmin4 monthsClient Prometheus
Deploys/week294 monthsClient ArgoCD

Evidence and Limitations

The comparison covers four months. One release failure during a cloud-region outage was excluded.

Release Approval

TechSupport Team prepared and tested the deployment runbooks. RiverCard’s engineering lead approved each production release.

Scope a Similar Engagement

Share a recent release failure, your CI/CD setup and who approves production changes. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.