6. Your own storage
By default, Blackslate keeps a folder's tables. A folder owner can instead keep them in an S3-compatible bucket they own. Tools, blocks and flows keep working the same way: only the place where table files live changes.
6.1 How it works
- The bucket belongs to the folder owner, with a provider they choose and pay.
- Blackslate keeps a restricted access key, encrypted in its vault. It is never shown again, never sent to browsers, never given to a Runner.
- For every read or write, Blackslate checks the person's rights, then signs a short-lived address (AWS Signature V4). The browser (or the Runner) transfers the file directly between the device and the bucket.
- What you gain: no Blackslate size limit per table (up to 5 GB per table file), tables that are yours, and the possibility of a Runner (chapter 7).
- What doesn't change: calculations still run in the browser (or on a Runner). Your own storage doesn't make queries on big tables faster.
- Tables move; files don't. Moving copies the tables. Files your tools keep (
window.leavenit.files) stay where they are: those already saved stay in Blackslate's storage (and count in its 500 MB), new ones go to your bucket. Small data saved withwindow.leavenit.get/setstays in Blackslate.
Who can do what:
| Person | Can |
|---|---|
| Owner of the shared folder (or the person, for My Workshop) | connect, test, move, disconnect |
| Other members | see where the data is stored ("Data stored in Scaleway (France)…"), nothing else |
6.2 Supported providers
Blackslate only accepts these providers (the site's security rules only allow their addresses):
| Provider | Field "Region" | Address used |
|---|---|---|
| Scaleway (France) | fr-par, nl-ams, pl-waw |
s3.<region>.scw.cloud |
| OVHcloud (France) | gra, sbg, rbx, de, uk, waw, bhs |
s3.<region>.io.cloud.ovh.net |
| Hetzner (Germany) | fsn1, nbg1, hel1 |
<region>.your-objectstorage.com |
| Cloudflare R2 | auto, plus your Account ID (32 characters) |
<account id>.r2.cloudflarestorage.com |
| Backblaze B2 | eu-central-003, us-west-004, us-east-005 |
s3.<region>.backblazeb2.com |
Bucket names: lowercase letters, digits, . and -, 3 to 63 characters.
6.3 What every provider needs (the checklist)
- An empty bucket, private (no public access), dedicated to Blackslate.
- An access key restricted to this bucket, allowed to read, write and delete objects, nothing more. You get an Access key (public identifier) and a Secret key (shown once by the provider: store it in a password manager).
- A CORS rule on the bucket, so the browser may use it from leavenit.com and from apps.leavenit.com (where installed tools run). Blackslate sets it for you when your key may change the bucket's settings: Set it for me in the Storage panel, or by itself in the step-by-step guide (6.4). The request is signed by Blackslate with the key it keeps, and sent by its
storage-corsserver function; the key never leaves Blackslate. Otherwise, Blackslate shows the rule, ready to paste in the bucket's settings:
[
{
"AllowedOrigins": ["https://leavenit.com", "https://apps.leavenit.com"],
"AllowedMethods": ["GET", "PUT", "HEAD", "DELETE"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag"],
"MaxAgeSeconds": 3600
}
]
If the provider's console has no CORS screen, use the AWS command line tool, which works with every provider, set up (aws configure) with a key that may change the bucket's settings. It wants the rule in another form: save this as cors.json (Blackslate shows it, and the command with your bucket, address and region filled in):
{ "CORSRules": [ { "AllowedOrigins": ["https://leavenit.com", "https://apps.leavenit.com"], "AllowedMethods": ["GET", "PUT", "HEAD", "DELETE"], "AllowedHeaders": ["*"], "ExposeHeaders": ["ETag"], "MaxAgeSeconds": 3600 } ] }
aws s3api put-bucket-cors --bucket <bucket> --cors-configuration file://cors.json --endpoint-url https://<address> --region <region>
- No click tracking, no public website, no custom domain on the bucket: Blackslate uses the provider's own address.
Connected your storage before November 2026? The rule then only allowed leavenit.com, so an installed tool could not read or write its tables. Open the folder's Storage panel, copy the CORS setting it shows now, and paste it into the bucket again, replacing the old one.
6.4 Connecting a folder, step by step
The step-by-step guide does it one step at a time: Storage → Step-by-step guide (also offered above Workshop when Blackslate's storage is more than 80% full, and above a tool whose folder is full). It says first what each provider will ask, then the bucket, the key (Save and test), the CORS rule (set by Blackslate when the key allows it, otherwise the provider's website or the command), and the move. It remembers, on this device, where you stopped (never your keys). Each step has Ask my AI for help: a new conversation with your AI, with the details of the step, never a key.
By hand, in the panel:
- Workshop → open the shared folder (or My Workshop) → the ⋯ next to its name → Storage. For a folder with separate data (lock icon): its ⋯ → Storage.
- Use my own storage: choose the Provider, the Region (and the Account ID for Cloudflare R2), then fill Bucket, Access key, Secret key.
- Save and test. Blackslate writes, reads back and deletes a small test file through signed addresses. The result shows ✓ Write ✓ Read ✓ Delete.
- If a step fails, the panel explains why and shows the CORS text (see 6.6). Fix, then Test again.
- Move my N tables. A progress bar shows each table (reading, checking, writing, switching). Keep the page open. Tools keep working during the move. If the page closes, the tables already moved stay moved: Move the remaining N finishes the rest.
- Done: the panel shows in use. New tables go to the bucket. Copies left in Blackslate's storage are deleted after 30 days.
Going back: Move back to Blackslate copies the current version of every table back. Tables larger than Blackslate's limit are refused, with their names. Blackslate never empties your bucket: your copies stay there. Replacing the key (rotation, lost or revoked key): Storage → Replace the key. Provider, region and bucket stay locked; enter the new Access key and Secret key, then Save and test. The storage stays in use. Disconnect is possible once no table is left in the bucket (and old files have been cleaned, usually within an hour).
6.5 Provider guides
Consoles change often. If a screen differs, look for the same idea under another name, or ask your AI with a screenshot.
Cloudflare R2 (tested end to end)
- Cloudflare dashboard → R2 Object Storage → Create bucket.
- Name: e.g.
leavenit-data. - Location: Automatic, or a location hint in Europe. Do not choose the "EU" jurisdiction: it uses another address (
<account>.eu.r2.cloudflarestorage.com) that Blackslate doesn't accept yet. - Keep the bucket private (no r2.dev address, no custom domain).
- Name: e.g.
- Your Account ID: on the R2 overview page (32 characters).
- Manage R2 API Tokens (or API Tokens) → Create API token:
- Permission: Object Read & Write.
- Specify bucket: only
leavenit-data. - Copy the Access Key ID and the Secret Access Key (shown once).
- The bucket → Settings → CORS Policy → Add CORS policy → paste the JSON of 6.3.
- In Blackslate: Provider Cloudflare R2, Region auto, your Account ID, bucket, keys.
Backblaze B2
- Buckets → Create a Bucket: private, in the region you'll pick in Blackslate (e.g.
eu-central-003). - Application Keys → Add a New Application Key: allow access to this bucket only, type Read and Write. Copy the keyID (Access key) and applicationKey (Secret key).
- CORS: Backblaze's S3 interface accepts the AWS command of 6.3, with
--endpoint-url https://s3.<region>.backblazeb2.com. (B2's own "CORS rules" screen applies to its native interface; use the command to be sure.)
Scaleway
- Object Storage → Create bucket: region
fr-par,nl-amsorpl-waw, private. - IAM → create an application with a policy limited to Object Storage in this project (read, write, delete objects), then generate an API key for it: Access key + Secret key. Add ObjectStorageBucketsWrite (or use ObjectStorageFullAccess on a project dedicated to Blackslate) and Blackslate can set the CORS rule itself.
- CORS: with the AWS command of 6.3 and
--endpoint-url https://s3.<region>.scw.cloud.
OVHcloud
- Public Cloud → Object Storage → create an S3 container in a region (e.g.
gra), private. - Create an S3 user with read/write rights on this container, then its S3 credentials: Access key + Secret key.
- CORS: with the AWS command of 6.3 and
--endpoint-url https://s3.<region>.io.cloud.ovh.net.
Hetzner Object Storage
- Object Storage → Create Bucket: location
fsn1,nbg1orhel1, private. - Security → S3 credentials → generate: Access key + Secret key. Hetzner's credentials apply to the project: keep a project dedicated to Blackslate if you want them limited. With them, Blackslate can set the CORS rule itself.
- CORS: with the AWS command of 6.3 and
--endpoint-url https://<region>.your-objectstorage.com.
6.6 Troubleshooting
| What you see | Cause | Fix |
|---|---|---|
| ✕ Write, "The browser couldn't reach the bucket. Paste the CORS setting below…" | no CORS rule (or a wrong origin) | Set it for me, or paste the CORS JSON of 6.3 on the bucket, then Test again |
| Set it for me: "Your key can't change this bucket's settings" | the key is limited to objects (the safest kind) | give it the right (Scaleway: ObjectStorageBucketsWrite), or set the rule in the bucket's settings or with the command of 6.3 |
| "The storage refused the key. Check the access key, the secret key and its permissions on this bucket." | wrong key, or key not allowed on this bucket | create a new key restricted to this bucket with read + write |
| "The bucket was not found. Check its name and region." | bucket name or region differs | check spelling and the region chosen in Blackslate |
| "Test the connection first." | moving before a successful test | Test again until the three ticks are green |
| "Some tables are still in this storage. Move them back first." | disconnecting while tables are in the bucket | Move back to Blackslate, then Disconnect |
| "Your tables are in this bucket: you can replace its key, but not change the provider, region or bucket…" | changing the bucket while it is in use | Move back to Blackslate first, then connect the new bucket |
| "These tables are too large for Blackslate's storage: …" | moving back tables above Blackslate's limit | keep them in your bucket, or make them smaller |
| A tool says "The storage refused the download (403)" | the key was deleted, expired or lost its rights | create a new key with the same rights at the provider, then Storage → Replace the key |
| Cloudflare R2 bucket in the "EU" jurisdiction | address …eu.r2.cloudflarestorage.com not accepted |
create a new bucket without the EU jurisdiction (a European location hint is fine) |