Notes apps are where people put the things they would never post: ideas, drafts, passwords they meant to move later, plans. Memos keeps that on a server you own, in a plain markdown timeline, and it is small enough that the hosting is an afterthought.
What you get
- Markdown notes in a timeline, with tags and a daily review
- A public profile page for the notes you decide to share
- Capacity sized to your usage, including notes, attachments and the selected database
- Offshore, no KYC, crypto billing, with an optional Tor address
Get it running
Choose capacity for notes and attachments
Choose a supported VPS with the Impreza Agent online and room for the installed Memos version, attachments, database growth and backup operations. Check actual usage before placing several apps on the same host.
Install it in one click
Install Memos from the catalog with a hostname such as notes.example.com. That domain becomes the canonical URL for shared notes and your profile page. See how one-click installs work.
Create your account straight away
Register as soon as it is up, before the address is anywhere else, and close signups if you are the only user.
Start writing
Use tags from the start, since they are what makes the timeline searchable months later.
Memos can publish individual notes and a profile page. On a public hostname, anything marked public is readable by anyone with the link and indexable by search engines. Check the visibility of a note before you paste anything into it you would not put on a website.
People put credentials in notes because it is convenient, and then they stay there in plain text. Keep secrets in a vault built for them, such as Vaultwarden, and keep your notes for notes.
An optional onion address can provide another access route for a private journal. It does not automatically close public routes or published ports. Keep authentication and note visibility configured, and review the Tor publishing guide before relying on an access model.
Review the database backend and attachment storage used by your Memos instance. Notes, uploaded resources and configuration can require different recovery steps; do not assume a single database file contains everything.
Keep notes, attachments and visibility together
Use app inspection and maintenance for the supported deployment and verify note visibility after configuration changes. Keep private notes and attachment links out of shared diagnostic output.
Before an upgrade, review app backups to Impreza S3 and map both the database and uploaded resources to covered storage. External attachment storage needs a separate plan. Use the database recovery method appropriate to your installed version and test that notes and their attachments can be opened together.
For migration between compatible servers, check shared URLs and access settings before switching the hostname. Preserve the original deployment record needed by the integrated restore process and keep secrets in a password manager rather than in notes.
Choose the recipe and plan your updates
The Impreza catalog offers an updated Memos recipe for new installations. A catalog update does not upgrade an existing app or convert its data. Review the version available in My Apps, back up the app’s covered data and follow the application’s supported upgrade path before changing an installed instance. Confirm the restored or upgraded app’s important functions before moving users to it.
For the installation flow and version shown at deploy time, use the app catalog guide.
Start now
Spin up an offshore VPS and install Memos from the catalog, or read the documentation.