Write in your workspace. Publish to the web.
Your help center, changelog, blog or documentation already starts life as notes. BlokNotes closes the loop with a built-in headless CMS: publish notes as versioned pages and data tables as structured collections, served over a clean API.
Environments separate draft from production, scoped tokens control who reads what, and built-in forms collect submissions from your site — spam-scored and stored in your workspace.
What you get
- Sites with slugs, locales and status
- Draft and production environments
- Notes published as HTML page snapshots
- Data tables published as collections
- Versioned snapshots with rollback
- Scoped API tokens (read / submit)
- CORS origin restrictions
- Form definitions with spam scoring
- Public note sharing with one click
Pages from notes, collections from tables
Publish any note as a page snapshot — rendered HTML plus plain text, versioned each time you publish. Publish a data table as a collection with its columns frozen at publish time, ready to be queried by your front-end.
- Snapshot versioning with an explicit current version
- Rows of a collection can link to their own pages
- Multiple sites per workspace
Environments and tokens like a real CMS
Each site has environments — draft and production by default — so you can stage content before it goes live. API tokens are scoped (read or submit), origin-restricted and revocable, with last-used tracking.
Forms without a backend
Define forms per site, drop them into your website and collect submissions straight into BlokNotes — with spam scoring, origin checks and a success message you control.
Or just share a note
Not everything needs a website. Any note can be shared as a public read-only page with one click — handy for proposals, briefs and living documents.
Questions about publishing & cms
Is the BlokNotes CMS a headless CMS?
Yes — content is served as JSON/HTML over an API protected by scoped tokens, and your website or app renders it however you like. Draft and production environments keep staging safe.
Can I roll back published content?
Every publish creates a new snapshot version. The current version is explicit, so you can republish a previous state at any time.
How do CMS forms prevent spam?
Submissions are spam-scored and carry origin checks; you can restrict allowed origins per form and per token.
Who relies on this
Works together with
Data tables
Inline databases inside your notes — typed columns, summaries and row pages.
Learn moreNotes & block editor
A calm, block-based editor where every note can link to the work it describes.
Learn moreSecrets vault
An encrypted vault for credentials, with expiring, read-limited secret sharing.
Learn morePut publishing & cms to work today
Free during the public beta — every feature, no usage limits, no credit card.