Overview
S4 sits between your applications (boto3, aws-sdk, Spark, Trino, DuckDB, or anything that speaks S3) and your real S3 bucket, and transparently compresses each object with a codec chosen per payload: CPU zstd for text and logs, GPU (NVIDIA nvCOMP Bitcomp or zstd) for integer and columnar data, and passthrough for already-compressed inputs.
No application changes are required. S4 keeps the same S3 wire protocol, the same SigV4 authentication, and the same SDK calls. You only change the endpoint URL. Range GET requests stay fast through a sidecar frame index that is compatible with Parquet and ORC readers.
The on-backend format is open, so there is no lock-in. If you stop the gateway, the objects remain readable with the Apache-2.0 s4-codec command-line tool, the s4-codec Python package, or the s4fs fsspec adapter (pandas, pyarrow, and DuckDB can read the data without the gateway).
Operate S4 with built-in day-2 tooling. The s4 estimate command projects savings on your existing bucket before you deploy. The s4 migrate command retro-compresses objects already in the bucket. The s4 recompact command re-compresses cold data at higher levels. The s4 maintain command runs policy-driven maintenance. The savings ledger and the s4 savings command report the storage bytes and dollars actually saved in production. Prometheus metrics and a Grafana dashboard are included.
This listing bills in proportion to the value delivered: the gateway meters the storage it is currently avoiding on your backend (GB-saved hours) once per hour, so a deployment saving little pays little. The rate is set to roughly one third of the avoided S3 Standard storage cost, so the majority of the savings always stays with you. It uses the same software as the per-pod-hour S4 listing; run the gateway with --marketplace-metered-savings, a usage dimension of GBSavedHours, and a persistent savings-ledger state file (one metering replica per deployment). The same software is also available free under the Apache-2.0 license as a public container image; the Marketplace build adds metered billing through your AWS bill and is the supported procurement path for enterprises.
Highlights
- Pay for measured value: billing is per GB of backend storage avoided, per hour, at roughly one third of the avoided S3 Standard storage cost - the majority of the savings stays with you.
- Zero application changes. S4 exposes an S3 wire-compatible endpoint (SigV4, multipart, Range GET, server-side encryption). Point your SDK at S4 and keep working.
- Open format, no lock-in. Objects stay readable without the gateway through Apache-2.0 command-line, Python, and fsspec tooling.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/unit/hour |
|---|---|---|
Metered savings (GB-saved hours) | GB of backend storage avoided by S4 compression, metered hourly | $0.00001 |
Vendor refund policy
S4 Metered Savings bills hourly on measured GB-saved usage; stop or reconfigure the gateway anytime to stop software charges. Usage already incurred is generally non-refundable. If you were billed in error or a product defect prevented normal use, email aws-support@abyo.net (abyo software LLC) within 30 days with your AWS account ID, product name, and billing period. Valid refunds are processed through AWS Marketplace.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
S4 Metered Savings via Helm chart
- Amazon EKS
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
First release of the Metered Savings edition, based on S4 v1.5.0. S4 v1.5.0. Highlights: (1) HA multipart - the client-transparent multipart composite ETag now survives gateway restarts and multi-gateway deployments via durable per-part state records on the backend; a new s4 maintain action mpu-state-gc reaps crash leftovers. (2) Multipart HEAD now reports the original Content-Length (previously the stored compressed size leaked on HEAD while GET reported original sizes). (3) UploadPartCopy correctness: raw (non-S4) copy sources are re-framed through the gateway (previously the assembled object could become unreadable through the gateway), and copy-source SSE-C keys plus x-amz-copy-source-if-match/none-match preconditions are now honored. (4) New opt-in --uniform-multipart-parts pads non-final backend parts to a deterministic size for backends that require uniform part lengths (validated live against Cloudflare R2). (5) New standalone s4-codec decoder CLI (decode / inspect / index) - read S4-stored objects offline with no gateway. (6) Security: the legacy rustls 0.21 chain (RUSTSEC-2026-0098/0099/0104) was removed and quick-xml was upgraded to 0.41 (RUSTSEC-2026-0194/0195). All v1.2.x metering behavior is preserved: S4 confirms entitlement at startup (fail-closed) and reports one metered pod-hour every hour via the AWS Marketplace MeterUsage API.
Additional details
Usage instructions
S4 Metered Savings deploys on Amazon EKS via the provided Helm chart and bills in proportion to the storage it saves you (GB-saved hours), not per pod.
-
Subscribe, then follow the AWS Marketplace launch steps for this product to install the Helm chart on your EKS cluster.
-
Value-based metered billing. The chart carries the Marketplace product code and the GBSavedHours usage dimension, and runs under the service account AWS Marketplace provisions with the aws-marketplace:MeterUsage permission. S4 confirms entitlement at startup (the container exits if the pod is not entitled), then once per hour reports the storage it is currently avoiding on your backend - in GB, measured by its savings ledger - to the AWS Marketplace Metering Service. You pay roughly one third of the avoided S3 Standard storage cost; a deployment that saves nothing pays nothing (hours with less than 1 GB saved bill zero).
-
Exactly ONE replica per deployment. This billing mode requires a single metering gateway (the chart enforces replicas=1 at install time). The savings ledger persists on a PersistentVolumeClaim by default; keep it on durable storage - losing the ledger under-meters until the counters rebuild (your favor, but inaccurate).
-
Set your S3 backend endpoint at install time. Override backend.endpointUrl, for example https://s3.us-east-1.amazonaws.com - use the regional S3 endpoint for the bucket you put behind S4.
-
Point your S3 clients (boto3, aws-sdk, Spark, Trino, DuckDB, or anything S3) at the S4 service endpoint. No application code changes are required - the gateway accepts any SigV4-signed client; ETag, Content-Length, HEAD, GET and listings are all client-transparent by default.
-
Verify the value: run s4 savings against the ledger state file (or watch the s4_ledger_* Prometheus gauges) - the metered GB-saved-hours match what the ledger measures.
Documentation: https://github.com/abyo-software/s4#readme Billing-mode details: https://github.com/abyo-software/s4/blob/main/docs/marketplace/metering.md
Support
Vendor support
Community support is available through GitHub issues at https://github.com/abyo-software/s4/issues . Marketplace subscribers can email aws-support@abyo.net for best-effort response within 2 business days. Documentation, an operations runbook, and a threat model are included in the repository.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products

