Expose services and connect every signal to the right application

Configure routes and domains, then use metrics, logs and events to understand service behavior.

From incoming traffic to diagnosis

Routes, certificates and operational signals remain attached to the service so teams spend less time correlating information.

Expose and observe

Connect each signal to the relevant application so teams can diagnose faster and act from the project.

  • Gateways and routes

    Distribute traffic through HTTP, TCP, gRPC or TLS routes to services in the project.

  • Domains and TLS certificates

    Attach your domains, configure listeners and let SailOps manage their associated certificates.

  • Metrics, logs and events

    Review CPU, memory, network, container logs and operational events from the product.

  • Alerts and telemetry

    Create alerts, choose notification channels and connect your OpenTelemetry flows.

Expose, observe and act

  1. 01

    Define the routes

    Distribute HTTP, TCP, gRPC or TLS traffic to the services in the project.

  2. 02

    Attach your domains

    Configure listeners, attach domains and let SailOps manage the associated TLS certificates.

  3. 03

    Monitor what matters

    Review metrics, logs and events, then create the alerts and notification channels you need.

Understand what makes up your bill

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

View detailed pricing

Make your service observable from its first release

Configure access in the console or discuss your networking and observability constraints with the SailOps team.