Scalable backend

Publish a backend from a repo and adjust CPU, memory, and instances per environment, with the cost per hour visible.

See how it works

YOU NAME THE BACKEND AND CONNECT THE REPOCHOOSE THE TYPE (SERVICE · WORKER · SCHEDULE TASK · LAMBDA)ADJUST CPU, MEMORY, AND INSTANCESDEPLOY WITH METRICS AND LOGS

Choose the type of backend you need to create

Service, Worker, Schedule Task, or Lambda. Name it, paste the GitHub repository URL, and choose the type; the rest is configuration.

Choose CPU, memory, and instances

CPU units and memory —with the cost per hour visible— plus a minimum and maximum number of instances. Change the values as you need to adapt.

Autoscaling and health checks

Define the autoscaling behavior, the health check grace period, and, if needed, an advanced health configuration.

Every environment, its own configuration

production, staging, and dev each have their own Runtime settings, variables, policies, and Docker arguments. Adjust production without touching dev.

Don't see what you need to set up? Tell us your case and we'll review it with you.Talk to an expert

We use cookies to enhance your experience on our site and tailor content to your needs. By clicking "Accept," you agree. Read our Cookie Policy and Privacy and Data Policy, and our Terms and conditions for more information.