GoreeCloud Memos

GoreeCloud Memos is the lightweight, self-hosted quick-capture notes application in the GoreeCloud ecosystem.

This repository is a GoreeCloud-maintained fork of the MIT-licensed Memos project. GoreeCloud keeps upstream provenance explicit while owning the product experience, privacy defaults, hardening, Glaze presentation layer, release process, and ecosystem integration.

Current state

Lifecycle: Forge / Development — not production-approved, not Seal-qualified, and not Anchor-qualified.

The current rebuild line starts from upstream Memos v0.31.0 at commit 2b2192d4e153bd04f1d325b60fd880cf00d68b01. At the October 9, 2026 assessment, upstream main had advanced to d5df8915f70a108971f9bf01151ecd3de3e0c91f, 46 commits beyond the stable baseline; unreleased upstream changes are reviewed separately instead of silently entering GoreeCloud.

GoreeCloud direction

• Private-first self-hosting and data ownership.
• Fast Markdown-native capture with search, tags, spaces, attachments, archive, export/import, and API access.
• Glaze V1.7 / 1.7.0 design authority, with repository-local acceptance still required.
• Canonical GoreeCloud Memos icon from GoreeCloud/branding-assets.
• No required advertising, analytics, hosted control plane, remote font, or external AI service for core operation.
• Explicit upstream maintenance and security-patch intake rather than an untracked source copy.
• All nine Integral Platform Systems are evaluated; runtime integrations remain evidence-gated.

Build

Backend:

go build ./cmd/memos

Frontend:

cd web
pnpm install --frozen-lockfile
pnpm lint
pnpm test
pnpm build

Android and Linux development packages

The experimental Android APK is an HTTPS-only WebView companion for a Memos server. It does not store offline-native notes. See Android Dev build for signing and install limits.

The experimental Debian AMD64 package hosts Memos only on the local loopback interface and opens its embedded interface in the default browser. It does not replace an existing VPS deployment. See Linux Dev package for its data location and build instructions.

These are Development artifacts; installation or a successful HTTP smoke test does not establish production, Stable, Seal, or Anchor readiness.

Recovery snapshot tools

Database-only snapshot:

memos snapshot sqlite --data /path/to/memos-data --output /safe/location/memos.db

SQLite plus all relative managed-local attachment files referenced by that exact snapshot:

memos snapshot sqlite-local --data /path/to/memos-data --output /safe/location/memos-recovery

Verify an existing bounded SQLite + managed-local bundle without restoring it:

memos snapshot verify-sqlite-local --bundle /safe/location/memos-recovery

Bundle creation and verification fail closed on missing/mismatched files, unsafe paths, manifest drift, database integrity failures, and unexpected bundled files. S3 objects, deployment configuration, absolute LOCAL references, reusable secrets, scheduling, retention, and restore orchestration still require separate recovery handling; see Backup and recovery.

Documentation

• Project specifications
• Competitive objectives
• Project record
• API
• Architecture
• Implemented features
• Planned features
• Security
• Authentication
• Search and saved views
• Webhooks
• Privacy
• Outbound network behavior
• Privacy Shield integration
• Manager integration boundary
• Observability integration
• Backup and recovery
• Performance
• Database compatibility
• Everkeep integration
• Glaze adoption
• Upstream maintenance
• Validation
• Contributing
• Release and rollback
• Changelog

Licensing and provenance

The inherited Memos source remains MIT-licensed. See LICENSE, NOTICE.md, and provenance/upstream.json. GoreeCloud modifications do not erase upstream attribution.