Schemas per folder
Give a folder a schema with string, number, date, boolean and array fields, and every entry is validated against it.
CMS
Define schemas, edit frontmatter without YAML typos, and browse every entry in a table — while the content stays plain files in a repo.
---
title: The Quiet Web
slug: the-quiet-web
status: published
published: 2026-11-04
tags: [essays, design]
---
# The Quiet Web
Small sites, slow pages, and the return of **writing for people**.
A decade of feeds taught us to perform. The quiet web asks for something else.
Small sites, slow pages, and the return of writing for people.
A decade of feeds taught us to perform. The quiet web asks for something else.
CMS
The schema lives in a file. The entries live in files. Your deploy pipeline already understands both.
Give a folder a schema with string, number, date, boolean and array fields, and every entry is validated against it.
Edit metadata through a guided key-value panel with validation, instead of hand-writing YAML and hoping.
Browse a collection as a table, sort it, then click straight into any record — no folder archaeology.
Drag images in; they go to your own S3-compatible storage and a Markdown link is pasted for you.
Content stays as Markdown files in a repository, ready for a static site generator, a CI job or your own API.
Viewer, editor, admin and owner — explicit invitations, no surprise access, no shared root password.
How it works
Add a YAML schema to a collection: field names, types and which are required. One file, reviewed like any other.
Fill the fields through the frontmatter panel, then write the body in Markdown with the same editor as everywhere else.
See every entry in a table, filter to what you need, and open a record. Everything is still a file in the repo.
Pricing
Every plan writes plain Markdown. Paid plans add scale, git sync and your own storage.
Billed monthly. Cancel anytime.
For a first notebook and a first song.
$0/forever
Start freeFor people who write every day.
$9/month
Choose ProFor a content or worship team.
$29/month
Choose TeamFor organisations that want their name on it.
$99/month
Choose EnterprisePrices in USD. Your files stay yours on every plan — including the free one.
FAQ
No dark patterns, no “talk to sales” maze. If something is still unclear, the free plan is the fastest way to find out.
Start freeEvery note is a Markdown file in your workspace. On Pro and above, the workspace is pushed to your git remote on a schedule, so the same files exist in your repo. Any file can also be exported to Markdown or a standalone HTML page.
The app runs in one mode at a time — you choose it when you deploy your instance — and all three share the same editor, files, collaboration and sync underneath. Teams often run one instance for writing and another for their song library.
Your workspace is not deleted. Premium features such as git sync and custom S3 storage stop at the end of the paid period, and the workspace continues on the Free plan's limits. You can export everything before or after.
The desktop app and mobile apps keep a local copy, so you can keep writing without a connection; changes merge back into the workspace when you reconnect. The browser app needs a connection to load, then keeps a local copy of your session.
Workspaces are private to their members. Roles run from viewer to editor to owner, and invitations are explicit. If you self-host, the database, the collaboration relay and the git clone all live on infrastructure you control.
Yes. The repository builds one Docker image that runs the API, the collaboration relay, the sync worker and the static app server, alongside Postgres and Redis. Migrations and plan seeding are CLI commands on the same image.
Start with one schema
The free plan needs no card. Every entry carries frontmatter from the first one, so your static site generator already understands the content.
Web · Desktop · Mobile · Self-hosted