Guides
How the common Airtable builds actually work — the decisions that matter, and the mistakes that are expensive to undo.
- How to build a client portal on Airtable — What it takes to let people log in and see only their own records when Airtable holds the data, and why the obvious way to build it exposes everything.
- How to run a website or blog on Airtable — Public pages with content in Airtable work fine until traffic arrives — the rate limit that breaks them, and why the images stop loading a few hours later.
- How to build a searchable directory on Airtable — A directory's data is public, so the risk moves from privacy to volume: why filtering and search belong on your server, and why record IDs make terrible URLs.
- When Airtable on its own is genuinely enough — The internal tool where every user already has the base — why the browser-key problem changes shape, how to scope the token, and when this stops being true.
- How to build a marketplace on Airtable — Sellers post, buyers browse, and one Airtable base has to answer to two different sets of rules — where the writes go wrong and how enquiries stay private.
- How to put a Next.js proxy in front of Airtable — Why the Airtable key belongs on the server, how caching keeps you inside the rate limit, and what Next.js gives you — and what it leaves you to build yourself.
- How to build an online shop on Airtable — What it takes to sell products with Airtable behind the shop: why the browser must never decide the price, and where Airtable stops being safe to take an order.