Cloud infrastructure for web studios and software teams
DevOps for studios and software teams/AWS · Kubernetes · CI/CD

Infrastructure your clients never have to think about.

I take hosting, deploys, backups and monitoring off your developers. Senior DevOps, 5+ years on banking infrastructure for 20M+ customers, now working directly with studios and software teams.

banking infra in production
5+ yrs
customers on the systems I worked on
20M+
read-only infra check
48h
admin access needed to start
0
A client project, coveredGo-live checklist
Environments
Staging and production, separate
Deploys
CI/CD with a rollback you have tried
Backups
Automatic, with a tested restore
Monitoring
Alerts that reach a real person
Access
No shared admin accounts, MFA on
Handover
Runbook and a clear owner

Stack

  • AWS
  • Kubernetes
  • Terraform
  • Helm
  • ArgoCD
  • GitOps
  • Prometheus
  • Grafana

01 — What I do

Four ways I take infrastructure off your team.

A read-only look at one client project, before something breaks.

I get read-only access to your cloud account and pipeline. I go through access, environments, deploys, backups, monitoring, security basics and cost, then write a short report: what I found, how risky it is, what to fix first. The scope is fixed, nothing in your account is changed, and the report is yours whether we work together or not.

Best for

Studios with a live client project nobody has looked at for a while, or a launch coming up.

  • Read-only
  • Short report
  • AWS
  • Security basics

Production-ready infrastructure for a client project, the same way every time.

Staging and production environments, infrastructure as code with Terraform, CI/CD with rollback, backups with a tested restore, monitoring and alerts, and a runbook for the handover. One fixed scope per project, so the tenth launch is not hand-built like the first.

Best for

Studios that launch client apps regularly and have no DevOps engineer in the team.

  • Terraform
  • CI/CD
  • Backups
  • Monitoring

Someone to call when the app is down, so it is not your lead developer.

Monthly support for live client projects: updates, backup checks, monitoring, incident response during working hours, and a short cost review every month. No 24/7 promise to start with. Response times are agreed per project.

Best for

Studios that host or maintain apps for clients and want to stop being the on-call for infrastructure.

  • Maintenance
  • Incident response
  • Cost review

From a hand-built server to something you can rebuild.

Move an app from a single server or an old setup to AWS or Kubernetes, with a plan for downtime, rollback and cost. Or go through an existing cloud bill and find what you pay for but do not use. I give you a number after looking at the data, not before.

Best for

Teams with an app on one server that only one person understands, or a cloud bill nobody has read.

  • AWS
  • Kubernetes
  • Migration
  • Cost review
Production data center server racks

02 — Background

Banking-grade habits for client projects.

I do not have a studio case study to show yet, and I would rather say so. What I have is five years of production at national scale and a short checklist you can use today.

001

PrivatBank: production infrastructure at national scale

Senior DevOps, 5+ years

Production infrastructure for a bank with more than 20 million customers: Kubernetes, CI/CD, observability, and the discipline of changing live systems without breaking them. I bring the same habits to smaller client projects: separate environments, deploys with rollback, backups that were actually restored, alerts that reach a real person.

customers
20M+
in production
5y+
  • Kubernetes
  • AWS
  • Terraform
  • Prometheus
  • Grafana
  • ArgoCD

002

Go-live checklist (free, one page)

use it today

What I go through before an app goes to production: access, deploys, backups, monitoring, security basics, cost, handover. Take it for your next launch. No email needed.

Open the checklist
  • Checklist
  • Launch
  • Handover

03 — About

One engineer who has run production, not an agency layer.

I spent more than five years in DevOps at PrivatBank, keeping production running for 20 million bank customers. Client apps are smaller, but the failure modes are familiar: a deploy nobody can roll back, a backup nobody has restored, a server that only one person understands.

When I open a client's cloud account I am not running a scanner and reading the output. I look for what I used to fix in banking: shared admin accounts, backups that were never restored, no alerts, everything on one server.

I started OneX Systems to take that work off small teams that build software for clients and do not have a DevOps engineer.

LinkedIn profile

04 — Engagement

From a 15-minute call to a working setup.

  1. 0115 minutes

    15-minute intro

    You tell me about your projects and how infrastructure works today. No slides, no sales deck. We decide together if a check makes sense.

  2. 0248 hours

    Infra Check 48h

    A read-only look at one project, then a short report with findings, risk and a fix order. Nothing in your account is changed.

  3. 03project or monthly

    Launch Kit or Care Plan

    If the report shows work worth doing, we agree scope and price before anything starts. Your accounts, your repositories, you own everything.

05 — Quick check

A 30-second read on your delivery setup.

Four questions. A suggested starting point. No email required to see it.

diagnostic01 / 04

How are your client projects set up?

06 — Questions

Questions we get every time.

OneX Systems

07 — Start

Tell me what you are running.

Client apps, hosting, deploys, backups. A 15-minute intro, read-only, no admin access, no load on your developers. You get a concrete assessment, not a generic deck.

Reply within 24 hours