---
title: Storey
path: index
status: published
---

# Storey

Storey is the ScaiLabs **S3-compatible object storage service** — sovereign,
EU-resident storage for both ScaiLabs products and external customers, with the
same tenancy, metering, and authorization path for both.

> Storey is in active development. The storage clusters are live, the
> management API and console are running, and billing integration is being
> finished. A tested compatibility matrix will be published here before general
> availability — see [Compatibility](/docs/storey/compatibility).

## What Storey provides

- **S3-compatible API** — works with aws-cli, boto3, rclone, and other standard
  S3 tooling. Compatibility is published as an explicit, tested matrix rather
  than claimed wholesale; check it before assuming a specific S3 feature.
- **Explicit data residency** — every bucket is created in a named region
  (`nlsouth`, `nlwest`) and never leaves it. The region is your choice, is fixed
  for the life of the bucket, and nothing is silently moved or replicated
  across regions.
- **Three-site durability within a region** — objects are stored redundantly
  across three separate datacentres in the bucket's region. A region is **not**
  a geo-redundant pair: protection against losing an entire region is a second
  bucket in another region, under your control.
- **Tenant isolation** — buckets and access keys are tenant-scoped, and bucket
  names are private to your tenant. An access key belongs to one region and
  reaches only the buckets you attach it to.
- **Managed via console and API** — buckets, keys, grants and quotas are
  managed through the Storey management API and the console at
  <https://storey.scailabs.ai>. Bucket creation is a management operation, not
  an S3 call.
- **Transparent metering** — storage and egress are metered from durable,
  auditable sources, and the usage shown in the console is read from the same
  rows that are billed. Requests and ingress are metered and reported but not
  billed.

## Getting started

1. [Quickstart](/docs/storey/quickstart) — create a bucket and an access key,
   then upload your first object.
2. [Concepts](/docs/storey/concepts) — regions, tiers, buckets, keys and grants.
3. [Management API](/docs/storey/management-api) — the control-plane surface.
4. [Limits](/docs/storey/limits) — the caps worth knowing before you design
   around them.

## What is deliberately not included

Object versioning, object lock, IAM-style policy documents, per-prefix
permissions, object tagging, event notifications, and automatic cross-region
replication are **not** current features. Lifecycle rules can be configured but
their execution is not yet verified. If one of these is a hard requirement, talk
to the Storey team before building against the service — and read
[Compatibility](/docs/storey/compatibility) first, which also carries a
**Terraform state-locking warning** worth knowing before you deploy.

## Status

| Item | State |
|---|---|
| Storage clusters (`nlsouth`, `nlwest`) | ✅ live |
| Regional S3 endpoints | ✅ live |
| Management API | ✅ implemented |
| Console (<https://storey.scailabs.ai>) | ✅ live |
| Storage and egress metering | ✅ collecting |
| Billing integration | 🚧 in progress |
| Published compatibility matrix | 🚧 in progress |