S3-compatible storage cost calculator

Compare object storage and Garage using usable capacity, replication, requests, egress, compatibility, independent backups and operating cost.

Last updated

In short

  • Usable object capacity differs from physical replicated storage.
  • S3 compatibility must be checked against the API behavior your application uses.
  • Replication is not an independent backup or a universal durability guarantee.
On this page (5)

Costs and savings · Part of Garage

Interactive worksheet · no sign-up

Estimate S3-compatible storage costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Additional billed replicated storage

Use physical capacity including redundancy only if not already paid for in infrastructure.

Billable egress

Local network and hardware are not economically free; account for them in infrastructure.

Billable request batches

Use an effective quoted rate, or add separate request charges to infrastructure if rates differ.

S3 compatibility is not full AWS feature equivalence. Check versioning, object lock, lifecycle rules and durability design before comparing capacity.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

Object storage comparisons often start with a price per gigabyte and end before replication, request traffic and operation are counted. This calculator helps compare a real S3 workload with an operated Garage design. It does not assume identical API features, durability commitments or service levels.

Reconstruct the current bill

Collect stored bytes, object count, storage classes, request types, retrieval, data transfer and replication charges. Include lifecycle rules and minimum-duration or retrieval charges where they apply to the source contract. A mostly idle archive and an actively downloaded media library have different cost drivers.

Input Why it matters
Live object bytes Starting usable capacity
Object count and size distribution Metadata and operational overhead
Write/change rate Replication traffic and retained copies
Read and download pattern Requests, bandwidth and network capacity
Required API operations Compatibility and application changes
Failure domains Node/location design and spare capacity
Independent recovery Backup scope and deletion protection

Use the actual invoice and access profile. A list-price comparison that ignores negotiated transfer terms or a bundled allowance can exaggerate the available saving.

Convert usable capacity to a physical design

Garage’s deployment guide describes a multi-node deployment with replication. For a three-copy planning example, 10 TB of live objects implies roughly 30 TB of object payload across replicas before metadata, free-space margin and other overhead. This is arithmetic about a replication factor, not a tested capacity or durability result.

Distributing copies across nodes is only useful if the failure domains match the requirement. Three disks in one machine do not tolerate loss of that machine. Three machines in one room do not address loss of the room. Account for connectivity and recovery bandwidth between locations.

Replication also reproduces legitimate deletion. If recovery from accidental deletion or compromised credentials is required, design an independent recovery path and include its cost. Do not equate replica count with backup retention.

Check the operations your application really uses

The S3 compatibility reference documents supported behavior and differences. Inspect your application’s calls, including multipart uploads, metadata, permissions and any lifecycle or event features. Garage’s access model should not be assumed to accept an existing AWS permission policy unchanged.

Use a test bucket with representative objects and an isolated application configuration. Verify upload, download, list, overwrite, delete and access denial. Include interrupted transfers, large objects and the metadata the application relies on. This is a reference validation procedure, not a claim that a particular integration has been tested by Pilae.

Price migration and steady operation separately

A bulk transfer can create source retrieval/egress charges, temporary capacity and staff work. Keep both services while checksums and application behavior are reconciled. If writes continue during the copy, plan the final synchronization rather than relying on a one-time inventory.

Recurring costs include nodes, network, recovery copies, monitoring, upgrades and incident response. A customer’s existing storage hardware can change incremental cash expenditure but still has replacement and operating costs. Use Pilae pricing for the service component and a scoped architecture quote for the rest.

Choose the outcome the evidence supports

A smaller bill is useful when the new system meets the required API, capacity and recovery behavior. If the source provides features that must remain, keep those costs in the model or limit the migration to a suitable workload. The Amazon S3 migration guide covers execution; this calculator answers the economic question after the scope is known.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Review our object storage workload

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.