Deploy containers without administering the underlying infrastructure

Start from a public or private image, define resources and health policies, then follow every version from the project.

Stay in control of every release

Configuration, rolling deployment and operational signals remain attached to the service so its status is understandable without switching tools.

Deploy and run

Ship a new version, check its status and adjust resources without administering the underlying infrastructure.

  • Container applications

    Deploy from a public or private registry, then configure CPU, memory, variables, files, health checks, rolling updates and autoscaling.

  • Static and PHP websites

    Host a website with managed storage, a custom domain and Git synchronization from a repository.

  • One time and scheduled jobs

    Run processing tasks on demand or on a schedule, then review their status and execution history.

  • Application marketplace

    Deploy preconfigured applications with their related services, versions and domain.

From image to observable service

  1. 01

    Choose what to run

    Provide a registry image, connect a repository for a website or enter the command for a job.

  2. 02

    Configure the service

    Define CPU, memory, variables, files, health checks, instances and scaling rules.

  3. 03

    Deploy and follow its status

    Review updates, events, metrics and logs from the project that owns the application.

Understand what makes up your bill

Review compute, memory, data, storage, traffic and observability separately before configuring a project.

View detailed pricing

Validate your next deployment

Access the console to configure the service or discuss your delivery constraints with the SailOps team.