About

Who you're hiring

Veliz is two cloud engineers, not an agency with a bench and a project manager between you and the work.

01 — Who you're hiring

Two engineers. One surname. No account team.

Veliz is two cloud engineers, not an agency with a bench and a project manager between you and the work. You get both of us on the engagement, and the person who writes a finding is never the person who signs off on it.

Nothing ships unreviewed

Every finding is checked by the engineer who didn't write it before it reaches your report. A finding that doesn't survive your own console check discounts every other page — so we check it first.

No single point of failure

An engagement doesn't stall because one person is on-call, ill, or on a plane. That matters when the deliverable has a date and your security team cleared a window for it.

Triage is the slow part, and it parallelises

Collection is automated; filtering false positives and adding business context is not. Two people reading the same estate is how a fifty-account organization still finishes in a week.

Still not an AWS partner

Neither of us resells AWS. No reseller margin, no credits to burn, and nothing to gain from recommending you buy more of anything. Doubling the engineers doesn't change that.

JV

Joaquin Veliz

Senior DevOps / SRE · Córdoba, AR

LinkedIn ↗

Eight years running production cloud infrastructure. Currently owns reliability, observability and cost for a multi-region email-security detection platform — Go and Java microservices across AWS EKS and Azure AKS, including restricted federal compliance environments. Cut roughly 40% of the infrastructure cost on a production data platform by migrating it to Graviton.

That day job is the reason this offering exists: it is a week-by-week tour of the exact failure modes the audit looks for — the disk watermark that silently blocked writes, the promotion script blind to multi-arch manifests, the indexing lag no error-rate alert would ever have surfaced. He wrote the audit tool because he wanted it, then found other people needed it more.

  • SAASolutions Architect
  • SOASysOps Administrator
  • DVADeveloper

Production infrastructure run

  • ProofpointEmail security · multi-region EKS & AKS, FedRAMP
  • AllataMulti-account landing zone, AWS Control Tower, governance
  • CoderhouseLegacy → EKS migration, VPN, platform automation
  • CencosudOrg-wide observability for a top-3 LatAm retail group
  • McAfeeSelf-managed K8s → EKS, DevSecOps pipelines, 4 regions
  • GlobantFintech core microservices, IBM Cloud → AWS
GV

Gonzalo Veliz

DevOps / SRE Engineer · Argentina

LinkedIn ↗

Six years across AWS, Azure and GCP. Currently DevOps Engineer at Wayni, where he is unwinding a seven-year-old Kubernetes delivery model — migrating 30+ .NET, NestJS and PHP services off Terraform-managed resources onto a centralized Helm strategy, and centralizing observability in ELK behind a standardized P0–PX alert severity model.

He also consults for Traxión, where the engagement started exactly the way ours does: he audited the AWS estate, then led the optimization programme that came out of it — more than US$7,000 a year of spend removed. Before that, airline-scale CI/CD and DevSecOps at Aeroméxico, multi-cloud event infrastructure at Asdeporte built to survive registration peaks, and a multi-cloud wallet platform across AWS and GCP.

  • AWS · Azure · GCP
  • Kubernetes & Helm
  • FinOps
  • Observability
  • DevSecOps

Production infrastructure run

  • WayniCloud-native fintech · 30+ services, Terraform → Helm, ELK
  • TraxiónAWS cost audit and optimization · consulting engagement
  • AeroméxicoAirline workloads · CodePipeline, Argo CD, ECS Fargate
  • AsdeporteHigh-concurrency events · Azure AKS & AWS, Grafana
  • RegcheqFintech observability · Datadog across EC2, ECS, EKS
  • E-WalletFintech · multi-cloud AWS + GCP, Terraform, Harness

Most of the companies above are employers, not clients. Two are not: Traxión and Regcheq were consulting engagements, and the AWS audit and cost programme Gonzalo ran at Traxión is the closest either of us has come to delivering this exact work for a paying client. What we do not have yet is a completed engagement under this name, with this tooling, and a client willing to be quoted on it — which is precisely what the pilot tier is for, and why it is capped at three.

Book a scoping call See the pilot terms

Let's find out what's in there.

Book a scoping call