Skip to main content

Pricing

Pay only for what you use, billed by the hour.

Pricing Philosophy​

SailOps pricing is designed to be:

  • Transparent - No hidden fees or surprises
  • Fair - Pay only for actual usage
  • Granular - Billed per hour
  • Scalable - Costs scale with your business

Containers​

Compute Classes​

Containers are billed based on compute class and the resources you configure. Each compute class has a fixed CPU:RAM ratio, and you adjust resources using sliders within the class limits.

ClassCPU:RAM RatioMax CPUMax RAMDescription
Eco1:23 cores6 GBDevelopment and testing
Standard1:415 cores58 GBGeneral production workloads
Spot1:23 cores6 GBBest-effort spot capacity, may be unavailable when spare capacity runs out
Production1:46 cores28 GBCritical workloads with dedicated resources
Prod. Compute1:26 cores16 GBCPU-intensive tasks (data processing, APIs)
Prod. Memory1:86 cores58 GBMemory-intensive tasks (caching, ML inference)
ARM1:48 cores32 GBCost-optimized ARM-based workloads

Within each class, configure resources using sliders:

  • CPU: Adjust in increments (varies by class)
  • Memory: Automatically calculated based on CPU:RAM ratio

Container Billing​

Containers are billed:

  • Per hour of runtime
  • For each replica running
  • Based on the compute class and resources selected

Example:

Container: api-server
Class: Standard
Resources: 2 vCPU, 8 GB RAM (1:4 ratio)
Replicas: 3
Uptime: 720 hours/month

Cost = (class rate × resource allocation) × 3 replicas × 720 hours

GPU Compute Classes​

GPU compute classes are billed separately for GPU resources in addition to standard CPU/RAM billing. GPU billing is calculated per GPU-fraction-hour, with each class offering different GPU models and allocation modes.

ClassGPU ModelGPU ModeGPU MemoryPrice DimensionDescription
gpu-l4NVIDIA L4Dedicated24 GBPer GPU-hourGeneral-purpose GPU for AI inference
gpu-h100-mig-smallNVIDIA H100MIG 1g.10gb10 GBPer slice-hourH100 MIG slice, minimum billing duration applies
gpu-h100-mig-mediumNVIDIA H100MIG 2g.20gb20 GBPer slice-hourH100 MIG slice, minimum billing duration applies
gpu-l40sNVIDIA L40SDedicated48 GBPer GPU-hourHigh-memory GPU for large models
gpu-h100NVIDIA H100Dedicated80 GBPer GPU-hourTop-tier GPU for training and inference

GPU Billing Notes:

  • GPU classes enforce minimum CPU and RAM requirements
  • MIG classes have minimum billing durations to prevent abuse
  • Some GPU classes require BUSINESS or CUSTOM support plans
  • GPU utilization and memory metrics are tracked separately

Autoscaling Costs​

When autoscaling adds replicas:

  • Only active replicas are billed
  • Scaling down stops billing immediately
  • Min replicas always billed

Databases​

PostgreSQL Pricing​

PostgreSQL databases use flavors within compute classes. Each compute class (eco, standard, production) offers a set of predefined flavors (small, medium, large, xlarge) with fixed CPU and RAM allocations.

Select a compute class, then choose a flavor that matches your workload requirements. Storage is configured separately.

MariaDB Pricing​

MariaDB databases follow the same model as PostgreSQL: select a compute class (eco, standard, production), then choose a flavor (small, medium, large, xlarge). Storage is configured independently.

MariaDB supports:

  • Multiple databases per instance
  • Public access for external connections
  • Automated backups

Database Flavors​

Both PostgreSQL and MariaDB use the following structure:

Compute ClassAvailable FlavorsDescription
Ecosmall, medium, large, xlargeDevelopment and testing
Standardsmall, medium, large, xlargeGeneral production databases
Productionsmall, medium, large, xlargeCritical databases with dedicated resources

Each flavor defines a fixed CPU and RAM allocation. Exact resource values for each flavor are available via the Pricing API.

Storage Classes​

ClassMax IOPSBest For
standard5,000General workloads, development
performance15,000High I/O, OLTP, analytics

All storage uses NVMe SSDs. Storage can be increased at any time without downtime.

High Availability​

HA doubles compute costs (standby replica running synchronously):

  • Primary instance: full compute cost
  • Standby replica: additional compute cost
  • Automatic failover in < 30 seconds
  • Storage shared and replicated

NATS Messaging​

NATS Cluster Pricing​

NATS clusters use flavors within compute classes, similar to databases. Select a compute class (eco, standard, production), then choose a flavor (small, medium, large, xlarge).

Compute ClassAvailable FlavorsDescription
Ecosmall, medium, large, xlargeDevelopment and testing
Standardsmall, medium, large, xlargeGeneral production messaging
Productionsmall, medium, large, xlargeCritical messaging with dedicated resources

NATS clusters are billed per-hour based on the selected compute class, flavor, and number of replicas.

Cache​

Valkey/Redis Instances​

Cache instances use flavors within compute classes, following the same model as databases and NATS. Select a compute class (eco, standard, production), then choose a flavor (small, medium, large, xlarge).

Compute ClassAvailable FlavorsDescription
Ecosmall, medium, large, xlargeDevelopment and testing
Standardsmall, medium, large, xlargeGeneral production caches
Productionsmall, medium, large, xlargeCritical caches with dedicated resources

Cache instances are billed per-hour based on the selected compute class, flavor, and number of replicas.

Websites​

Hosting Plans​

Websites use fixed plans built on the Eco compute class:

PlanCPUMemoryReplicasBest for
Starter0.25 vCPU256 MiB1Personal sites, prototypes
Standard0.5 vCPU512 MiB2Business sites, moderate traffic
Pro1 vCPU2048 MiB3High-traffic sites, PHP applications

Prices shown via the API are per instance; billing multiplies by the plan's replica count at Eco class rates.

Website Storage​

Website files are stored in S3. Storage is billed per GiB per hour regardless of whether the website is running.

Start/Stop​

Stopped websites are not charged for compute. S3 storage charges still apply.

Gateways​

Gateway Classes​

Gateways are billed per-hour based on the selected class:

ClassBandwidthBest For
gw-small200 MbpsDevelopment, small applications
gw-medium500 MbpsMedium traffic applications
gw-large1 GbpsHigh-traffic production
gw-xlarge4 GbpsEnterprise, very high traffic

Included Features​

FeatureIncluded
Custom domainsFree (unlimited)
SSL certificatesFree (auto-provisioned)
RoutesFree (unlimited)

Managed Observability​

Managed observability usage covers telemetry sent through SailOps OpenTelemetry ingestion and retained in the managed observability backends. It is separate from normal resource compute billing.

Included telemetry​

PlanMetric samples / monthTrace spans / monthTelemetry storageActive seriesMetric retentionMetric sample rate limit
Basic5 million1 million10 GiB-month5007 days100 samples/s
Starter50 million5 million25 GiB-month10,00030 days1,000 samples/s
Business500 million25 million100 GiB-month100,00090 days10,000 samples/s
Custom0 included0 included0 includedCustom365 daysCustom

Overage pricing​

Usage dimensionPrice
Metric samples€0.10 per million samples
Trace spans€0.30 per million spans
Telemetry storage€0.08 per GiB-month

For Basic, metric ingestion is hard-capped when the included metric sample quota is reached. Paid plans continue ingesting and bill overage. Custom plans bill managed observability from the first unit unless your contract defines custom terms.

You can monitor current usage, quota, projected overage, active series, and per-project breakdown in Monitoring → Usage → Telemetry.

Volumes​

All persistent volumes — block volumes attached to containers and shared (RWX) volumes — are billed per GiB per hour based on provisioned capacity.

Block volumes​

Block volumes are the persistent volumes attached to a container. They are billed on the provisioned size of each volume, using the storage class rate:

Storage ClassDescription
standardGeneral-purpose NVMe (5K IOPS)
performanceHigh-throughput NVMe (15K IOPS)
  • Billing starts when the volume is first bound
  • Billing stops when the volume is deleted
  • Detached volumes continue to be billed until explicitly deleted
  • Resizing a volume updates the billing rate immediately

Shared volumes​

Shared (RWX) volumes are billed per GiB per hour based on the provisioned size, regardless of actual usage. Shared volumes persist independently of any container lifecycle.

  • Billing starts when the volume is created
  • Billing stops when the volume is deleted
  • Resizing a volume updates the billing rate immediately

Object Storage​

Object Storage is billed on metered usage across four dimensions. There is no fixed cost — you pay only for what you consume.

DimensionPrice (excl. tax)Description
Storage€0.79 per GiB-monthTime-weighted average of stored bytes, including all object versions
Writes & listings€5.00 per million requestsPUT, POST, DELETE and list operations
Reads & HEAD€0.50 per million requestsGET and HEAD operations
Downloads€0.02 per GiBEgress bytes — same rate from the SailOps internal network and the Internet

Quantities are billed fractionally: there is no minimum charge and requests are not rounded up to the next million.

Usage is measured per bucket and aggregated at the project level. Costs appear in the Object Storage tab of the billing dashboard.

info

Object Storage requires an activated billing account and is unavailable during the free trial.

Cost Estimation​

Costs depend on your selected compute classes, resources, and usage. Here are example configurations:

Example: Development Setup​

Container (Eco, 0.5 vCPU / 1 GB × 1 replica):
720 hours/month

Database (Eco, 0.5 vCPU / 1 GB):
720 hours/month + 10 GB storage

Cache (Eco, 0.5 vCPU / 1 GB):
720 hours/month

Gateway (gw-small):
720 hours/month

Example: Production Setup​

Container (Standard, 2 vCPU / 8 GB × 3 replicas):
720 hours/month

PostgreSQL Database (Standard, medium flavor + HA):
720 hours/month + 50 GB performance storage

MariaDB Database (Eco, small flavor):
720 hours/month + 10 GB standard storage

NATS Cluster (Standard, small flavor × 3 replicas):
720 hours/month

Cache (Standard, small flavor):
720 hours/month

Gateway (gw-medium):
720 hours/month

View current pricing in the dashboard when creating resources.

Billing Cycle​

Monthly Billing​

  • Billing period: 1st to last day of month
  • Invoice generated on 1st of following month
  • Payment due within 14 days

Real-Time Usage​

View current usage anytime:

  1. Click Billing in the left sidebar
  2. Select a resource tab:
    • Summary — Overall cost overview
    • Containers — Container compute costs
    • Websites — Website hosting costs
    • Gateways — Gateway bandwidth costs
    • PostgreSQL — PostgreSQL database costs
    • MariaDB — MariaDB database costs
    • Caches — Valkey/Redis cache costs
    • NATS — NATS messaging costs
    • Jobs — One-time job costs
    • Cron Jobs — Scheduled job costs
    • Marketplace — Costs of existing instances deployed before retirement
    • Custom Services — External service costs
    • Volumes — Block and shared volume storage costs
    • Object Storage — Object storage usage costs
  3. See accumulated costs and usage details for the selected resource type

Payment Methods​

Accepted Methods​

  • Credit/Debit Card — Visa, Mastercard, and other networks supported by Stripe
  • SEPA Direct Debit — Bank transfers for European bank accounts

Payments are processed securely through Stripe. Card and bank details are never stored on SailOps servers.

Adding Payment Method​

  1. Open Organization Settings (click your Organization name at bottom left > Settings)
  2. Select the Payments tab
  3. Click Add Payment Method
  4. Enter card details in the Stripe secure form
  5. The card is set as your default payment method

Stripe Customer Portal​

You can manage your payment methods and billing details directly through the Stripe Customer Portal:

  1. Go to Organization Settings > Payments tab
  2. Click Manage Billing to open the Stripe portal
  3. From there you can update card details, view payment history, and download receipts

Cost Optimization​

1. Right-Size Resources​

Match compute class to actual needs:

If CPU < 30% and Memory < 50% consistently:
→ Consider downgrading compute class

2. Use Autoscaling​

Scale down during low traffic:

autoscaling:
min: 1 # Low traffic minimum
max: 10 # Peak capacity

3. Clean Up Unused Resources​

Regularly review and remove:

  • Stopped containers
  • Unused databases
  • Old backups

4. Use Cache Effectively​

Cache reduces database load:

  • Smaller database needed
  • Fewer queries = faster response
  • Lower costs overall

5. Optimize Storage​

  • Compress data when possible
  • Clean up old logs
  • Use appropriate retention policies

FAQ​

How am I charged for stopped containers?​

Stopped containers:

  • No compute charges
  • Storage still charged if persistent

What happens if payment fails?​

  1. Email notification sent immediately
  2. Grace period starts — your services continue running
  3. Stripe retries the payment automatically
  4. If the invoice remains unpaid after the grace period, your organization is suspended
  5. Update your payment method to restore services instantly

Can I set spending limits?​

SailOps uses pay-as-you-go billing. To control costs:

  • Stop or suspend unused resources and projects
  • Monitor usage in the Billing dashboard
  • Contact support for custom billing arrangements on the CUSTOM plan

Are there setup fees?​

No. SailOps has no:

  • Setup fees
  • Minimum commitments
  • Cancellation fees

How do I get an invoice?​

Invoices are:

  • Generated monthly
  • Available in Billing (click in sidebar) > Summary tab
  • Sent to billing email

Pricing API​

SailOps exposes a pricing endpoint that returns current rates for all resource types, scoped to your organization.

GET /api/v1/organizations/{organizationId}/pricing
Negotiated pricing

If your organization has a CUSTOM plan with negotiated rates, the pricing endpoint returns your contract-specific prices. The billing dashboard and cost estimators use these same rates, so the amounts you see always match your invoice.

The response includes:

FieldDescription
computeClassesContainer compute class pricing (per-CPU-hour, per-RAM-GiB-hour)
storageClassesStorage pricing (per-GiB-hour, max IOPS)
loadBalancerClassesGateway pricing (per-hour, bandwidth)
databaseClassesDatabase and service flavor pricing (per-hour per flavor)
websitePlansWebsite plan pricing (per-hour per instance, CPU, memory)

Additional fields for GPU compute classes:

FieldDescription
minCpuMinimum CPU cores required for the class
minRamMiBMinimum RAM in MiB required for the class
gpuTypeGPU model (L4, L40S, H100)
gpuModeGPU allocation mode (dedicated, mig-1g.10gb, mig-2g.20gb)
gpuMemoryGiBGPU memory per unit in GiB
pricePerGpuHourPrice per GPU-fraction-hour
maxGpusMaximum number of GPUs per container
minBillSecondsMinimum billing duration for MIG classes (anti-abuse)
requiresPlansArray of required support plans (BUSINESS, CUSTOM)
Programmatic Access

Use this endpoint to build cost estimators or integrate pricing into your CI/CD pipelines. The full schema is defined in the Public API documentation.