KuboRun
Menu

Cloud services

Your services, in one dashboard.

An API, a background worker or a database: run each part of your application with the resources it needs.

Size each serviceKeep persistent dataCheck usage

Size each service

Set CPU, RAM and replica count for each container. Keep an API running all day and run another workload only when needed.

Keep persistent data

Use volumes for data that must survive a container replacement. Runtime disk belongs to the running workload; it is not a replacement for a volume or a backup.

Check usage

Costs depend on resources, replicas and running time. Retained storage still counts when you stop a service. Try those settings in the simulator before deciding.

Frequently asked questions

What matters before publishing.

Can I run several services?

Yes. Each has its own resource, network and storage settings.

Does stopping a service delete its data?

Persistent data belongs in volumes. Do not keep data you need to retain on a container’s runtime disk.

You may also be interested in

More guides for your project.

View all solutions →
Publish a websitePublish your website on your own domain.→Static websitesFor a static website, bring your files.→Your frameworkNext.js, Astro or React: deploy what you built.→