Skip to content

How it works

Application replicas and autoscaling

A replica is a running copy of the application. Fixed replicas keep a configured count; autoscaling adjusts it within minimum, maximum and plan capacity. Failover is included in every plan (a standby copy kept off in another country); autoscaling and load balancing are optional and billed by the hour. Copies running at once: Hobby up to 2, Pro up to 3, Enterprise up to 5, each extra copy billed by the hour while it runs. Extra copies do not repair application errors.

Keep sessions, queues and mutable data in shared services. A local SQLite file, local upload folder or embedded scheduler needs special care before scaling: copies can diverge or execute the same scheduled action twice.

There are three modes: Scalability (autoscaling), Load balancing or Failover. Failover is included in every plan: your project stays online when a server goes down, because the standby copy in another country takes over on its own. Autoscaling and load balancing are optional, available on every plan and billed by the hour only while the extra copies run.

Scalability (autoscaling) — you turn it on in the dashboard: when CPU goes over the limit, a clone starts on its own and shares the load; when usage drops, it is turned off and stops being billed.

Load balancing: one or more extra copies stay on 24 hours and share the traffic with the primary. Each extra copy is billed by the hour while it is on. The copies share the same database and S3, so keep sessions, queues and files in shared services, not in the container’s memory or disk.

Failover — included: the standby copy is ready but kept OFF in another country — it uses no CPU and its image is already downloaded; every deploy updates it. If the primary fails, a watcher starts the standby in the other region (USA ↔ Germany) and the project comes back on its own within seconds.

Copies running at once: Hobby up to 2, Pro up to 3, Enterprise up to 5. Each copy has the plan’s size. Hourly price of each extra copy (plan price ÷ 30 days ÷ 24 h): Hobby US$ 0.0069 (≈ US$ 5/month if always on), Pro US$ 0.0278 (≈ US$ 20/month), Enterprise US$ 0.0819 (≈ US$ 59/month). Load balancing: always-on copy at the full hourly price. Autoscaling: the 1st extra copy at full price and, from the next one on, 10% off: Hobby US$ 0.0063, Pro US$ 0.0250, Enterprise US$ 0.0738.

Extra copies require a paid plan in good standing; during the trial the app runs 1 copy. The usage invoice is issued on the 1st of each month and is paid by Pix (Brazil, PAGUEO) or card (Stripe). An unpaid usage invoice follows the same rule as any other: paused after 4 days, deleted after 9. Usage, prices and invoices are in Billing → Extra copies.

Application replicas and autoscaling · Devora Cloud · Devora Cloud