In LayerOps, a service can represent anything that runs on your instances, whether it's an API, a frontend, a job, or anything else. These services are highly configurable and can be deployed from our marketplace or directly from any Docker image.

A service can have a public port, autoscaling rules, be considered as a CRON, have environment variables, etc.
Go to the Create service page for a list of all service configuration options.


Once created, you can access your service to see all the information: on which instance it is deployed, how many services are deployed, resource usage, etc.


In "overview" you'll find all the important information about your service. For example, you can find the exposed ports and associated domain names.

You'll also find basic monitoring of the resources allocated and consume by your service.

service overview

For detailed monitoring, go to the monitoring documentation.


Track where your services are deployed in the "Instances" tab. You can see the distribution on the different providers.

service overview


Follow real-time alerts related to your service. If your service is configured with autoscaling, these alerts can cause scale out / scale down, or even scaling on instance pools.

service overview

More information about autoscaling here.


In the monitorin tab you can find a basic display of your service logs. On this page you will also find direct links to your service's dashboard to view the complete logs and metrics of your service.

service overview

To access monitoring, you first need to create a user able to connect to the dashboard. Read more documentation about monitoring or about monitoring user creation

SSH Connections

The "SSH Connection" tab allows to manage and establish SSH connections to your services. You can view existing SSH connections and create new ones, useful for debugging and troubleshooting purposes.

You can easily add SSH connections by configuring an authorized public IP address and associating it with a public SSH key, providing a secure method for connecting to your services.

service overview

You can control SSH access through Role-Based Access Control (RBAC). This ensures that SSH connections are authorized only for users with the necessary permissions, enhancing the overall security of your services. Read more about RBAC