Independent Storage.

MeltyBase decouples asset management from the infrastructure layer. Unlike traditional SaaS platforms that lock you into proprietary storage, MeltyBase allows you to point your data to any hardware or cloud provider while maintaining a unified metadata plane.

Storage Independence Philosophy

The "Independent" in MeltyBase Storage means you own the bucket, the disk, and the encryption keys. MeltyBase acts as a high-performance orchestration layer that manages uploads, delivery, and usage tracking across any backend.

BYO-Infrastructure

Plug in your existing S3 buckets or local NVMe arrays. MeltyBase never locks you in.

Unified API

Switch storage backends with a single environment variable—no code changes required.

S3 Compatibility (BYO-Bucket)

MeltyBase supports any S3-compatible provider natively. This includes specialized providers like Wasabi, Cloudflare R2, DigitalOcean Spaces, or self-hosted Minio clusters.

// Environment Configuration

STORAGE_STRATEGY=s3

S3_BUCKET=my-private-assets

S3_REGION=us-east-1

AWS_ACCESS_KEY_ID=...

Local NVMe Storage

For air-gapped environments or maximum performance, MeltyBase can store assets directly on the host's filesystem. This is ideal for bare-metal servers with high-speed NVMe arrays where zero-latency I/O is critical.

  • Path-based Isolation: Each project is isolated in its own Unix directory path.
  • Direct I/O: Minimal abstraction overhead compared to cloud storage.

Metadata Vaulting

Every asset—regardless of where it is physically stored—is recorded in the MeltyBase Metadata Vault. This Postgres-backed plane stores critical information including ID, MimeType, Size, and custom Tags.

{
  "id": "770e8400-e29b-41d4-a716-446655440001",
  "name": "audit_report_q1.pdf",
  "storage_path": "project_uuid/asset_uuid.pdf",
  "size": 1048576,
  "mime_type": "application/pdf",
  "tags": ["financial", "audit"]
}

Secure Presigned Access

Assets are never publicly exposed. MeltyBase utilizes Presigned URLs and Authenticated Proxies to ensure that only authorized users can access specific files. By default, access tokens expire after 15 minutes, ensuring total control over data egress.

  • S3 Presigning: Native AWS SDK v2 presigned URLs.
  • Local Hub Proxy: All local assets are served through the /v1/hub/assets/ endpoint with full JWT verification.