What do our Kubernetes services include?

We design and run GitOps delivery on Kubernetes: Argo CD applications, promotion from dev to production, verification gates and database migrations that run inside the release. The CI/CD & IaC package builds or re-architects your pipelines and infrastructure as code for USD 4,000, fixed, in 2 weeks. If you also want a developer portal on top, IDP Foundations is USD 5,000 for 2 weeks.

GitOps means the cluster is changed by what is merged, not by someone typing commands. Promotion, checks and rollback then follow the same path every time.

What you get, step by step

Everything in the package, in the order it lands. The price and the duration stay the same.

  1. Step 1: Pipelines

    Build or re-architect your CI/CD pipelines.

  2. Step 2: Infrastructure

    Build or re-architect your infrastructure as code.

  3. 2 weeks

    USD 4,000

Want to keep going after the package? Add engineers by the hour at the published rates, with a 6-month minimum term. How staff augmentation works.

How do releases move from dev to production on AWS EKS?

For a fintech portfolio-analytics SaaS platform, with separate dev and prod accounts on AWS EKS, releases are promoted with Kargo on Argo CD:

  • Dev deploys happen automatically, followed by a 1-hour soak.
  • Verification gates run before production: edge smoke checks, pod-restart and readiness checks, and an HTTP 5xx-ratio gate.
  • Migrations run in a pre-sync hook, with an automatic database snapshot taken first.
  • Rollback is a re-promotion of the previous version. It was rehearsed in dev only: 72 s back, 124 s forward.
  • The first production release through the new pipeline had all 12 running service images verified to match the release (October 2026).
  • Seven manual steps and a certification checklist were replaced by one action.

Prefer to pay by the hour?

Add engineers to your own team at the published rates instead of buying a package.

  • You interviewYou meet the engineer who will do the work.
  • 6-month minimumBilled per hour worked.
  • Free replacementIf they leave or don't fit, we replace them and cover the handover at no cost.
See how staff augmentation works
  • Lead / ArchitectUSD55–⁠60per hour
  • SeniorUSD45–⁠50per hour
  • MidUSD35–⁠40per hour
  • JuniorUSD30per hour

USD per hour, drawn to one scale

Frequently asked questions

What is Argo CD used for?

Argo CD is a GitOps tool: it keeps what runs in a Kubernetes cluster equal to what is written in Git, and shows when the two differ. At the transportation company it manages 101 applications.

What does Kargo add to Argo CD?

Kargo promotes a release from one stage to the next, for example dev to production, and runs checks between them. At the fintech platform it promotes after a 1-hour soak and verification gates.

Can you roll back a bad release?

Rollback is a re-promotion of the previous version. We rehearsed it in dev only at the fintech platform: 72 s back, 124 s forward. We do not publish a production rollback time.

How do database migrations fit into a release?

They run in a pre-sync hook, with an automatic database snapshot taken before each migration.

How much does a GitOps pipeline cost?

CI/CD & IaC is USD 4,000, fixed price, 2 weeks. With a developer portal on top, IDP Foundations is USD 5,000 for 2 weeks.

Which clouds have you run Kubernetes on?

AWS EKS at the fintech platform and a major cloud at the transportation company. Our own AI marketing platform runs on Google Cloud with Cloud Run.

Can I add DevOps engineers to my team by the hour?

Yes, with staff augmentation: USD 55–⁠60 an hour for a Lead or Architect, 45–⁠50 Senior, 35–⁠40 Mid and 30 Junior, with a 6-month minimum.

Do you work in English, Spanish or Portuguese?

Both, 100% of the time. You interview the engineer who will do the work.

What changed once releases went through the pipeline?

At the fintech platform, production releases went from 1.15 a week (April to July 2026) to 3.7–⁠4.0 a week over the last 30 days, about 3x. Production release failures went from 23% of runs overall to 4% since July 2026, and the median time from merge to production went from over a week to a few days.

These figures describe the platform we work on, alongside its own developers. We do not publish a production rollback time or a cost saving for this engagement.

What does Argo CD look like across several clusters?

A US transportation services company runs 150+ active repositories on multi-cluster Kubernetes on a major cloud. Our platform team of 6 has worked there since December 2025:

  • Argo CD grew from 46 to 101 applications and from 8 to 29 application sets, with a management cluster added in April 2026.
  • Build-once image promotion went from 4 to 31+ repositories.
  • Shared CI went from 35 to 76+ repositories, with 9 new reusable workflows.
  • 17 repositories now run on the release-branch model.

Tell us your case.

We reply to every request within 1 business day. We sign an NDA before the call if you ask.