Technical documentation
Deep-dive guides to how the Bricks platform works — for the people who build on it.
The data API & its permissions
How the Bricks REST data API selects a tenant and enforces access — the row-level permission model behind every table, and the load-bearing difference between a tenant API key and an integrator API key.
EN · FRBackend translation
How the Bricks API localizes what it produces — assistant messages, emails and stored tenant data — and why the language of a response can come from three different places depending on what is being translated.
EN · FRFrontend translation
How the Bricks web app resolves a language, where its translations live, and how localized tenant content (media, labels) is kept separate from the app's own interface strings.
EN · FRThe RPC API & workflows
How to run server-side logic on Bricks — the two RPC surfaces, how workflows are built and triggered, the full catalogue of available nodes, and the expression rules that trip everyone up once.
EN · FRThe Brickify API
How Brickify turns an existing project into a Bricks tenant — what the endpoint actually returns, why the endpoint itself is free, and where the cost of adopting Bricks really lands.
EN · FRThe concepts graph & ontologies
What Bricks means by concept, ontology and artefact — how ontologies describe a system, artefacts are the runtime that system reads to run itself, and extension is the primitive that puts bricks together.
EN · FRCreating a tenant-spec manifest
How a selection of bricks composes into a TenantSpec, renders into an apply manifest, and instantiates a real tenant — the concrete shapes at each step and how to author a manifest by hand.
EN · FRStudio AI tools
What Studio AI can actually do — what the assistant can act on, how a two-phase orchestrator separates backend from frontend work, and the guardrails that keep it inside the platform.
EN · FRData flows
How Bricks controls where a tenant's data can go: every third-party connection is declared and signed, enforced in the browser and on the server, and listed for the people concerned.
EN · FRPrivate messages: Matrix behind BricksID
How people write to each other through BricksID over Matrix, how an organisation creates rooms for its people and links to conversations from its application, and what each party can see.
EN · FRBricks as a social network: spaces, followers and the Fediverse
How an organisation becomes a space that people follow from Bricks and from Mastodon, how it publishes to its followers or only to some of its roles, what a person reveals by following, and the workflow nodes that decide all of it.
EN · FRCompliance evidence for auditors
Where an auditor, a DPO or a risk officer starts: the principle behind Bricks's compliance evidence, one page per regulation, the limits that apply to all of them, and how to obtain the evidence.
EN · FRGDPR
What Bricks provides for an organisation's GDPR obligations: protection by design, a generated record of processing, declared processors and transfers, security of processing, retention and erasure, and what the people concerned can see.
EN · FRDORA
What Bricks provides to a financial entity that runs on it under DORA: the inventory of ICT assets, protection and detection, backups, the register of third parties, supply-chain screening and exit.
EN · FReIDAS: identification and signatures
How BricksID identifies people and lets them sign, measured against the eIDAS regulation as it applies today: the signature level offered, the evidence and its seal, long-term verification, and what is not offered yet.
EN · FReIDAS 2 and the European Digital Identity Wallet
What the 2024 revision of eIDAS changes for an organisation on Bricks, where BricksID stands today, and what in its design already fits the European Digital Identity Wallet.
EN · FRAI Act: transparency
How Bricks meets the transparency obligations of the AI Act for apps built with AI and for AI inside an organisation's processes: content marking, provenance, declared AI assistants, and the limits that remain.
EN · FRAI presets
Which AI model, run in which country, under which legal chain, processes your studio AI — a small, curated, honestly-tagged choice, and why Bricks deliberately offers more than one.
EN · FRBricksID: sign-in and signatures
How an application signs a person in with BricksID, asks them to sign a PDF, reads the outcome and checks the proof.
EN · FR