Skip to content
lastdevops

Infrastructure audit in 3–5 days

We review reliability, security, delivery, backups and cost, rank the risks and give you a plan. The report is yours to keep, whether or not you continue with us.

Talk to an engineerGet a free review

An engineer replies, not a salesperson — within one business day.

  • 3–5 business days
  • Read-only access
  • Risks ranked by impact
  • The report is yours

Official cloud partners

  • Yandex Cloud
  • Selectel
  • Timeweb Cloud
among our clients
  • Novotek
  • RZD
  • SberCorus
  • Otus
  • Besttrip
  • JedAI
  • IMSystems
  • Builddocs
  • Headframe
  • RTDS
Case studies →
symptoms.log

When teams come to us

Nobody has the full picture

The infrastructure grew over years, and how it fits together lives in a few heads.

You inherited it

A previous vendor or a departing engineer left, and you need to know what you now own.

Something already broke

After an outage you want to find the next single point of failure before it finds you.

Before a big change

A migration, a funding round or an enterprise deal — you need to know where you stand.

scope.md

What we do

Reliability

Single points of failure, zones, failover and how recovery would actually go.

Backups and DR

What is backed up, where, and whether anyone has restored from it.

Security basics

Access, secrets, exposed services and how changes reach production.

Delivery

CI/CD, environments and how long it takes to ship and roll back a change.

Observability

Whether you would notice an incident before your customers do.

Cost

Where cloud spend goes and which resources sit idle.

What you keep

  • Written report with the current state
  • Risk register ranked by impact
  • Roadmap with estimates
  • A walkthrough call with your team

Stack

  • Kubernetes
  • Terraform
  • CI/CD
  • Prometheus
  • Backups
  • IAM
git log --cases

Similar problems we have solved

All case studies
Industrial

Novotek

Infrastructure had grown ad hoc: configuration lived on the servers, and changes could not be tracked or reproduced.

  • Described the infrastructure as code, so it is reproducible and goes through review
  • Separated development, testing and production environments
  • Introduced monitoring and an incident response procedure
Transportation

RZD

Strict continuity requirements: services cannot be stopped, and problems must be visible before users notice them.

  • Rebuilt the setup for fault tolerance with no single points of failure
  • Set up metrics, logs and meaningful SLI/SLO-based alerts
  • Organized on-call rotations and incident reviews
Telecom

RTDS

Some incidents were reported by users rather than caught by monitoring.

  • Introduced metrics, logs and traces with alerts on business-critical flows
  • Organized 24/7 on-call and incident response
  • Introduced incident reviews that fix root causes, not symptoms

TEAM.md

Who will work on your project

There are three of us, by design: the engineers you talk to are the engineers who do the work. No account managers, no hand-offs.

  • Alexander Kaloshin — Co-founder

    Alexander Kaloshin

    Co-founder

    20+ years in IT. In 2014 he founded Last.Backend, a container orchestrator built at almost the same time as Kubernetes. Leads our AI practice.

    • Last.Backend: container management and DevOps as a service
    • Fault-tolerant infrastructure: Kubernetes, CI/CD, bare metal
    • Go engineering
    • Speaker at ProIT Fest and GolangConf
  • Alexander Tikhomirov — Co-founder

    Alexander Tikhomirov

    Co-founder

    7 years in DevOps and dozens of delivered projects, from a first pipeline to production under heavy load.

    • Infrastructure design and operations
    • Cloud migrations and greenfield builds
    • CI/CD, Kubernetes, infrastructure as code
  • Denis Gerasimov — Co-founder

    Denis Gerasimov

    Co-founder

    5 years in DevOps. Takes on the hardest problems and sees them through.

    • Complex infrastructure projects
    • Monitoring, on-call and incident response
    • Operations automation
FAQ.md

FAQ

What do you need from us?
Read-only access to the infrastructure and cloud console, and two or three hours with the people who know the system. We change nothing during the audit.
Do we have to continue with you afterwards?
No. The report is yours, and you can act on it with your own team or any vendor.
What does it cost?
It depends on the size of the infrastructure. Tell us what you run, and we'll quote a fixed price before we start.
How do you get access to our systems?
Through accounts you create for us, with MFA and least-privilege roles. Access is logged and can be revoked at any time. We sign your NDA before the first technical conversation if you prefer, and we don't copy your data to our machines.

Let's talk about your infrastructure

Tell us what is going on today. We reply within one business day with a free initial review.

Talk to an engineerServices