Skip to content

Managed hosting: your application on our infrastructure

You have code and no servers. We run the application on the same clusters that serve our own product, MetaPlatho, with the same deploy pipeline, monitoring and backups. You push to the repository; the rest is on us.

When you need this

  • 1

    There is an application, but no cloud account and nobody to set one up

  • 2

    You do not want to hire a DevOps engineer for one product

  • 3

    Shared hosting or a single VPS no longer covers what the application needs

  • 4

    You need a database, a queue and file storage, not just a place for the code

  • 5

    You want one monthly figure instead of a cloud bill with dozens of lines

What's included

  • Deploys from your repository

    A push to the main branch builds a container image and rolls it out without downtime. Rollback to the previous version is one command.

  • Database, cache, queue, storage

    PostgreSQL or MySQL, Redis, a job queue and S3-compatible object storage — the parts your application needs, sized for it.

  • Domains, TLS and CDN

    We connect your domain, issue and renew certificates automatically and put static files behind a CDN.

  • Monitoring you can see

    Metrics, logs and alerts for your services. You get access to the dashboards, and the alerts come to us.

  • Backups

    Database and file backups run on a schedule and are stored separately from the cluster. Restores are tested.

  • A portable setup

    The application is described by a Dockerfile, a Helm chart and a pipeline in your repository. The same files deploy it in any other Kubernetes cluster, AWS EKS included.

How the work goes

  1. 1

    Look at the application

    We read the repository: what it is written in, what it depends on, what resources it needs.

  2. 2

    Resources and price

    We agree on CPU, memory, storage and environments. You get a fixed monthly price for them.

  3. 3

    Staging first

    The application is packaged into a container and deployed to a staging environment, where you check it.

  4. 4

    Go live

    Data is transferred, the domain is switched in an agreed window, and the application goes under monitoring.

Questions

  • Kubernetes
  • Helm
  • Docker
  • GitHub Actions
  • PostgreSQL
  • Redis
  • Traefik
  • Cloudflare
  • Grafana
  • VictoriaMetrics
  • Loki
  • 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.