Operations · Side quest build
Build your own Airtable
One opinionated workflow beats a blank database builder. Airtable charges $24–$54 per person per month — that’s $288–$648 a year per person — for something you can replace with focused software of your own. Here is the honest scope, the honest timeline, and the exact prompt to hand your coding agent.
Who this replacement is for
This build targets an operations team tracking a single repeatable process. The goal: manage records through a fixed workflow with views tailored to the work. If you need more than that, keep paying — the point of building it yourself is owning a tool shaped exactly like your workflow, not re-implementing a venture-funded roadmap.
Same build, different logo: this v1 also replaces Baserow and Grist — they all solve the same core job.
How long it actually takes
One number would be a lie, so here are three. Each tier is a real, usable product — pick the one that matches how much of Airtable you actually use.
| Estimate | What you get |
|---|---|
| 3 days | typed fields, table view, csv import |
| 2 weeks+ | kanban views, comments, attachments, simple automations |
| 3 months+ | schema designer, formulas, linked bases, extension platform — the part you should probably skip |
What a minimal Airtable alternative needs
- typed fields for text, status, person, date, number, and attachment
- table, kanban, and filtered saved views
- record detail with comments and activity history
- CSV import and export with a mapping preview
- simple automations for status changes and overdue records
Data model
Record, FieldDefinition, View, Comment, AutomationRule
Integrations
email, webhooks, object storage
Capability context
Astro, D1, R2
The guardrail
Validate every value against the field schema and keep attachment access private.
Deliberate non-goals
Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
The complete build prompt
Copy this into your coding agent of choice. It is scoped for a useful v1 — journeys, screens, business rules, data model, security, tests, and acceptance scenarios included. Pick your stack:
You are building a production-ready software product named “Tableflow”, a deliberately focused alternative to Airtable. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: an operations team tracking a single repeatable process. Primary outcome: manage records through a fixed workflow with views tailored to the work. Product principle: optimize the exact workflow below instead of copying the full breadth of Airtable. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. An admin imports a CSV, maps columns to the fixed workflow fields, reviews validation errors, and creates only valid records after confirmation. 2. An operator opens a saved view, edits a record, changes status, adds a comment and attachment, and sees each action in its history. 3. A status change matches an automation rule, queues an email or webhook, and exposes success or retryable failure on the record timeline. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Workflow dashboard: record totals by status, overdue count, recent activity, saved views, create record, import, and export actions. 2. Table and kanban views: configured columns, sorting, filters, pagination, bulk selection, drag status changes, and saved-view indicator. 3. Record detail: typed fields, validation, comments, private attachments, assignee, due date, activity timeline, archive, and restore. 4. Import and automations: mapping preview with row errors; rule list with trigger, conditions, action, run history, pause, and test controls. CORE CAPABILITIES 1. typed fields for text, status, person, date, number, and attachment 2. table, kanban, and filtered saved views 3. record detail with comments and activity history 4. CSV import and export with a mapping preview 5. simple automations for status changes and overdue records DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Field definitions are configured in code or seed data for one workflow; every write is validated against type, requiredness, and allowed status values. 2. Kanban moves use the same status transition service as the detail form and atomically record actor, old value, new value, and time. 3. CSV import has a dry-run phase, stable row numbers, explicit date parsing and does not persist anything until the user confirms the summary. 4. Automation evaluation happens after a committed change, uses an event id as its idempotency key, and never blocks the user’s save. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Record, FieldDefinition, View, Comment, AutomationRule. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Astro pages and ordinary HTML forms. Use HTMX for form submissions, partial navigation, and server-driven updates, then Alpine.js only for small local browser state. The core workflow must remain understandable if either enhancement layer fails. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with the AHA stack: Astro for routing, layouts, and server-rendered pages; HTMX for interactions that benefit from HTML fragment responses; and Alpine.js for small, local interface state. Prefer Cloudflare D1 for relational persistence, R2 for object storage, Workers for server endpoints and scheduled work, Durable Objects only for coordinated real-time state, and Workflows or Queues for durable background jobs—but only when the product requirements call for them. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, D1, R2 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with email and webhooks and object storage. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Validate every value against the field schema and keep attachment access private. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. An import containing valid and invalid rows reports each issue and creates exactly the confirmed valid subset with no partial surprise. 2. A disallowed status transition fails consistently from table, kanban, API, and record screens while preserving the original record. 3. A webhook action retried after timeout produces one recorded automation outcome and does not duplicate an already accepted destination write. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
You are building a production-ready software product named “Tableflow”, a deliberately focused alternative to Airtable. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: an operations team tracking a single repeatable process. Primary outcome: manage records through a fixed workflow with views tailored to the work. Product principle: optimize the exact workflow below instead of copying the full breadth of Airtable. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. An admin imports a CSV, maps columns to the fixed workflow fields, reviews validation errors, and creates only valid records after confirmation. 2. An operator opens a saved view, edits a record, changes status, adds a comment and attachment, and sees each action in its history. 3. A status change matches an automation rule, queues an email or webhook, and exposes success or retryable failure on the record timeline. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Workflow dashboard: record totals by status, overdue count, recent activity, saved views, create record, import, and export actions. 2. Table and kanban views: configured columns, sorting, filters, pagination, bulk selection, drag status changes, and saved-view indicator. 3. Record detail: typed fields, validation, comments, private attachments, assignee, due date, activity timeline, archive, and restore. 4. Import and automations: mapping preview with row errors; rule list with trigger, conditions, action, run history, pause, and test controls. CORE CAPABILITIES 1. typed fields for text, status, person, date, number, and attachment 2. table, kanban, and filtered saved views 3. record detail with comments and activity history 4. CSV import and export with a mapping preview 5. simple automations for status changes and overdue records DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Field definitions are configured in code or seed data for one workflow; every write is validated against type, requiredness, and allowed status values. 2. Kanban moves use the same status transition service as the detail form and atomically record actor, old value, new value, and time. 3. CSV import has a dry-run phase, stable row numbers, explicit date parsing and does not persist anything until the user confirms the summary. 4. Automation evaluation happens after a committed change, uses an event id as its idempotency key, and never blocks the user’s save. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Record, FieldDefinition, View, Comment, AutomationRule. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Render with React Server Components by default. Use Server Actions for authenticated form mutations and add Client Components only for interactions that genuinely require browser state, browser APIs, drag-and-drop, or live updates. The core workflow must remain understandable before client-side JavaScript finishes loading. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Next.js, the App Router, and TypeScript. Use Server Components by default, Server Actions for authenticated mutations, and Route Handlers for public APIs, OAuth callbacks, webhooks, feeds, uploads, and downloads. Use PostgreSQL through Drizzle ORM with versioned migrations and an isolated test database. Access S3-compatible object storage through a server-only adapter, and run slow or retryable work in a real job or workflow system instead of the request lifecycle. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, D1, R2 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with email and webhooks and object storage. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Validate every value against the field schema and keep attachment access private. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. An import containing valid and invalid rows reports each issue and creates exactly the confirmed valid subset with no partial surprise. 2. A disallowed status transition fails consistently from table, kanban, API, and record screens while preserving the original record. 3. A webhook action retried after timeout produces one recorded automation outcome and does not duplicate an already accepted destination write. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
You are building a production-ready software product named “Tableflow”, a deliberately focused alternative to Airtable. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: an operations team tracking a single repeatable process. Primary outcome: manage records through a fixed workflow with views tailored to the work. Product principle: optimize the exact workflow below instead of copying the full breadth of Airtable. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. An admin imports a CSV, maps columns to the fixed workflow fields, reviews validation errors, and creates only valid records after confirmation. 2. An operator opens a saved view, edits a record, changes status, adds a comment and attachment, and sees each action in its history. 3. A status change matches an automation rule, queues an email or webhook, and exposes success or retryable failure on the record timeline. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Workflow dashboard: record totals by status, overdue count, recent activity, saved views, create record, import, and export actions. 2. Table and kanban views: configured columns, sorting, filters, pagination, bulk selection, drag status changes, and saved-view indicator. 3. Record detail: typed fields, validation, comments, private attachments, assignee, due date, activity timeline, archive, and restore. 4. Import and automations: mapping preview with row errors; rule list with trigger, conditions, action, run history, pause, and test controls. CORE CAPABILITIES 1. typed fields for text, status, person, date, number, and attachment 2. table, kanban, and filtered saved views 3. record detail with comments and activity history 4. CSV import and export with a mapping preview 5. simple automations for status changes and overdue records DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Field definitions are configured in code or seed data for one workflow; every write is validated against type, requiredness, and allowed status values. 2. Kanban moves use the same status transition service as the detail form and atomically record actor, old value, new value, and time. 3. CSV import has a dry-run phase, stable row numbers, explicit date parsing and does not persist anything until the user confirms the summary. 4. Automation evaluation happens after a committed change, uses an event id as its idempotency key, and never blocks the user’s save. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Record, FieldDefinition, View, Comment, AutomationRule. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Blade views and ordinary forms. Use Livewire for focused server-driven interactions and Alpine.js only for small local interface state. The core workflow must remain understandable without relying on a client-side application shell. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Laravel, PHP, Blade, Livewire, and Alpine.js. Use controllers and Blade forms for durable navigation, Livewire for focused interactions, Form Requests for validation, Policies and Gates for authorization, and small application actions or services for domain transitions. Use Eloquent with migrations, database constraints, and transactions; Laravel Storage for private S3-compatible files; queued Jobs for retryable work; the Scheduler for recurring work; and Notifications or Mail for email. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, D1, R2 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with email and webhooks and object storage. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Validate every value against the field schema and keep attachment access private. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. An import containing valid and invalid rows reports each issue and creates exactly the confirmed valid subset with no partial surprise. 2. A disallowed status transition fails consistently from table, kanban, API, and record screens while preserving the original record. 3. A webhook action retried after timeout produces one recorded automation outcome and does not duplicate an already accepted destination write. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
You are building a production-ready software product named “Tableflow”, a deliberately focused alternative to Airtable. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: an operations team tracking a single repeatable process. Primary outcome: manage records through a fixed workflow with views tailored to the work. Product principle: optimize the exact workflow below instead of copying the full breadth of Airtable. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. An admin imports a CSV, maps columns to the fixed workflow fields, reviews validation errors, and creates only valid records after confirmation. 2. An operator opens a saved view, edits a record, changes status, adds a comment and attachment, and sees each action in its history. 3. A status change matches an automation rule, queues an email or webhook, and exposes success or retryable failure on the record timeline. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Workflow dashboard: record totals by status, overdue count, recent activity, saved views, create record, import, and export actions. 2. Table and kanban views: configured columns, sorting, filters, pagination, bulk selection, drag status changes, and saved-view indicator. 3. Record detail: typed fields, validation, comments, private attachments, assignee, due date, activity timeline, archive, and restore. 4. Import and automations: mapping preview with row errors; rule list with trigger, conditions, action, run history, pause, and test controls. CORE CAPABILITIES 1. typed fields for text, status, person, date, number, and attachment 2. table, kanban, and filtered saved views 3. record detail with comments and activity history 4. CSV import and export with a mapping preview 5. simple automations for status changes and overdue records DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Field definitions are configured in code or seed data for one workflow; every write is validated against type, requiredness, and allowed status values. 2. Kanban moves use the same status transition service as the detail form and atomically record actor, old value, new value, and time. 3. CSV import has a dry-run phase, stable row numbers, explicit date parsing and does not persist anything until the user confirms the summary. 4. Automation evaluation happens after a committed change, uses an event id as its idempotency key, and never blocks the user’s save. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Record, FieldDefinition, View, Comment, AutomationRule. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Rails views and ordinary forms. Use Turbo for navigation, submissions, and server-driven updates, then Stimulus only for small browser-side behavior. Do not turn the product into a client-side SPA, and keep the core workflow usable when enhancement fails. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Ruby on Rails and Hotwire: Turbo for navigation, form submissions, and server-driven updates, and Stimulus for small browser-side behavior. Use RESTful controllers with strong parameters and explicit authorization, with domain transitions in testable models or small application services. Use Active Record migrations plus database-level constraints and transactions; Active Storage with an S3-compatible service for private files; Active Job with a durable queue backend for retryable work; Action Mailer for email; and Action Cable only when live updates are required. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, D1, R2 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with email and webhooks and object storage. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Validate every value against the field schema and keep attachment access private. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. An import containing valid and invalid rows reports each issue and creates exactly the confirmed valid subset with no partial surprise. 2. A disallowed status transition fails consistently from table, kanban, API, and record screens while preserving the original record. 3. A webhook action retried after timeout produces one recorded automation outcome and does not duplicate an already accepted destination write. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
Build just one piece
Not ready to replace all of Airtable? Fine. These are the peculiar sub-problems hiding inside it — the parts that are actually interesting to build. Each one is a standalone prompt, scoped to an evening, no strings attached to the full build.
The import that changes nothing until you say soDry-run everything, report by source row, persist only on confirm.
Build a two-phase CSV importer for a workflow tracker: a dry run that finds every problem, then a commit that holds no surprises. Phase one parses the file and maps columns to the workflow's typed fields, previewing the first rows post-mapping. Validate every row against the schema: required fields, allowed status values, dates parsed against an explicitly selected format (never guessed), numbers, and person fields matched to known users. Every error carries a stable row number from the source file, so an unknown-status error on row 847 is checkable in the original spreadsheet. Nothing persists during the dry run. The summary states exactly what will happen: how many rows are valid and will be created, how many are invalid and will be skipped, all listed. Only explicit confirmation commits — atomically, the valid subset only. If the process dies mid-commit, either everything landed or nothing did. Make the error list exportable, because fixing the file and re-running is the natural workflow. Done when: a mixed-validity file reports each issue with its source row number, nothing is persisted before confirmation, and a crash mid-commit leaves zero partial rows.
One status service to rule the kanban, the table, and the formEvery surface calls the same transition function, or the audit log lies.
Build a single status-transition service that every surface of a record tracker shares: table inline edit, kanban drag, record detail form, and any API caller. One function owns the rules: which transitions are legal from each status, what each requires (a record cannot reach Done with required fields missing), and what happens on success. It validates, applies the change, and writes an activity event — actor, old value, new value, timestamp — in the same transaction. No caller can skip the validation or the event: the kanban drag handler is a thin wrapper that derives the target status from the destination column and calls the exact same code path as everyone else. Uniform failure matters as much as uniform success: a disallowed transition returns the same structured error everywhere, and the kanban reverts the card to its origin column with the message shown — not a silent snap-back. Handle concurrency with a version check: two simultaneous moves of one record resolve to one winner, and the loser learns the record changed. Done when: an illegal transition fails identically from all four surfaces, every status change has exactly one activity event with old and new values, and a lost concurrent move reverts visibly.
Automations that fire once, even when retried twiceEvaluate after commit, key by event id, retry without re-firing.
Build the automation runner for a record tracker: rules like when-status-becomes-Shipped-call-this-webhook, fired exactly once per change and never blocking the human. Evaluation happens after the triggering change commits, not inside the save: the transition writes an event with a unique id, and a queue consumer evaluates rules against events. The event id doubles as the idempotency key — a consumer crash and redelivery re-evaluates, finds the run already recorded, and skips. Each rule execution is a run with states: pending, succeeded, failed, retrying. Webhook calls include the event id so receivers can dedupe; a timeout schedules a bounded backoff retry, and the ambiguous case — timeout after the request may have landed — retries with the same key rather than minting a fresh delivery. Email actions check for an existing send record before sending. Every run appears on the record's activity timeline with its outcome, and terminal failures expose a manual retry. Done when: forced redeliveries produce one recorded run per event per rule, a webhook retry after timeout cannot double-deliver to a dedupe-aware receiver, and a slow automation never delays the user's save.
Typed fields without a schema designerOne schema in code, one validator, every write path obeys.
Build a typed-field engine for a fixed-workflow tracker: field definitions declared in code, one validator enforcing them everywhere. Each definition declares a key, a type (text, number, date, status, person, attachment), requiredness, and constraints: allowed status values, number ranges, text lengths. From this single source derive everything — form inputs, table cell renderers, sort behavior, and above all one validate-and-coerce function that every write path calls: the detail form, inline table edits, CSV import, and automation actions. Coercion rules live here too: trim text, parse a numeric string into a number for number fields, resolve a person by email or id, normalize dates to one canonical stored form. Reject unknown keys outright so stray columns never creep into records. Errors come back structured — field key, rejected value, reason — so every surface renders them natively instead of parsing message strings. The payoff test: change a field's allowed statuses in the definition and watch every surface update without touching any of them. Done when: an invalid value fails identically via form, inline edit, and import, coercion is consistent across all paths, and no write can bypass the validator.
Frequently asked questions
How long does it take to build your own Airtable?
A basic version — typed fields, table view, csv import — takes about 3 days. Roughly 2 weeks+ gets you a solid v1 with kanban views, comments, attachments, simple automations. Matching everything Airtable really does (schema designer, formulas, linked bases, extension platform) is closer to 3 months+, which is exactly why you should scope down instead.
How much does Airtable cost if I keep subscribing?
Airtable runs $24–$54 per person per month on public paid plans, which is $288–$648 per year for every person on your team. A focused self-built replacement costs your build time plus close-to-zero hosting.
What stack should I use to build a Airtable alternative?
The build prompt on this page ships in four flavors: the AHA stack (Astro, HTMX, Alpine.js), Next.js, Laravel, and Ruby on Rails. The capability context for this product is Astro, D1, R2. Pick the stack you already know — the scope matters more than the framework.
What features does a minimal Airtable replacement need?
A useful v1 needs: typed fields for text, status, person, date, number, and attachment; table, kanban, and filtered saved views; record detail with comments and activity history; CSV import and export with a mapping preview; simple automations for status changes and overdue records. Everything else is scope creep until you personally miss it.
What should I deliberately not build?
Do not support arbitrary formulas, linked bases, extensions, or a schema designer in v1.
Does this build also replace Baserow and Grist?
Yes. Airtable, Baserow and Grist all solve the same core job — manage records through a fixed workflow with views tailored to the work. The scoped v1 on this page covers what most people use any of them for, so one focused build replaces whichever you currently pay for.