Hi all,
I built MySolido — a personal data vault that runs entirely on your own PC. No cloud provider, no third-party server — just a local Solid Pod under your control.
Why I built it
There are wallets (EUDI), identity systems (Jouw.id, Athumi) and infrastructure being built across Europe. But there’s no consumer product where people actually store their stuff. MySolido fills that gap: the vault where your documents, medical records, photos, passwords and contracts live — locally, on your own machine.
What’s under the hood
- Community Solid Server v7.1.9 running locally
- Flask/Python frontend — browse, upload, search, organize
- 20 pre-configured folders (identity, medical, financial, legal, etc.)
- Full-text search across your pod
- Windows installer (.exe) and macOS (.dmg) available
What’s new since v1.0
- Bridge service — a read-only mirror of your local pod on a Dutch VPS (bridge.mysolido.com). Access your vault from your phone, share files over the internet. Local stays master, Bridge is read-only.
- Share links — token-based URLs with optional password and expiry. Recipients don’t need Solid or a WebID.
- ODRL policies — per-container usage policies (W3C Recommendation). Machine-readable rules for what recipients can do with your data.
- Consent module — record, view and withdraw consent, conforming to W3C Data Privacy Vocabulary v2.3 and ISO/IEC TS 27560:2023.
- Watermarking — PDF and image watermarks on shared files (“Shared with [recipient] on [date]”), applied on-the-fly via the Bridge.
- Profile module — structured personal attributes stored as JSON-LD with DPV vocabulary. Foundation for the “Reverse Google” intention economy concept.
- AI assistant — local RAG pipeline (Ollama + ChromaDB) that searches your documents. Hybrid mode available: local indexing + cloud API for answers. Your files never leave your PC during indexing.
- Audit logging — full log of who accessed what and when.
- ZIP export — backup your entire vault.
The bigger picture: Reverse Google
The long-term vision is what I call the Omgekeerde Google (Reverse Google): users store rich personal data locally, voluntarily signal purchase intentions anonymously, companies bid on those intentions, and users receive compensation. Inverting the surveillance advertising model. The profile module and consent system are the first building blocks.
Architecture
Your PC (master) → Bridge (read-only mirror) CSS :3000 CSS :3000 Flask :5000 Nginx + HTTPS .data/ (local) .data/ (synced copy)
Local is always master. The Bridge syncs via scp, secured with bcrypt password auth and Let’s Encrypt HTTPS.
Questions for the community
-
WebID resolution: My pod runs on localhost:3000 locally and is mirrored to a public URL. What’s the recommended way to handle WebID when the same pod exists at both addresses?
-
Sharing with non-Solid users: I’ve built token-based share links alongside WAC. Is anyone else bridging the gap between Solid access control and sharing with the non-Solid world?
-
ODRL enforcement: I’m using ODRL policies as a juridical layer (not technical enforcement). Combined with watermarking for traceability. Curious how others approach policy-driven data sharing in practice.
Links
- Website: mysolido.com
- GitHub: github.com/Wim1201/mysolido (GPLv3)
- Bridge (live): bridge.mysolido.com
- Windows installer: GitHub Releases
Feedback welcome — especially on interoperability, policy handling, and how this fits into the broader Solid ecosystem.
. Maybe this is obvious somewhere in the interface, but I don’t understand the language. Also, if I weren’t already familiar with Solid I would know how to log in to an app. I did use the POD’s url, `127.0.0.1:3000`, but I think most people’s intuition is to use the same url they use to browse the POD. In this case, `localhost:5000`, but that didn’t seem to work.