# Build brief — a focused alternative to Coda

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

## Context

**Coda** — Doc platform that combines writing, tables, automations, and small apps. It currently costs $12/mo.

A doc with tables and buttons is buildable; Coda's editor, formula engine, packs/integrations, permissions, and team workflows make full parity difficult.

This brief describes a focused, single-operator replacement for the part of Coda 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

Build a rich doc editor, embedded tables, formulas, buttons, and simple automations.

- 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

- Rich text editor.
- Database tables.
- Formula engine.
- Auth.
- Integrations.
- 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 docs-with-tables workspace to replace Coda, single-user.
Requirements:

- Local web app: Node + Express + better-sqlite3, server-rendered pages with
  vanilla JS, no build step.
- Docs are Markdown edited in a textarea with live preview (marked); a
  fenced block naming a table, like table:Expenses, renders that table live
  inside the doc.
- Tables have typed columns (text/number/date/select/checkbox), inline row
  editing, and are real SQLite tables I can query with other tools.
- Formula columns: a JS expression over the row's other fields (price * qty)
  evaluated server-side with new Function over plain values only, recomputed
  on edit. No imports, no network access in formulas.
- Buttons in docs: a doc can declare a button that runs one whitelisted
  server action (add row with defaults, mark done); docs never execute
  arbitrary code.
- Named views per table: filter + sort saved and embeddable in any doc.
- CSV export per table, Markdown export per doc; localhost only, no
  accounts, no telemetry.
- Out of scope: collaboration, permissions, and packs/integrations. Coda's
  formula language and pack ecosystem are the product; this is my personal
  version.
- README: setup and where the data lives on disk.

## 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:

- Formula language.
- Packs.
- Permissions.
- Automations.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Permissions, presence, and shared workflows are difficult to simplify.

## 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:

- [AFFiNE](https://github.com/toeverything/AFFiNE) — Open-source workspace with docs, whiteboard, and knowledge-base features; partial Coda-lik

---

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