# Build brief — a focused alternative to Airtable

> **Verdict:** Partly, if you narrow it · **Buildability:** 53/100 · **Category:** Databases
> **Source:** https://www.canitbevibecoded.com/airtable
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Airtable. Verify current pricing and capabilities before acting.

## Context

**Airtable** — Spreadsheet-like database for teams, forms, automations, and interfaces. It currently costs $24/mo.

A spreadsheet database CRUD app is buildable, but Airtable's views, permissions, automations, interfaces, forms, sync, and integrations are broad.

This brief describes a focused, single-operator replacement for the part of Airtable that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Create tables/fields/views, forms, simple automations, filters, and a REST API over Postgres/SQLite.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Database.
- Schema builder.
- Grid UI.
- Auth/permissions.
- Automation worker.
- Hosted backend.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal spreadsheet-database to replace Airtable. Requirements:

- Local web app: Node + Express + better-sqlite3, one database file at
  data/base.db; the grid is Tabulator plus vanilla JS, no build step.
- Create tables and columns from the UI, typed as text, number, date,
  select, checkbox, or URL; each is a real SQLite table so other tools can
  query it.
- Inline grid editing, click-to-sort, per-column filters.
- Saved views: name + filters + sort + hidden columns, stored in a views
  table and listed in a sidebar.
- Link columns: a cell can reference rows in another table, picked from a
  dropdown, rendered as chips that click through to the linked row.
- A quick-entry form page per table at /form/<table>: one input per column,
  posts a row.
- CSV import and export per table so nothing is ever trapped.
- Localhost only, no accounts, no telemetry.
- Out of scope: multi-user permissions, automations, and hosted interfaces;
  when teammates need in, that is what Airtable is for.
- README: setup and where the database lives.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Rich field types.
- Interfaces.
- Automations.
- Sync/integrations.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [NocoDB](https://github.com/nocodb/nocodb) — Open-source Airtable-like no-code database built on existing SQL databases

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/airtable