# 8. Reference

## 8.1 Limits

| What | Limit |
|---|---|
| Tool file | `.html`, 2 MB (an app: its files, 2 MB each, 10 MB in all) |
| Screenshots | 4 per tool, PNG/JPG/WebP, 2 MB each |
| Title / description | 3–90 / 10–500 characters |
| Username / password | 2–40 characters / 10 characters minimum |
| Makers per tool | 10 (invitations included) |
| Tool versions kept | 10 |
| Favorites | 200 |
| Data saved by a tool | keys 1–200 characters; values 1 MB (personal), 256 KB (shared); about 20 requests per second |
| Table name | lowercase letters, digits, `_`, starting with a letter, up to 63 characters |
| Table version in Blackslate's storage | about 50 MB compressed |
| Tables and files in Blackslate's storage | 300 MB of tables per folder, and 500 MB per person (tables and files together) for all the folders they own (a shared folder counts for its owner); what lives in your own storage doesn't count. See **Storage** for what you use |
| Files of tools | JPEG, PNG, WebP, GIF, PDF, text, CSV, JSON; 10 MB per file after shrinking; 20,000 per folder |
| Offline copies on a device | 50 tools, 30 days; 2,000 reads per tool; tables up to 10 MB each, 50 MB per account; files opened 100 MB per account; files waiting to be sent 50 MB per account |
| Imported calendars | Airbnb, Booking, Abritel/Vrbo, Google, Outlook, iCloud (https only); read every hour; 1 MB per calendar, 2,000 bookings, 10 calendars per tool and folder |
| Calendars (`calendar.set`) | 20 feeds per tool and folder, 2,000 events per feed; the feed shows the last 60 days and the next 400; title 200 characters, place 200, description 2,000 |
| Seeing changes (`onChange`) | about every 3 seconds while the page is visible; nothing while it's hidden |
| E-mails sent by tools (`mail.send`, through the Runner) | plain text, 20 KB, subject 200 characters; 200 per folder and per day, 2,000 waiting; scheduled up to 400 days ahead; wait 24 hours at most after their time; content erased 30 days after |
| Showcase (public values and files) | 64 KB per value, 100 values per tool and folder; 50 published files per tool and folder |
| Inbox (public link) | 32 KB per request; 20 requests per minute per link; a daily limit per link (200 by default, up to 10,000); 1,000 requests waiting per tool; 10 public links per tool |
| Row changes by tools (`sql.exec`) | one statement, 20,000 characters, 100 parameters; saved automatically every 500 changes; at most 20,000 waiting |
| Protected table | 1,000 members writing in it; one change touches at most 10,000 rows |
| My tools | 30 pages, 150 tiles per page, 40 per folder or group; names 40 characters (tiles 60); icons kept as 96 × 96 images; a wallpaper image: 1,920 pixels on its longest side, about 1 MB |
| Notes | 200,000 characters each, 500 per data area, the last 20 versions kept; text only |
| Data warehouses | per read: 50,000,000 rows (At most, 1,000,000 by default; beyond 5,000,000, Runner 1.10), 2 hours; a data lake: 2,000 files and 4 GB per read; Browse lists 5,000 tables; Runner 1.7 or later. Sending a table (4.8): the published table, 2 hours per send, in one schema per warehouse, one block per table, a key of 10 columns at most; Runner 1.8 or later. Live queries (4.9): 50 per folder, 20 parameters each, 10,000 rows, 2 MB and 30 seconds per answer, 60 calls per minute per tool and person; Runner 1.9 or later |
| Flows | 50 flows and 50 blocks per data area; a block reads 10 tables at most; SQL 100,000 characters per block (a flow text: 90,000 per block, 50 blocks) |
| Directory (organisation) | 20,000 people, 100 columns; a link is read every night at 2:00 (Paris time), https only; more than 3 people and a fifth leaving at once: on hold; a table with a rule: 4 conditions, 1,000 parts; chains of 4 tables; teams 10 levels deep |
| Table version in your own storage | 5 GB per file; a large table (more than 2,000,000 rows or 300 MB) is computed by the folder's Runner only, the browser shows its first 200 rows (7.10) |
| Blocks in a warehouse | one select, 60,000 characters; 2 hours per block; the table's name: 63 characters, not starting with `lvn_` |
| Usage of a tool | kept 13 months; `track`: names 1–40 characters, 50 names per tool, 1,000 actions per person and per day; 200 different errors per tool (first line, 200 characters); 50 openings per person and per day |
| Folders per shared folder / depth | 1000 / 12 levels |
| Recently deleted | 30 days |
| Runner per block | 2 hours; tables up to about a third of its free disk (Runner 1.10); 1 try at a time, 6 requests per minute per folder |
| Runners per data area | 3 |
| Pairing code | single use, 30 minutes |
| AI agents (MCP) | 600 calls per hour per agent, 200 of them changes; answers 60,000 characters; 20 personal tokens per person, 30 days to 1 year |

## 8.2 Glossary

| Term | Meaning |
|---|---|
| Copy | your own version of a tool, made with **Copy**: change it as you like, the original stays as it is |
| Owner | the person who created a shared folder |
| Organisation | a shared folder for a company or an association, with admins, that invites work accounts by e-mail |
| Work account | an account tied to one organisation: as a **User** it opens the organisation's tools, as a **Creator** it also makes them |
| Data area | My Workshop, a shared folder, or a folder with separate data: where tools save data and tables |
| Public link | a secret address that opens a tool for anyone, without an account, to send to its inbox |
| Home (of a tool) | the folder where a tool lives and opens by default; elsewhere it is a shortcut |
| Maker | someone who can edit and publish a tool |
| Showcase | public tools, after review |
| Table, version | a dataset; each change makes a new version |
| Block | an SQL script that reads tables and publishes one table |
| Journal | the row changes a tool wrote with `sql.exec`, in order, until they are saved into a version |
| Protected table | a table of a shared folder where each member sees and changes only their own rows, and managers see all |
| Directory | an organisation's list of people (work e-mail, region, department, manager…), kept up to date from a table or a file; tables with a rule follow it |
| Table with a rule | a table of an organisation where each person sees the rows the directory gives them (their values, the rows they are responsible for, their team's), and admins see all |
| Table of reference | a table with a rule that other tables follow (regions ← ventes ← lignes_vente) |
| Manager | someone who **Can manage** a folder (or its owner): sees every member's rows of protected tables and their private values |
| Flow | a graph of tables and blocks, that can be scheduled |
| Note | a Markdown text kept in a folder, free or about a tool, a table or a flow; versioned |
| Flow text (leavenit-flow) | a flow written as JSON (by an AI, or by **Export**), imported with **Import a flow…** or **Update from…**; no data and never a key |
| Runner | a program on your own machine that runs a data area's schedules around the clock |
| Large table | a table of more than 2,000,000 rows (or 300 MB): the folder's Runner computes the blocks that read it, on its disk; the browser shows its first 200 rows |
| Own storage | an S3-compatible bucket you own, holding a data area's tables |
| Block in a warehouse | a block whose query (one select, in the warehouse's SQL) runs in a data warehouse that allows writing: its result becomes a table of the warehouse (`leavenit.daily_sales`, drawn in violet), never a table of Blackslate; Runner 1.11 (4.10) |
| Health | the page that gathers what asks for an action: flows that fail, are missed, paused or slower than usual, Runners offline, rows refused by a web service, the errors of your tools and their users' feedback (3.12) |
| Feedback | what the people who use a tool send its makers from its ⋯ menu (Send feedback): a kind and a text, anonymous unless they allow an answer (3.12) |
| AI agent | an AI app (Claude, Claude Code, Cursor…) connected to Blackslate by MCP: it works with your rights in the folders you choose, changes only their Dev version and asks you for promotions; it keeps an **Agent note** in each folder (3.13) |
| Description (of a table, a column) | what a table or a column means: written in one sentence, drafted by your AI (to check), or inherited from the column it is copied from; shown with where the column comes from (the SQL of its block) and its values; for Blackslate's tables and a warehouse's (4.13) |
| Send to a web service | a flow's block that sends each row of its result to one of the folder's web services, one call per row, each row once (by a column that identifies it); its table is the log of what was sent and what the service answered; on the folder's Runner (1.13); simulated in Dev or Test when the service isn't declared there (4.12) |
| Dev, Test, Prod | the three versions of a shared folder: Prod is the one everyone uses; Dev and Test have their own tables, flows, warehouses and keys, and their own version of the folder's tools (a change of a tool goes to Dev first), for admins and editors; **Promote** carries tool versions, flows and the columns of tables from one to the next, never rows or keys (4.11) |
| Usage | what a tool's makers see: how many people open it, from where, on what, whether they come back, the actions it counts (`window.leavenit.track`) and its errors; counts only, never who |
| Data warehouse | a database, cloud warehouse or data lake a company already has; a block **Read from a warehouse** sends it a query through the Runner, and only the result comes into Blackslate; with **Writing** on, a block can send its table back into one schema (**Send to a warehouse**); a tool can read it live through the **live queries** its owner declared |

## 8.3 Security and privacy, in short

- **Tools run sealed**: in a frame on another domain, without network access. A tool can't read your account, can't call any server, and only reaches its data through Blackslate, which checks your rights each time.
- **Who sees what**: your personal data is yours; a shared folder's data is visible to its members; a folder with separate data only to the people chosen. In a **protected table**, and for **private values** and **private files**, a member sees only their own; the folder's managers see everyone's. In a **table with a rule**, each person receives only the rows of their values in the organisation's directory. Tools on the Showcase are public; their users' data isn't.
- **Where data lives**: by default with Blackslate's providers (Supabase, in Europe). With **your own storage**, a data area's tables live in your bucket, at the provider and in the country you chose; you are then responsible for that place.
- **Keys**: Blackslate keeps your storage key encrypted and never shows it again. A Runner holds no storage key; Blackslate keeps only a fingerprint of its token.
- **Usage of a tool**: its makers see counts (openings, people, sources, devices, actions, errors), never who. No IP address is kept and no cookie is set; people without an account are counted from a code that changes every day. Kept 13 months.
- **AI agents** (3.13): an agent you connect acts with your rights, only in the folders you chose, and changes only their Dev version; every action is logged; you disconnect it in one click. Its sign-in works only through Blackslate's MCP server, and it never sees a key or a password.
- **Emails** are sent from `noreply@leavenit.com`. Blackslate never asks for your password by email.

## 8.4 Getting help

- Report a tool: its page → **More** → **Report**.
- Contact: the **Contact** link (account menu or footer).
- With an AI assistant: give it `https://leavenit.com/llms-full.txt` and describe what you want to do.
