# The right hosting starts with your needs.

[Evaluate SailOps](https://sailops.io/en/evaluate-sailops/)

Updated 27 October 2026 · SailOps team

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.

## Who does what?

- The platform: SailOps · sailops.io
- The publisher: Here We Cloud SARL · France
- The integrated assistant: Bosco AI · available in beta

[Read the legal notice](https://sailops.io/en/legal/)

## 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.

**Check for your project:** Versions, extensions, sizing, storage and the restore procedure your application needs.

[Follow the first deployment guide](https://docs.sailops.io/getting-started/first-deployment/)

### 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.

**Check for your project:** Resources supported by your stacks, key permissions and redeployment behavior when a persistent volume is attached.

[Explore automation](https://sailops.io/en/platform/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.

**Check for your project:** Organization consumption, plan fees, backups and usage outside the scope of your estimate.

[Read about cost tracking](https://docs.sailops.io/billing/usage-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.

## Compare a configuration, not a starting price.

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

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.

[Open the estimator](https://sailops.io/en/pricing/#estimate)

## Where does Bosco AI fit?

Bosco complements the platform by helping understand resource state and prepare operations. It is available in beta, included with usage limits and subject to your permissions. Observe does not change project resources, Ask requires approval for each change and Auto can execute eligible operations, with approval for sensitive actions.

[Explore Bosco modes and examples](https://sailops.io/en/bosco/)

## Information to take the next step

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

- [First deployment guide](https://docs.sailops.io/getting-started/first-deployment/)
- [Trial conditions](https://docs.sailops.io/getting-started/trial/)
- [Usage and billing](https://docs.sailops.io/billing/usage-tracking/)
- [Platform status](https://status.sailops.io/status/platform)
- [Meet Here We Cloud](https://www.herewecloud.com/en/)

## Evaluate your own architecture.

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

- [Configure my first project](https://app.sailops.io)
- [Review my project with the team](https://calendly.com/herewecloud/sailops-demo)
