Next-Gen Storage ProxySigV4 Compatible

Partition S3 storage with strict real-time quotas.

S3-Split sits transparently between your applications and upstream S3 providers. Partition physical buckets into isolated virtual prefixes, issue client keys, and enforce byte-accurate storage quotas before writing a single byte upstream.

100%

S3 SDK Drop-in

0 bytes

Quota Leaks

AWS • R2

Multi-Provider

app/storage.ts - Standard AWS SDK
typescript
// Drop-in AWS SDK v3 configuration
import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";

const s3 = new S3Client({
  region: "us-east-1",
  endpoint: "https://s3.your-domain.com",       // S3-Split Gateway
  credentials: {
    accessKeyId: "s3s_ck_live_9a7d2e4f1b8c",   // Client Key
    secretAccessKey: "s3s_sec_4f1b8c9a7d2e4f", // Secret Key
  },
});

// Real-time byte quotas enforced transparently
await s3.send(new PutObjectCommand({
  Bucket: "marketing-assets", // Managed Bucket (Virtual Prefix)
  Key: "documents/q3-summary.pdf",
  Body: fileStream,
}));
Architecture

Transparent 3-tier gateway proxy flow.

Downstream applications communicate with S3-Split using standard S3 APIs. The gateway validates SigV4 signatures, verifies byte quotas against the PostgreSQL registry, and forwards authorized requests to your configured Upstream Accounts.

Tier 1Downstream Clients

Applications & SDKs

External microservices, web apps, data pipelines, and CLI tools interact through standard AWS SDKs using their assigned Client Keys.

  • Standard SigV4 request headers
  • Custom endpoint: https://s3...
  • Zero client code modifications
PUT /marketing-assets/doc.pdf
Tier 2 • CoreS3-Split Gateway

Proxy & Quota Engine

Intercepts requests, validates signatures, maps Managed Buckets to virtual prefixes, and rejects over-quota writes before touching storage.

  • Real-time byte quota verification
  • Multipart upload part reservation
  • PostgreSQL object registry sync
✓ Quota Check: 24MB < 50MB
Tier 3Upstream Storage

Upstream Accounts

Physical object storage infrastructure provided by AWS S3, Cloudflare R2, MinIO, or Wasabi with master credentials encrypted at rest.

  • AES-256-GCM encrypted credentials
  • Transparent virtual prefix routing
  • Continuous baseline upstream scans
s3://corp-storage/tenants/t1/doc.pdf
Platform Capabilities

Engineered for multi-tenant storage governance.

Eliminate runaway S3 storage bills, partition tenant data securely, and enforce hard quotas without disrupting developer workflows or switching tools.

Storage Quota01

Real-Time Byte Quotas

Reject over-quota uploads before sending a single byte to upstream providers. S3-Split tracks active byte allocations and locks part reservations during multipart uploads to prevent concurrent overages.

Key Invariant0 Over-Allocation Leaks
Virtual Prefix Buckets02

Virtual Storage Partitioning

Carve a single upstream physical S3 bucket into hundreds of isolated Managed Buckets using virtual prefixes. Downstream apps operate with dedicated Client Keys as if they owned dedicated physical buckets.

Key InvariantBypass AWS 100-Bucket Limit
SigV4 Standard03

Drop-in S3 SDK Compatibility

Full support for AWS Signature Version 4 protocol. Downstream applications continue using official AWS SDKs, boto3, or the AWS CLI by simply re-pointing the endpoint URL and supplying their Client Key.

Key InvariantZero Code Rewrites Required
Object Registry04

Database Registry & Baseline Scan

A relational PostgreSQL registry records all Managed Objects, sizes, and ETags. Background baseline scans index pre-existing objects upon bucket registration to ensure byte-perfect quota accounting.

Key InvariantSub-Millisecond Quota Lookup
SDK Integration

Works with any standard S3 client.

No proprietary libraries or SDK wrappers. Point standard AWS SDKs, Boto3, or the AWS CLI to your S3-Split gateway endpoint and supply your tenant Client Key.

Node.js / TypeScript - @aws-sdk/client-s3
typescript
import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";

// Standard AWS SDK with zero code changes
const s3 = new S3Client({
  region: "us-east-1",
  endpoint: "https://s3.your-domain.com", // S3-Split Gateway Proxy
  credentials: {
    accessKeyId: "s3s_ck_live_9a7d2e4f1b8c",   // Client Key ID
    secretAccessKey: "s3s_sec_4f1b8c9a7d2e4f", // Client Secret Key
  },
});

// Upload to Managed Bucket (transparently mapped to upstream storage)
await s3.send(
  new PutObjectCommand({
    Bucket: "marketing-assets",
    Key: "reports/q3-summary.pdf",
    Body: fileStream,
  })
);
1. Custom Endpoint

Point endpoint to your S3-Split gateway URL.

2. Scoped Client Keys

Authenticate with generated s3s_ck_... keypairs.

3. Zero Code Changes

Keep existing upload pipelines, multipart logic, and metadata headers.

Interactive Demonstration

Experience real-time byte quota enforcement.

Drag the slider to simulate an S3 PutObject upload against a mock Managed Bucket with a 50 MB Storage Quota. Notice how the gateway calculates byte thresholds and returns S3-compliant responses instantly.

Mock Managed Bucketmarketing-assets
Virtual Prefix Bucket
Storage Quota MeterCap: 50 MB (52,428,800 B)
32.0 MB/50 MB(64.0%)
Within Quota
32 MB (33,554,432 bytes)
0 MB25 MB (50%)50 MB (100%)75 MB100 MB
Quick Presets:
Simulated Gateway Response200 OK
Protocol: S3 REST API
Gateway Proxy Response - 200 OK
http
HTTP/1.1 200 OK
x-amz-id-2: s3split-gw-proxy-node-1
x-amz-request-id: 7G9X2B01K4M9Q
Date: Tue, 22 Sep 2026 07:30:00 GMT
ETag: "a1b2c3d4e5f60718293a4b5c6d7e8f90"
Content-Length: 0
Server: S3-Split-Gateway/1.0
x-s3split-quota-status: WithinQuota
x-s3split-bytes-allocated: 33,554,432

✓ Upload Allowed: Within Storage Quota

The object fits within the allocated 50 MB byte quota. S3-Split proxies the payload upstream and writes an indexed Managed Object record to PostgreSQL.