Skip to content
lastdevops

Case studies

Infrastructure we built, migrated or took over for these companies: cloud migrations, greenfield platforms, rebuilds of existing setups, monitoring and 24/7 incident response.

filter:

  • Novotek

    Industrial

    Infrastructure rebuildMonitoring and on-call

    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

  • RZD

    Transportation

    Infrastructure rebuildMonitoring and on-call

    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

  • SberCorus

    Fintech and EDI

    Infrastructure rebuildMonitoring and on-call

    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

  • Otus

    EdTech

    Cloud migrationMonitoring and on-call

    Traffic comes in spikes around course launches, and paying for permanent spare capacity made no sense.

    • Migrated the infrastructure to the cloud in stages, without service downtime
    • Set up autoscaling for peak load
    • Added monitoring and regular cost reviews

  • Besttrip

    Travel

    Greenfield infrastructureMonitoring and on-call

    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

  • JedAI

    AI platforms

    Greenfield infrastructure

    ML workloads need different infrastructure than regular web services.

    • Deployed clusters for training and inference
    • Made environments reproducible
    • Built model rollout pipelines

  • IMSystems

    System integration

    Greenfield infrastructureInfrastructure rebuild

    Deployments for different customers in air-gapped environments had to be repeated by hand.

    • Described the infrastructure as code so every environment deploys the same way
    • Accounted for air-gapped networks with limited internet access
    • Cut the time needed to stand up a new environment

  • Builddocs

    Construction document management

    Cloud migration

    The system ran on its own hardware; maintenance was getting more expensive and capacity was running out.

    • Planned and executed a cloud migration with a rollback plan at every step
    • Set up backups with regular restore testing
    • Built deployment pipelines on the new platform

  • Headframe

    Product development

    Greenfield infrastructureMonitoring and on-call

    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

  • RTDS

    Telecom

    Monitoring and on-callInfrastructure rebuild

    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

Some of the clients we can name publicly. Many projects are under NDA. Details are shared under NDA: on request we will prepare a case relevant to your project and references.

A similar problem?

Tell us what you run today, and we'll suggest an approach and show how we solved something similar.

Talk to an engineer