ZitiVault: Sovereign Object Storage

What it is

ZitiVault is S3-compatible object storage where you keep the keys to your own data. Tenants sign in with their own single sign-on, create buckets, issue scoped access keys and connect the backup and archive tools they already use.

The difference from a public cloud bucket is where the data sits and who decides: Genworx staff choose which storage backend holds each tenant's data — on-premises TrueNAS, Cloudflare R2, AWS S3, or any S3-compatible server.

Architecture

Tenant traffic reaches storage through a gateway that verifies and re-signs every request:

tenant tools ──SigV4──▶ gateway ──re-signed, streamed──▶ TrueNAS / R2 / AWS
tenant users ──SSO────▶ portal  ─┐
Genworx staff ─SSO────▶ admin   ─┴▶ API ──▶ PostgreSQL ◀── worker (usage, health)

The gateway streams request bodies with constant memory. A 5 TB archive costs the same RAM as a 5 MB object, which is what makes very large archives practical.

Built for large archives

• Multipart uploads up to 5 TiB per object.
• Streaming integrity checks — SigV4 chunk signatures and CRC trailers are verified without buffering the body.
• Constant memory regardless of object size.

Tenant isolation and control

Each tenant gets its own buckets, keys and quotas. Isolation, key scopes, quotas, metering and audit are enforced by the platform rather than relying on the underlying storage.

Access keys are scoped: a backup tool can be given write-only access to one prefix without seeing the rest of the tenant's data.

Usage is metered per tenant, so capacity and billing are visible rather than estimated.

Standards, not a proprietary client

ZitiVault speaks the standard S3 API. That means the AWS CLI, rclone, restic, Veeam, and anything else that writes to S3 works unchanged — there is no agent to install and no lock-in at the protocol layer.

Backends are reached only through the standard S3 API, with one service credential each. There is deliberately no dependency on a vendor's admin API.

Why it matters

For organisations with data-residency obligations or a policy against public cloud storage, ZitiVault gives S3-compatible tooling with the storage physically under a chosen jurisdiction — while keeping the operational model your team already knows.