Skip to content
Sign in

S3-compatible object storage

Object storage.Without thecomplexity.

S3-compatible object storage, run for you by S&S Labs. Pay only for what you store and move. The open-source core is on its way.

Sign inView documentation
An upload, end to end
$ aws s3 cp photo.jpg s3://media/ \    --endpoint-url https://s3.swiftfs.rwupload: ./photo.jpg to s3://media/photo.jpg
  1. 01ClientAny S3 tool signs the request (SigV4)
  2. 02S3 APISignature and checksums verified
  3. 03AccessKey scope, bucket policy, quota
  4. 04Object engineBlob written and synced, metadata committed
  5. 05StorageStored, and metered to the byte

Why SwiftFS

Storage infrastructure without unnecessary complexity.

The S3 API you already use.

Point the AWS CLI, the AWS SDKs, rclone or s3cmd at SwiftFS. No new client to learn, and nothing to rewrite to leave.

Open by design.

SwiftFS Core will be published as open source. The same code runs SwiftFS Cloud.

Pay for what you use.

Storage by the GB-month, requests by the thousand, data out by the GB. No seats, no minimums.

How it works

Every request takes the same five steps.

  1. 01

    Client

    The AWS CLI, an AWS SDK, rclone or s3cmd signs each request with Signature Version 4, in a header or a presigned URL.

  2. 02

    S3 API

    SwiftFS checks the signature, then the payload's SHA-256, Content-MD5 and any CRC or SHA checksum before anything is kept.

  3. 03

    Access

    The access key's scope, the bucket's policy, quotas and rate limits decide. Every refusal is an S3 error your client understands.

  4. 04

    Object engine

    The object is written as one blob, synced to disk, and committed with its metadata in PostgreSQL. Nothing is acknowledged before both are durable.

  5. 05

    Storage

    The change is recorded to the byte in the same transaction, which is what usage and invoices are computed from.

S3 compatibility

Tested, not claimed.

Compatibility is listed operation by operation, and something is marked supported only once automated tests prove it with real clients. Versioning, lifecycle rules and server-side encryption are not there yet, and the matrix says so.

See the compatibility matrix
Supported
35
operations and features
Tested with
6
S3 clients and SDKs
  • aws-cli 2.37
  • rclone 1.75
  • s3cmd
  • AWS SDK for Go v2
  • minio-go v7
  • AWS SDK for JavaScript v3

Features

What ships today.

  1. 01

    S3 compatible

    Buckets, objects, multipart uploads, presigned URLs, bucket policies and CORS through the S3 API, verified with 6 real clients. What isn't supported answers NotImplemented instead of pretending.

  2. 02

    Uploads straight from the browser

    Your server signs a URL; the browser uploads to SwiftFS directly. Per-bucket CORS rules, presigned GETs for private files, and public-read paths for media.

  3. 03

    Access that fits each app

    Access keys limited to chosen buckets, read-only if you like, with an expiry. Revoke one in a click; the others keep working.

  4. 04

    Data you can trust

    Checksums are verified on the way in. A background scrubber re-reads what is stored and flags anything that no longer matches.

  5. 05

    Metered exactly

    Storage is billed on the average you keep over the month, measured to the byte-second. Usage and charges are in the console as they accrue.

  6. 06

    Built for teams

    Organizations with owners, admins, developers and viewers, email invitations, and an audit log of who did what.

Developer experience

Your tools already speak SwiftFS.

Set the endpoint, keep your code. Access keys come from the console with ready-to-paste configuration, and the secret is shown once.

SDKs and tools
export AWS_ACCESS_KEY_ID=…  AWS_SECRET_ACCESS_KEY=…

aws --endpoint-url https://s3.swiftfs.rw s3 mb s3://my-app-media
aws --endpoint-url https://s3.swiftfs.rw s3 cp ./photo.jpg s3://my-app-media/photos/
aws --endpoint-url https://s3.swiftfs.rw s3 ls s3://my-app-media/photos/
aws --endpoint-url https://s3.swiftfs.rw s3 presign s3://my-app-media/photos/photo.jpg --expires-in 3600

Open source

Self-host. Or let us run it.

Self-host SwiftFS

One Go binary and PostgreSQL, on your hardware and your network.

SwiftFS Core, with the S3 API, the storage engine, access control and exact usage records, will be published as open source. The self-hosting guide already shows what running it takes.

Self-hosting guide

SwiftFS Cloud

S&S Labs runs it for you: the servers, the upgrades, the monitoring.

Create an organization, invite your team, and start storing in minutes. Billed monthly for what you use, in US dollars by card or in Rwandan francs by mobile money or transfer.

Sign inCompare

Pricing

Pay only for what you use.

Estimate your bill

Billed in USDfrom 2026-10-01

StorageThe average you store over the month
USD 0.02per GB-month
Class A requestsWrites and listings: PUT, COPY, POST, LIST, multipart
USD 0.005per 1,000 requests
Class B requestsReads: GET, HEAD
USD 0.0004per 1,000 requests
EgressData downloaded from SwiftFS
USD 0.05per GB
DeletesDELETE and aborting uploads
Free

Billed in RWFfrom 2026-10-01

StorageThe average you store over the month
RWF 28per GB-month
Class A requestsWrites and listings: PUT, COPY, POST, LIST, multipart
RWF 7per 1,000 requests
Class B requestsReads: GET, HEAD
RWF 0.6per 1,000 requests
EgressData downloaded from SwiftFS
RWF 70per GB
DeletesDELETE and aborting uploads
Free

Use cases

Where SwiftFS fits.

01

Application uploads

Photos, documents and media from your users, uploaded from the browser with presigned URLs and served publicly or privately.

02

Backups and archives

Database dumps and file archives with rclone or the AWS CLI. Large files go up in parts; checksums prove what arrived.

03

Static assets and downloads

Public-read buckets for images, builds and downloads, with range requests for large files and CORS for your web apps.

Start storing.

Create an account, make a bucket, and upload with the tools you already have.

Sign inRead the quickstart