Storage

Maskura connects to an S3-compatible bucket you control or provides managed object storage when you do not have one. Supported writes pass through the processing pipeline before they are stored.

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) and Backblaze B2 (backblazeb2.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. They are distinct from the Maskura API key used by callers. See Credentials and workspaces for the complete map. You remain responsible for your provider account, bucket policy, retention settings, and storage-provider charges.

Managed storage

Managed storage is S3-compatible object storage for a workspace. It is available through MCP or the S3 API and has 1 GiB of visible capacity included per workspace. Maskura does not claim replicated or multi-provider durability.

Objects are limited to 64 MiB for both source and stored output. Standard single PUTs support JSONL, JSON, CSV, TSV, plain text, and Avro OCF. Client-driven S3 multipart uploads are supported and durable; presigned destination PUTs are not supported; unsupported binary PUTs are rejected.

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.