Instances are the runtime units that execute your project's code. When your application is deployed, the code is built and packaged into a container image and run as an Instance.

Under the hood, Instances are Firecracker microVMs (opens in a new tab) which serve as a thin, isolated, high performance wrapper around your code. Each Instance is associated with a single Deployment of a Service and runs in one of Koyeb's regions.

Instance types

The Instance type determines the resources (CPU, Memory, Disk) allocated to your application. You can select your Instance type in your Service's Deployment configuration.

Instance typevCPURAMDiskPrice
free0.1256MB2.5GB SSD$0.00/month ($0.000000/second)
nano0.25256MB2.5GB SSD$2.70/month ($0.000001/second)
micro0.5512MB5GB SSD$5.40/month ($0.000002/second)
small11GB10GB SSD$10.70/month ($0.000004/second)
medium22GB20GB SSD$21.40/month ($0.000008/second)
large44GB40GB SSD$42.90/month ($0.000016/second)
xlarge88GB80GB SSD$85.70/month ($0.000032/second)

All plans can deploy 1 Instance of the free type. This lets you to deploy a web Service to the Frankfurt region with 256MB of RAM, 0.1 vCPU, and 2.5GB of SSD.

You can customize the Instance type running in each region if you are deploying to multiple regions.

Instance life cycle

Each Instance's life cycle is closely related to that of the Deployment it belongs to. Instance health statuses affect Deployment health statuses and that health status bubbles up to the Service and App levels. Likewise, changes in Service configuration affect how Instances start and stop and whether they receive traffic routed to the application.

When deploying from a git repository, Instances will be provisioned once the build succeeded. When deploying from a container registry, Instances will be provisioned when the image is downloaded and other requirements are met.

When an Instance responds to health checks as expected, Koyeb will mark the Instance as healthy and add it to the group of Instances that are targets for load balancing. If an Instance stops responding to health checks or fails to reach a healthy state during initial provisioning, it will be marked as unhealthy.

If an Instance is not working correctly, a new Deployment is promoted, or the Instance's Service is deleted, the Instance will be stopped. This will remove the Instance from the Service load balancer's list of targets and then stop and delete the Instance.

Instance statuses

Instances can have several statuses during their life cycle:

  • Allocating: A start request has been received and the Instance is about to start.
  • Starting: The Instance is running but health checks have not yet succeed.
  • Healthy: The Instance is running and health checks are succeeding.
  • Unhealthy: The Instance is running but health checks are failing.
  • Stopping: The Instance is being stopped. This happens when a Service change is requested and the Deployment that the Instance is associated with is stopping.
  • Stopped: The Instance is stopped.
  • Error: The Instance failed to start.

In addition to the Instance status, messages are provided with additional information. These messages can be helpful when troubleshooting problems with a specific Instance or a Deployment.

Check out the troubleshooting page to learn more about how to troubleshoot your Services, Deployments, and Instances.

You can learn more about MicroVMs and Firecracker reading the following articles: