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:
| Class | CPU:RAM Ratio | Max Resources | Description |
|---|---|---|---|
| Eco | 1:2 | 3 cores, 6 GB | Development and testing |
| Standard | 1:4 | 15 cores, 58 GB | General production |
| Production | 1:4 | 6 cores, 28 GB | Dedicated resources |
| Prod. Compute | 1:2 | 6 cores, 16 GB | CPU-optimized |
| Prod. Memory | 1:8 | 6 cores, 58 GB | Memory-optimized |
| ARM | 1:4 | 8 cores, 32 GB | Cost-optimized ARM workloads |
Within each class, you configure resources using sliders. Pricing scales with allocated CPU and memory.
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
- Go to your container
- Click the Billing tab
- View current period usage and costs
Project Costs
- Go to Billing in the sidebar
- View Cost Distribution by resource type
- Filter by container to see breakdown
Organization Overview
- Go to Organization > Billing
- View total costs across all projects
- Download invoices
Cost Optimization
Right-Size Containers
Choose the smallest compute class and resource allocation that meets your needs:
| Workload | Recommended Configuration |
|---|---|
| Development/testing | Eco, 0.5-1 vCPU |
| Low-traffic APIs | Eco (1-2 vCPU) or Standard (1 vCPU) |
| Production web apps | Standard, 2-4 vCPU |
| High-performance APIs | Standard (4-8 vCPU) or Production (2-4 vCPU) |
| CPU-intensive apps | Prod. Compute, 2-6 vCPU |
| Memory-intensive apps | Prod. 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
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:
- Go to Containers
- Sort by last activity
- Stop or delete unused containers
Keeping Costs Under Control
SailOps does not offer budget alerts or spending limits. To keep costs under control:
- Follow accumulated costs in the Billing dashboard
- Stop or delete unused containers
- Cap autoscaling with an appropriate Max Replicas
Understanding Your Invoice
Invoice Breakdown
| Line Item | Description |
|---|---|
| Container: api-prod | Standard (2 vCPU, 8 GB) × 720 hours × 3 replicas |
| Container: worker | Eco (0.5 vCPU, 1 GB) × 500 hours × 1 replica |
| Subtotal | Sum of all container charges |
| Credits Applied | Remaining trial credit, if any |
| Total Due | Final amount |
Viewing Historical Usage
- Go to Organization > Billing
- Select a previous month
- 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
| Configuration | Monthly 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
| Configuration | Monthly 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 |