Your project, your requirements

The right hosting starts with your needs.

SailOps is an application hosting platform (PaaS) developed by Here We Cloud SARL, a French company. It brings container deployment, managed data services, networking, observability and cost tracking together in one console.

Three practical situations

What you want to simplify.

Start with your application and the way your team works. These are capabilities to examine and an initial check to make.

An application and its data

You have a container image, a PostgreSQL or MariaDB database and possibly a Valkey cache. Configure these resources in a project, connect them and expose the application through a gateway and your domain.

Follow the first deployment guide

Environments to reproduce

Your team deploys regularly and needs reusable configurations. Declarative stacks, the API and project keys help prepare and repeat operations; logs, metrics and activity help you follow the result.

Explore automation

Costs to explain to your team

You need to connect spending to a service or project. SailOps provides usage groupings, period comparisons and CSV export. The public estimator helps prepare a configuration before deploying it.

Read about cost tracking

What to clarify before deciding.

Operating conditions also affect your choice. Use these points to prepare your trial or your discussion with the team.

Location and contractual requirements

SailOps is operated from France. For data residency, certification, support or availability requirements, confirm the scope of each service and the applicable commitments before proceeding.

Availability and backups

Redeploying with a persistent volume can interrupt service. Protection options differ between services: validate your restore procedure and acceptable interruption.

GPUs and object storage

GPU access depends on configuration, plan and available capacity. S3-compatible object storage requires activated billing and is unavailable during the trial.

Access and observability

Permissions depend on each feature and its assigned scope. Grafana covers the organization; project filters do not isolate access. Also check your plan’s quotas and retention.

A budget you can examine

Compare a configuration, not a starting price.

Build an architecture using published rates, then share your assumptions with your team.

Open the estimator
  1. Enter the applications, instances, running hours, databases, gateways and volumes you need.
  2. Add relevant backup and S3 storage usage, then choose a plan.
  3. Keep a variant for comparison, copy the configuration link or export the breakdown as CSV.

This is an estimate excluding tax, not a quote. Monthly assumptions use 730.5 hours for continuously running resources. GPUs, observability overages and some services are not calculated; total organization consumption may change plan fees.

Information to take the next step

Documentation and information published by SailOps: review the details relevant to your project.

The next step is in your project

Evaluate your own architecture.

Start with a budget and a first service. For specific requirements, discuss your project with the SailOps team.