Storage

The hosted Maskura service connects to an S3-compatible bucket you control. Supported writes pass through the processing pipeline and are written to your storage.

Hosted requirement

Hosted access requires bring-your-own S3-compatible storage at an allowlisted HTTPS cloud endpoint. The hosted endpoint families are AWS S3 (amazonaws.com and amazonaws.com.cn), Google Cloud Storage (storage.googleapis.com), Backblaze B2 (backblazeb2.com), Cloudflare R2 (r2.cloudflarestorage.com), DigitalOcean Spaces (digitaloceanspaces.com), and Wasabi (wasabisys.com).

MinIO and arbitrary custom S3-compatible endpoints are not accepted by the hosted service. They are supported only by the self-hosted OSS gateway.

Connect your bucket

  1. Open onboarding or Storage Configuration.
  2. Select an allowlisted cloud family and enter its HTTPS endpoint, region, access key, and secret key.
  3. Save the configuration. New requests use that storage backend.

Storage credentials are write-only in the website and are never returned to the browser after you save them. You remain responsible for your provider account, bucket policy, retention settings, and storage-provider charges.

Processing charges

Maskura prepaid credit pays only for hosted processing usage: $30 per 1M successful writes, $2 per 1M successful reads, and $0.15 per GB processed after the free allowance. Successful PUT and DELETE operations count as writes. Successful GET, HEAD, and LIST operations count as reads. For successful PUT and GET operations, processed bytes are max(source bytes, stored/emitted output bytes); metadata operations, LIST, HEAD, and DELETE have zero processed bytes. Failed operations are not billed. See Pricing for the current allowance and rates.

Transformed read limits

Hosted transformed reads are currently capped at 64 MiB. Text records and complete JSON documents are capped at 8 MiB. When a transformed read cannot be streamed safely, Maskura may use a temporary encrypted local spool before returning response bytes. All such spool data shares a 256 MiB process quota, and stale artifacts are removed within a bounded cleanup window. Maskura does not provide durable object storage.