Mycorrhizal CRM Documentation
Mycorrhizal CRM is a self-hosted personal contact relationship management system for managing contacts, relationships, activities, notes and reminders.
The name comes from mycorrhiza, the symbiotic network fungi form with plant roots — a fitting metaphor for the web of relationships this software helps you maintain. Use this software as your digital rolodex.
Features
- Contact Management - Organize contacts with custom fields, photos, and circle-based grouping
- Relationship Tracking - Map connections between contacts
- Activities & Notes - Log meetings, calls, and personal notes
- Reminders - Set recurring reminders, delivered by email, ntfy, Gotify or browser push
- Privacy-Focused - Self-hosted, your data stays with you
Quick Links
- GitHub Repository
- Privacy & data minimization
- Supported versions — what this runs on, “supported” tiers, and the multi-user deployment shape
- Integrations — ownership, diagnostics, and what breaks if one is down
- Upgrade compatibility & supported-upgrade floor
- Service-worker updates & the recovery page
- Field compatibility matrix (DATA-01)
- Versioning policy (REL-01)
- Changelog policy (REL-05)
- Release-candidate process (REL-02)
- Breaking-change policy (MAINT-02)
- Deprecation policy (MAINT-01) · deprecation register
- Dependency upgrade policy (COMPAT-03)
- Client/server compatibility policy (ANDROID-01)
- Issue classification — labels, priority, severity, readiness bar (MAINT-03)
- PII inventory (store-by-store)
- Observability: logs, correlation IDs, and the system-event timeline
- Security checklist (OWASP ASVS L2 + API Security Top 10)
- Deployment security baseline (operator security boundary)
- Incident response & credential rotation runbook
- Security stewardship cadence — rotation intervals, key custody, and periodic reviews (#955, #956)
- Disaster recovery boundaries (what recovery guarantees exist, and where they stop)
- Migration recovery runbook
- Rebuilding the full-text search index
- Derived-data inventory (what is denormalized, how it rebuilds)
- Verifying release artifacts
- Reproducible builds (REL-04)
- Release gates — what must pass before a tag publishes (REL-03)
- Repository governance — branch/tag rulesets, required checks, commit signing (#508)