Sold by: abyo software
Deployed on AWS
Free Trial
Drop-in S3-compatible gateway that transparently compresses every object, cutting S3 storage bytes 50-80 percent for compressible data with zero application changes. This edition bills by measured savings: you pay per GB of backend storage avoided, per hour, at roughly one third of the avoided storage cost.
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
Sold by
Categories
Delivery method
Supported services
Delivery option
S4 Metered Savings via Helm chart
Latest version
Operating system
Linux
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Free trial
Try this product free for 14 days according to the free trial terms set by the vendor. Usage-based pricing is in effect for usage beyond the free trial terms. Your free trial gets automatically converted to a paid subscription when the trial ends, but may be canceled any time before that.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/unit/hour |
|---|---|---|
Metered savings (GB-saved hours) | GB of backend storage avoided by S4 compression, metered hourly | $0.00001 |
Dimensions summary
This listing uses a single usage-based dimension. You pay by GB-saved-hour, which measures the backend storage the compression gateway avoids, metered each hour. Your bill scales directly with how much storage you actually avoid, so there are no tiers or instance sizes to choose. The more compressible data you store, the more GB-saved-hours accrue. The software fee is separate from your own container compute cost. You run one metering replica, which the deployment chart enforces while metered savings billing is active.
Top-of-mind questions for buyers
A GB-saved-hour is one gigabyte of backend S3 storage the gateway avoids through compression, counted for one hour. Each hour the gateway measures the storage it is currently avoiding and bills that amount. Only compressed bytes you no longer store in S3 count toward the metered quantity.
Already-compressed inputs pass through untouched, so they avoid little or no storage and add few GB-saved-hours. Your metered cost falls when there is less to save and rises when more compressible data accrues savings. You pay in proportion to storage actually avoided each hour.
The GB-saved-hour software fee is separate from the container compute you run yourself. You deploy the gateway on your own cluster and pay those node costs directly. The deployment chart allows only one metering replica while metered savings billing is active.
abyo.net
Helpful?
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.
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
S4 Metered Savings via Helm chart
Supported services: Learn more
- 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
S4 v1.5.2 (cumulative over v1.5.1, same-day releases). Fix wave for three defects found in a live EKS end-to-end verification of v1.5.0, each reproduced on chart-default deployments: (1) Multipart / framed GETs and CompleteMultipartUpload no longer buffer whole objects in gateway memory - they stream frame-by-frame, so a single 2 GiB GET no longer OOM-kills a 2Gi-limit pod (previously reproduced 3/3); Range requests decode only the covering frames. The post-Complete index scan now uses O(parts) small ranged reads instead of a full-object transfer. (2) --read-timeout-seconds is now a progress-based idle guard instead of a whole-connection wall clock: healthy large transfers are no longer killed at 30 seconds (plain aws-cli 2 GiB uploads went from 2/6 to 6/6 in live verification); the TLS handshake is covered too; slowloris protection is preserved. New S4_READ_TIMEOUT_SECONDS env override and a helm extraArgs value for operators. (3) An interrupted CompleteMultipartUpload is now idempotently retryable: the gateway keeps a durable completion record, so a client retry that previously received NoSuchUpload (leaving an unreadable phantom object at the key, potentially replacing live data) now finishes the upload and returns success. s4 maintain (mpu-state-gc) detects and reports committed-but-unindexed objects left by crashed uploads that were never retried. (4) s4 savings now shows an always-accurate saved-bytes column (the exact metered quantity) and documents the 5 MiB multipart padding floor: with the aws-cli default 8 MiB part size, at-rest savings are limited until s4 recompact - raise multipart_chunksize to 64 MiB or more for multipart-heavy workloads. All metering behavior is unchanged and was verified byte-accurate against live MeterUsage records. Verified end-to-end on EKS with this image: 6/6 plain 2 GiB uploads, 2 GiB GET at 145 MiB gateway RSS with zero restarts, and interrupted-Complete retry recovery on a real phantom.
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. v1.5.2: healthy large transfers are never killed by the connection guard, multi-GiB GETs stream at constant gateway memory, and interrupted multipart Completes recover idempotently on retry. Multipart-heavy workloads: raise your client multipart_chunksize to 64 MiB or more so the 5 MiB part padding floor does not cap at-rest savings (see the padding-floor documentation).
-
Verify the value: run s4 savings against the ledger state file (or watch the s4_ledger_* Prometheus gauges) - the new saved column is exactly the metered GB-saved-hours quantity.
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
Self-contained EC2 AMI of the S4 transparent S3 compression gateway with CPU codecs (zstd / gzip) preinstalled. Launch on any general-purpose or compute-optimized instance (t3 / m6i / m7i / c6i / c7i), point your S3 clients at it, and cut S3 storage bytes 50-80 percent for compressible data with zero application changes.
Self-contained EC2 AMI of the S4 transparent S3 compression gateway with NVIDIA nvCOMP GPU codecs preinstalled. Launch on a GPU instance (g4dn / g5 / g6), point your S3 clients at it, and cut S3 storage bytes 50-80 percent for compressible data with zero application changes.
Drop-in S3-compatible gateway that transparently compresses every object (CPU zstd or GPU nvCOMP), cutting S3 storage bytes 50-80 percent for compressible data with zero application changes. Includes pre-deployment savings estimation and measured-savings reporting.
Cut your CloudWatch custom-metric bill: govern metric cardinality at ingest, then auto-baseline and roll up savings across your whole AWS Organization.
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.