Skip to content

DevOps for startups: the smallest production setup that is still production

An MVP does not need a platform. It needs a place to run, a deploy that does not depend on one laptop, backups, and a signal when something breaks. We set up exactly that, quickly, and write it so it can grow with the product instead of being thrown away.

When you need this

  • 1

    The MVP is nearly ready and there is nowhere to run it properly

  • 2

    A founder or a developer deploys by hand over SSH

  • 3

    A demo, a pilot client or a funding round is close and the product has to be online

  • 4

    You were advised to start with microservices and Kubernetes and doubt that you need them

  • 5

    You have cloud credits and want to spend them on the product, not on idle servers

What's included

  • A setup sized for today

    One server with containers or a small Kubernetes cluster — whichever the product needs now. The reason for the choice is written down.

  • CI/CD from the first day

    A push builds, tests and deploys. Any developer can release, and the previous version is one command away.

  • Domain, TLS, environments

    Production and a staging copy on your domain, with certificates issued and renewed automatically.

  • Monitoring and alerts

    Availability checks, basic metrics and logs, alerts to Telegram or Slack. Enough to learn about a failure before a client does.

  • Backups

    The database and uploaded files are backed up on a schedule to storage outside the server. A restore is tested once before launch.

  • A growth path

    Everything is code in your repository. The document lists what to change and at which signs: a second server, a managed database such as AWS RDS, a Kubernetes cluster.

How the work goes

  1. 1

    Call

    What the product does, what it is written in, when it has to be live and what budget there is for hosting.

  2. 2

    Scope and price

    A short list of what goes into the first setup and what is deliberately postponed. Fixed price.

  3. 3

    Setup

    We build it through pull requests in your repository and deploy the application together with your developers.

  4. 4

    Launch and after

    The product goes live. We either hand over with documentation or stay on for monthly support.

Questions

  • Docker
  • Docker Compose
  • AWS EKS
  • Terraform
  • Helm
  • GitHub Actions
  • PostgreSQL
  • Cloudflare
  • Grafana
  • VictoriaMetrics
  • AWS
  • Hetzner

Describe the task — get a plan and a price

Write what you have and what you need. We answer within one business day with questions or a concrete proposal.