Client: TradeNest · E-Commerce & Retail · EU B2C marketplace (150 staff)

Reducing Kubernetes Costs for a Marketplace

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

TechSupport Team supported TradeNest’s marketplace on Google Kubernetes Engine. Over five months, the client’s GCP billing records show monthly infrastructure costs falling from $38,000 to $27,000. Deployments rose from one to six per week.

Client and engagement facts

Client
TradeNest
Industry
E-Commerce & Retail
Business context
EU B2C marketplace (150 staff)
Delivery model
DevOps support
Application
B2C marketplace on Kubernetes
Supplied geography
EU
Company size in source
150 staff

Application stack and tools

Application stack

  • Ruby on Rails
  • GKE
  • GCP

Tools used

  • GCP billing
  • GitLab
  • Datadog
  • Terraform

Why Support Was Needed

Three node pools were running at 8% utilization after a migration, and serial CI/CD steps slowed releases. The engineers reviewed capacity and split deployment steps by service tier.

Technical Work

  • Audited Kubernetes node pools, idle volumes and egress patterns.
  • Right-sized node pools based on recorded utilization.
  • Parallelized the CI/CD pipeline across service tiers.

Representative Incident

A GCP pricing change added cost in month three. The team right-sized the pools again within two weeks to partially offset the increase.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Infra cost$38k/mo$27k/mo5 monthsClient GCP billing
Deploy frequency1/wk6/wk/wk5 monthsClient GitLab
Page P952.8 s1.1 ss5 monthsClient Datadog

Evidence and Limitations

The five-month billing comparison includes a provider pricing change. The table shows platform billing and deployment measures for this workload.

Kubernetes Cost Baseline

Three node pools provisioned during a prior migration were running at 8% utilization before right-sizing.

Scope a Similar Engagement

Describe your Kubernetes footprint, utilization and the deployment work that competes for the team’s time. 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.