Skip to main content

Container Billing

Understand how container usage is calculated and billed.

Pricing Model​

SailOps uses per-hour billing for containers. You only pay for the time your containers are running.

Compute Class Pricing​

Containers are billed based on the selected compute class and allocated resources:

ClassCPU:RAM RatioMax ResourcesDescription
Eco1:23 cores, 6 GBDevelopment and testing
Standard1:415 cores, 58 GBGeneral production
Production1:46 cores, 28 GBDedicated resources
Prod. Compute1:26 cores, 16 GBCPU-optimized
Prod. Memory1:86 cores, 58 GBMemory-optimized
ARM1:48 cores, 32 GBCost-optimized ARM workloads

Within each class, you configure resources using sliders. Pricing scales with allocated CPU and memory.

Per-Hour Billing

Charges start when a container is deployed and stop when it's Stopped or deleted. Usage is billed per hour, prorated, on the CPU and memory you configure.

How Billing Works​

Cost Calculation​

Cost = (CPU Rate + Memory Rate) × Running Time (hours) × Number of Replicas

Example:

  • Standard class, 2 vCPU, 8 GB RAM
  • Running for 24 hours
  • 3 replicas
Cost = (CPU rate × 2 + Memory rate × 8) × 24 hours × 3 replicas

View current pricing in the dashboard when creating or scaling containers.

Billing Cycle​

  • Charges accrue in real-time
  • Invoices generated monthly
  • Payment processed on the 1st of each month

Viewing Container Costs​

Per-Container Costs​

  1. Go to your container
  2. Click the Billing tab
  3. View current period usage and costs

Project Costs​

  1. Go to Billing in the sidebar
  2. View Cost Distribution by resource type
  3. Filter by container to see breakdown

Organization Overview​

  1. Go to Organization > Billing
  2. View total costs across all projects
  3. Download invoices

Cost Optimization​

Right-Size Containers​

Choose the smallest compute class and resource allocation that meets your needs:

WorkloadRecommended Configuration
Development/testingEco, 0.5-1 vCPU
Low-traffic APIsEco (1-2 vCPU) or Standard (1 vCPU)
Production web appsStandard, 2-4 vCPU
High-performance APIsStandard (4-8 vCPU) or Production (2-4 vCPU)
CPU-intensive appsProd. Compute, 2-6 vCPU
Memory-intensive appsProd. Memory, 2-6 vCPU

Use Autoscaling​

Scale down during low-traffic periods:

Autoscaling:
MinReplicas: 1 # Scale to 1 at night
MaxReplicas: 10 # Scale up during peaks

Configure autoscaling →

Scale to Zero​

For environments that are only needed at set hours, such as a staging environment, set Min Replicas to 0 together with a schedule trigger. The container stops outside the schedule and incurs no compute charges.

A container scaled to zero does not start on incoming requests. See Scale to Zero.

Stop Unused Containers​

Regularly review and stop unused containers:

  1. Go to Containers
  2. Sort by last activity
  3. Stop or delete unused containers

Keeping Costs Under Control​

SailOps does not offer budget alerts or spending limits. To keep costs under control:

  1. Follow accumulated costs in the Billing dashboard
  2. Stop or delete unused containers
  3. Cap autoscaling with an appropriate Max Replicas

Understanding Your Invoice​

Invoice Breakdown​

Line ItemDescription
Container: api-prodStandard (2 vCPU, 8 GB) × 720 hours × 3 replicas
Container: workerEco (0.5 vCPU, 1 GB) × 500 hours × 1 replica
SubtotalSum of all container charges
Credits AppliedRemaining trial credit, if any
Total DueFinal amount

Viewing Historical Usage​

  1. Go to Organization > Billing
  2. Select a previous month
  3. Download the detailed invoice

FAQ​

When do charges start?​

Charges begin when a container is deployed, including image pull time.

Am I charged during updates?​

Yes, both old and new replicas are charged briefly during rolling updates. This is typically seconds to a minute.

What if my container crashes?​

You're charged for the time it was running. CrashLoopBackOff containers incur minimal charges due to rapid restarts.

Can I set spending limits?​

No. SailOps uses pay-as-you-go billing without spending limits. To control costs, stop or delete unused resources and follow usage in the Billing dashboard.

How do replicas affect pricing?​

Each replica is charged independently. 3 replicas = 3× the cost.

Cost Comparison​

Estimates below use list prices excluding tax, for a full month of 730.5 hours.

Example: Small API​

ConfigurationMonthly Cost (estimate)
1 × Eco (0.5 vCPU / 1 GiB), 24/7€12.50
2 × Eco (0.5 vCPU / 1 GiB), 24/7 (HA)€25.00
1 × Eco (0.5 vCPU / 1 GiB), scale to zero outside Mon-Fri 08:00-20:00~€4.46

Example: Production App​

ConfigurationMonthly Cost (estimate)
3 × Standard (2 vCPU / 8 GiB), 24/7€400.80
2-10 × Standard (2 vCPU / 8 GiB), autoscaling€267.20 to €1,336.00