Skip to content
lastdevops

DevOps as a Service

A senior DevOps team on a monthly retainer. We build and maintain your delivery platform — CI/CD, infrastructure as code, Kubernetes, observability — inside your repositories, so it stays yours.

Talk to an engineerStart with an audit

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

  • Audit in 3–5 days
  • Everything as code in your Git
  • 24/7 on-call available
  • Co-founders do the work

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

Developers fix pipelines instead of shipping

Every week someone loses a day to a broken build, a flaky deploy or an expired certificate.

Infrastructure nobody can reproduce

It was clicked together in a console, and the person who did it is the only one who knows how.

One DevOps engineer — or none

Your only platform engineer is a single point of failure, is overloaded, or has just resigned.

Hiring takes months

A senior platform engineer is hard to find, and the infrastructure work can't wait that long.

scope.md

What we do

CI/CD pipelines

GitLab CI, GitHub Actions or Jenkins, with ArgoCD for GitOps. Fast builds, safe deploys, one-step rollback.

Infrastructure as code

Terraform, Pulumi, Ansible and Packer. Every change goes through review instead of a console.

Kubernetes platform

Cluster setup, upgrades and day-to-day operations — or a simpler platform if Kubernetes isn't worth it yet.

Observability

Prometheus, Grafana, Loki or ELK and OpenTelemetry, with alerts that point to a runbook.

Secrets and access

Vault or your cloud's secret manager, SSO, least-privilege roles and audited access.

Resilience by default

Multi-zone deployments, backups with restore tests and a recovery plan are part of the platform, not an add-on.

What you keep

  • IaC modules and pipelines in your Git
  • Dashboards and alert rules with runbooks
  • A monthly report you can forward to management
  • Handover documentation, kept current as we go

Stack

  • Kubernetes
  • Terraform
  • Ansible
  • GitLab CI
  • GitHub Actions
  • ArgoCD
  • Prometheus
  • Vault
pipeline.yml

How the work goes

After every stage you decide whether to go further.

  1. 01 · audit3–5 days

    Audit

    We review delivery, infrastructure, reliability, security and cost.

    Outcome: A written report with a prioritized list of problems

  2. 02 · plan1–2 weeks

    Plan

    Target setup, priorities and the monthly scope of work.

    Outcome: A roadmap and an estimate

  3. 03 · operatemonthly

    Ongoing service

    We build the roadmap item by item and keep the platform running.

    Outcome: A monthly report: work done, incidents, next steps

git log --cases

Similar problems we have solved

All case studies
Fintech and EDI

SberCorus

Releases were rare and manual; every deployment was an event.

  • Moved services to Kubernetes with zero-downtime updates
  • Built build, test and deploy pipelines for every environment
  • Cleaned up secrets management and access rights
Travel

Besttrip

The product was growing faster than its infrastructure.

  • Built the infrastructure from scratch: networks, access, environments
  • Automated builds and deployments
  • Took the service over for ongoing operations
Product development

Headframe

A strong product team with no dedicated infrastructure engineer.

  • Built the infrastructure and release process from scratch
  • Set up observability so the team can see the state of its services
  • Handed over knowledge and documentation to the team
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

How is this different from hiring a DevOps engineer?
You get a team instead of one person: senior engineers who share context, cover for each other and don't all go on leave at once. You also skip months of hiring and onboarding.
How is it different from DevOps consulting?
Consultants hand you a plan. We implement it, and then keep running it with you.
Who will work on our project?
One of our three co-founders leads every engagement and stays on it. The engineers you meet on the first call are the ones with access to your systems.
Do you need Kubernetes for this?
No. If a managed platform or plain VMs fit your scale, we'll tell you in the audit.
Do we own everything you build?
Yes. Code, Terraform, Helm charts and runbooks live in your repositories from day one, and cloud accounts stay in your name. If you ever take the work in-house, the handover is documentation and a call, not a rescue project.
Where is your team and what hours do you work?
We work in UTC+3. That is one to two hours ahead of Central Europe, so a normal European business day overlaps almost entirely with ours. For US teams we schedule calls in your morning, and incidents are covered 24/7 regardless of time zone.

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