OpenVibe.Zone

OpenVibe.Zone gives every OpenVibe project private storage zones at openvibe.zone. A zone is an S3 bucket of one project environment, sandbox or production.

What it does

• Default zones. Each environment has a default zone, which holds its existing objects.
• Named zones. A project creates more zones by name, each with an optional quota.
• Names are never reused. A zone's name is never given to another zone, even after it is deleted, so a URL signed for one bucket can never reach a different one.
• Access keys read, write or both. A key can be limited to some zones, and its secret is shown once.
• S3 tools. The AWS SDKs, rclone and backup tools reach zones over S3, path style.
• Large files and copies. Multipart uploads carry big objects in parts, and server-side copies (CopyObject and UploadPartCopy) move data between zones without downloading it.
• Usage. Requests, egress and stored bytes are counted per zone by the hour. The console shows each zone's month so far, and the project's usage page adds them up.
• Deletion. Deleting a zone removes every object and every copy of it. A zone holding an object under a retention hold cannot be deleted.

How it fits the network

• Zone owns the zone records and their control API.
• OpenVibe.Media owns what is inside a zone: the objects, their bytes and copies, the S3 surface, the access keys, quota enforcement and the one deletion path. Every object in a zone is an ordinary Media object, reachable through Media's own API too.
• Projects and roles come from OpenVibe.Network.
• OpenVibe.Services lists zones beside a project's other resources and can delete one.

Status

STATUS.json's stage is "alpha". Multipart uploads, server-side copies and per-zone usage were added on 2026-10-15. The S3 endpoint is s3.openvibe.media, and the control API also answers at api.openvibe.zone.