Quick start
Just me, on this computer
Keep a personal minddy installation on this computer. The desktop app starts and stops it; no domain name or remote server is needed.
- 1 user
- Local only
- Fewer background services
Run minddy on your own computer or server.
Manage projects and issues on infrastructure you control. This guide starts with the desktop app, then walks you through a personal installation or a shared server for your team.
Two ways to run it
Choose a personal installation on this computer or a server that several people can access. Both use the desktop app.
Production setup
Several people, on a server
Give your team access to the same minddy installation on a dedicated server. Keep it on your private network or add a domain and HTTPS for remote access.
- Multiple users
- Private or public
- Dedicated host
How self-hosting works
minddy manages your projects and issues. Supabase, its required data service, handles accounts, files and live updates. The desktop app connects you to this installation.
minddy organizes the work
Create projects, assign issues and follow your team’s progress.
Supabase manages accounts and data
It provides sign-in, the database, file storage and live updates between users.
You choose where data is stored
Host Supabase yourself or use a Supabase Cloud project for your accounts, project data and attachments.
PostgreSQL alone is not supported. minddy also needs Supabase Auth, Storage, and Realtime.
Keep your encryption key safe
Choose how this instance stores workspace content and files. Encryption is enabled by default. The installer generates MINDDY_DATA_ROOT_KEY in both modes. Preserve it across updates and keep a protected recovery copy. Turning encryption off later does not decrypt already protected data.
What self-hosting includes
Manage projects, issues and accounts, export your data and connect AI assistants through MCP. Choose which AI, email, Git and notification services to configure.
minddy Cloud billing and product analytics are not required. GitHub and GitLab connections can use minddy’s connection service by default; disable it with --no-forge-relay if you want to manage those connections yourself.
Coming from minddy Cloud?
Export your Cloud data to a JSON transfer file, then import it into your own installation. The transfer includes projects, issues, comments and attachments.
1. Export from Cloud
Settings → Data → “Download my data”. You get a minddy-export-….json file with no passwords or keys inside.
2. Import on your instance
Open Settings → Data → “Import a transfer file”. Existing data is kept. If an imported item’s identifier is already in use, minddy assigns a new one and lists it in the report.
Passwords, API keys and access tokens are not transferred. Reconnect GitHub, GitLab and AI providers after importing.
After the first sign-in
Keep the maintenance guide for the version you installed. It explains how to back up, update and troubleshoot your server.
Create a restorable backup
Save the database, attachments, environment, and configuration together.
Update one release at a time
Back up, apply the published release, run checks, then reopen access.
Check your installation
Use the diagnostic command, called doctor, to find configuration, connection and service problems.