Pricing
Transparent pricing for the way you use Mindio.
Self-host forever free, buy one-year Desktop access, or buy Pro source once.
Self-hosted
Free
Forever free · Deploy on your own server
- Frontend + backend fully open source (AGPL-3.0)
- Optional prebuilt jar for a faster deploy
- Your data stays on your server
- Community support via GitHub
Desktop
$4.99/year
$19.9/year
One-year access · Renewal instructions by email before expiry · Monthly plans coming soon
- Native macOS & Windows app
- Works fully offline
- Direct access to local files
- Early-bird renewal eligibility retained
Pro Source License
$49
One-time payment · Includes 1 discounted upgrade key
- Source for Pro features
- A complete, compilable system to modify and extend
- 1 discounted upgrade key included
- For personal, non-commercial use
Optional add-on
Personal site hosting — yourname.mindio.me
$20/year · Skip the domain, HTTPS, and server setup — publish and go live.
How do I get the source code or jar after purchase?
After payment succeeds, the system automatically generates a download link and a unique upgrade key and emails them to the address you used at checkout — check your spam folder if it doesn't arrive within a few minutes.
How does the upgrade key work?
Every purchase comes with a one-time-use upgrade key, good for a discounted upgrade to the next version. A new key is issued each time you use one.
What exactly can — and can't — I do with the Personal vs. Commercial license?
Personal: for your own use only — read, learn, self-host, and modify for your own workflow. No commercial projects, no client delivery, no company or team use, and no reselling or publishing the source. Commercial: covers commercial products, client delivery, and internal business use, but you still can't resell or publicly redistribute the Pro source itself, or repackage it as a source template. Neither license lets you share the license file, activation code, or upgrade key, or strip copyright/license notices. Rule of thumb: just for yourself → Personal; the use case makes money, serves clients, or runs inside a company → Commercial.
What can I do with the open-source (frontend + backend) code?
The open-source edition ships under AGPL-3.0: you can read it, modify it, and self-host it. Personal use and internal company use are generally fine. The key boundary is AGPL's network-use clause: if you modify it and let other users interact with it over a network, for example as an external service, client system, or SaaS, you need to provide those users with the corresponding modified source code under AGPL-3.0 and keep the copyright/license notices. In short: using it yourself or internally is generally fine; building a closed-source external service on top of the open-source edition is not a good fit.