Block editor
Headings, lists, checklists, code, images and links between notes, with Markdown shortcuts.
Notes you write once and find again
Write notes, checklists and reminders, keep them private, and share them with the team when you choose.
Notes are written in a block editor (paragraphs, headings, lists, checklists, quotes, code, dividers, links, and images by URL or uploaded to R2) with Markdown shortcuts, a / block menu and [[note title]] links with backlinks. Each note has a colour, a pin, labels and a notebook, and goes to the archive or the trash, which a daily cron empties after 30 days. Quick capture sits on the home page, with six templates (meeting, call, daily log, idea, checklist, project brief). Checklists tick, reorder and move ticked items to the bottom; one reminder per note, in IST and repeating if needed, is emailed by a cron every 5 minutes. A note is private to its author until it is shared with chosen people or the whole team, to read or edit, or through a read-only /n/<token> link with an optional expiry; owners and admins never see someone else's private notes. Search uses a D1 FTS5 index with a LIKE fallback. Autosave keeps versions to view and restore, and two people saving the same note get a choice, never a silent overwrite. Markdown and Google Keep imports, Markdown and CSV exports, POST/GET /api/v1/notes, webhooks, and Claude to summarise, turn a note into action items, clean up, translate, and answer questions only from notes the person may see.
What Notes does for you.
Headings, lists, checklists, code, images and links between notes, with Markdown shortcuts.
Private until you share it with chosen people, the team or a read-only link.
Full-text search, labels, notebooks, reminders and version history.
A suggested path for Notes. What you can do depends on your access in the app.
Type in the quick note box, or press n.
Add labels, a notebook, a colour or a reminder.
Share with people or the team, or make a read-only link.
Live host, inventory, governance, health checks, verification, dependencies and history.
Notes are written in a block editor (paragraphs, headings, lists, checklists, quotes, code, dividers, links, and images by URL or uploaded to R2) with Markdown shortcuts, a / block menu and [[note title]] links with backlinks. Each note has a colour, a pin, labels and a notebook, and goes to the archive or the trash, which a daily cron empties after 30 days. Quick capture sits on the home page, with six templates (meeting, call, daily log, idea, checklist, project brief). Checklists tick, reorder and move ticked items to the bottom; one reminder per note, in IST and repeating if needed, is emailed by a cron every 5 minutes. A note is private to its author until it is shared with chosen people or the whole team, to read or edit, or through a read-only /n/<token> link with an optional expiry; owners and admins never see someone else's private notes. Search uses a D1 FTS5 index with a LIKE fallback. Autosave keeps versions to view and restore, and two people saving the same note get a choice, never a silent overwrite. Markdown and Google Keep imports, Markdown and CSV exports, POST/GET /api/v1/notes, webhooks, and Claude to summarise, turn a note into action items, clean up, translate, and answer questions only from notes the person may see.
Uploaded business files belong to Documents and Drive; public documentation belongs to Docs; tasks with owners and dates belong to Boards.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
notes.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.