Shared notes, meeting records, and internal updates
Small teams use Memos for short shared notes, meeting records, and internal updates. It fits teams that want a simple, self-hosted place to post and search them.
Home
Today
Standup
Shipped: the new onboarding email.
Blocked: waiting on the staging database.
#team/standup
Yesterday
Decision: we release on Tuesdays from now on. #team/decisions
đź‘Ť4
3 days ago
On-call handover #team/ops
Completed: Rotate the API keys
To do: Close the disk alert on db-2
Example memos. Yours start private.
In practice
Ways it fits the day.
These are independent starting points, not a prescribed process. Keep only the parts that match your work.
Share meeting agendas, notes, and action items
Post short how-to notes and process reminders
Collect onboarding links and tips in a tagged feed
Maintain project status updates and sprint notes
Document decisions, discussions, and team retrospectives
Link to specs and design documents with a short summary
Why Memos
The fit stays simple.
No per-user licensing
SQLite by default, with PostgreSQL or MySQL for larger setups
Set your instance name and logo
REST API and webhooks connect Memos to team tools
Self-hosting keeps team notes inside infrastructure you manage