Autoscaling platform · Early access

Deploy from Git. Scale with traffic. Never touch a server.

Connect a GitLab or GitHub repository, choose how many instances to start with, set a monthly budget cap. CloudAutoScale builds, runs and scales your application on infrastructure you never have to see.

No Kubernetes. No Proxmox. No cloud console. Just your code and your limits.
checkout-apiRunning
main · a3f9c1e · deployed 2 min ago · GitLab
Traffic (req/s)1,840
Instances3 → 7
Budget this month$212 / $400
Traffic +240% in 10 min — scaled from 3 to 7 instances. Alert emailed to [email protected].
Runs on Our Proxmox clusters Your bare-metal servers
How it works

Four steps. Then it runs itself.

Everything happens in one panel. You never log in to a server, a cluster or a hypervisor.

01

Connect your repository

Point CloudAutoScale at a GitLab or GitHub project. Add deploy credentials, environment variables and secrets in the panel. We build from your Dockerfile or detect your stack.

02

Set your limits

Pick the number of instances to start with and the maximum you are willing to spend per month. The cap is a hard ceiling, not a suggestion.

03

We run and scale

Traffic goes up, instances go up. When workers run out of room we add capacity: bigger nodes, more nodes, or both. Traffic drops, everything scales back down.

04

Stay in the loop

Spikes, scale events and budget thresholds trigger email alerts. Restart, roll back or redeploy from the panel whenever you want.

Features

Built for teams that would rather ship.

Git-native deploys

Push to your branch and we build and ship. GitLab (cloud or self-hosted) and GitHub, private repositories included.

Traffic-driven autoscaling

Instance count follows real request load measured in minutes, not a schedule you have to guess in advance.

Hard budget caps

Set a monthly maximum. Scaling never crosses it, and you are warned well before you get close.

Grows both ways

Vertical and horizontal. Workers get bigger and more numerous as your application needs it, then shrink again.

Our clusters or your servers

Run on our own Proxmox clusters, or attach your physical servers as capacity. Mix them if you like.

Zero cluster knowledge

Kubernetes runs underneath. You never configure it, see it or debug it. Restarts and rollbacks are one click.

Division of labour

You decide. We operate.

You control

  • Repository, branch and build settings
  • Starting instance count
  • Monthly budget cap
  • Environment variables, credentials and secrets
  • Restart, roll back, redeploy
  • Who gets alerted, and when

We handle

  • Building and storing your images
  • Provisioning and replacing worker nodes
  • Scaling instances up and down with traffic
  • Load balancing, TLS certificates, DNS
  • Health checks and self-healing
  • Scaling down and keeping cost inside the cap
Under the hood

Kubernetes, without the Kubernetes.

Every application runs in its own isolated namespace on clusters we provision and manage through the Rancher API. A control plane watches request metrics and budget usage, scales pods first, and when pods are not enough, provisions new worker capacity on Proxmox or brings your own servers into the cluster.

ObserveRequest rate, latency, CPU and memory per application, sampled every few seconds.
DecideScale pods, resize workers or add new ones, always checked against your budget cap first.
ActRancher and Proxmox APIs apply the change. You get an email if it is worth knowing about.
ProxmoxOur own data centers
Bare metalYour physical servers

Take capacity from us or attach your own servers. Both are managed from the same panel.

About

Built by someone who runs infrastructure for a living.

Emre Göktepe

Founder · Infrastructure & DevOps engineer

Emre runs production Kubernetes, Proxmox and network infrastructure for hosting and SaaS companies. CloudAutoScale is the layer he kept rebuilding for customers by hand: Git in, running application out, cost capped.

CloudAutoScale

Founded 2023 · Türkiye

CloudAutoScale turns a Git repository into a running, autoscaling application on our own Proxmox clusters or on your servers, without exposing Kubernetes to the customer. Early-access customers are being onboarded now.

FAQ

Questions people ask first.

Do I need to know Kubernetes or Docker?

No. A Dockerfile helps but is not required for common stacks. You never interact with Kubernetes directly; the panel is the only interface.

What happens when I hit my budget cap?

Scaling stops at the cap. You receive an email before you reach it and again when you do. Your application keeps running at the capacity the cap allows.

Can I use my own servers?

Yes. Physical servers in your data center or office can be attached as worker capacity. We install the agent, join them to the cluster and operate them like any other node.

Which repositories are supported?

GitLab, both gitlab.com and self-hosted, and GitHub. Private repositories work through deploy tokens or deploy keys you add in the panel.

How is traffic measured?

Request rate, latency and resource usage per application, measured over a short window so bursts are caught in minutes, not hours.

Is this available now?

We are onboarding early-access customers. Request access below and we will get in touch to discuss your workload.

Early access

Ready to stop managing servers?

Tell us what you run and where it lives today. We will reply within one business day.

[email protected]