# Build brief — a focused alternative to Notion

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

## Context

**Notion** — Flexible docs, databases, wikis, and lightweight project workspace. It currently costs $12/mo.

A solo notes-and-database workspace is buildable, but Notion's block editor, permissions, sync, templates, AI, integrations, and collaboration take real product work.

This brief describes a focused, single-operator replacement for the part of Notion 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 block-based notes app with markdown-ish editor, simple databases, backlinks, templates, and local/cloud sync.

- Capture, organise, search, link, and export personal notes.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Web app framework.
- Database.
- Auth.
- Rich-text/block editor.
- Hosting.

### Data and integrations

- Optional LLM API.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### 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 notes-and-databases app to replace Notion. Requirements:

- A local web app: Node + Express + better-sqlite3, server-rendered pages with a little
  vanilla JS. No frontend framework, no build step.
- Pages are Markdown, stored in SQLite, edited in a plain textarea with a live preview
  pane (render with marked). Markdown is the format, not blocks.
- [[Wiki-style]] links between pages, with a backlinks section rendered at the bottom of
  every page.
- Simple databases: a page can define a table (columns typed text/number/date/select),
  rows editable inline, stored as JSON in SQLite.
- Full-text search across everything via SQLite FTS5, search box in the header.
- A nightly export of all pages to a folder of plain .md files, so my notes are never
  trapped in the app.
- Binds to localhost only. No accounts, no telemetry, everything on my machine.
- Out of scope: real-time collaboration, cross-device sync, and a block editor. Do not
  build auth or hosting config, this runs on my own machine.
- Include a README with setup steps 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:

- Mature block editor.
- Cross-device sync.
- Permissions.
- Database views.
- Permissions, presence, and shared workflows are difficult to simplify.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- 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:

- [AppFlowy](https://github.com/AppFlowy-IO/AppFlowy) — Open-source Notion-like workspace with databases and docs

---

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