New techniques applied in practice: distributed storage with IPFS, content addressing and web3 solutions that work in practice.
PHP/MySQL platform to IPFS
A fully dynamic web environment converted to a static IPFS version. See the original at Abundomy.com and the decentralized version on our own node.
Read: what is IPFS and why do we choose it? →
View IPFS version →
Abundomy Money — Financial app
Pay each other for services provided without an intermediary. Original found at abundancey.com — the IPFS version runs on our own node. Testing can be done with just a valid email address.
Open the app →
Qortal — Real WEB 3.0
Started as a blockchain platform and has now grown into one mesh network technology: communicate, send files and call in private groups — completely without an IP address and without a central server.
More info about Qortal →Two types of IPFS that we run ourselves
IPFS is not one thing. We use it in two ways — public where possible, closed where necessary.
Gateway-IPFS — public
We set up a complete site or app on IPFS and serve it via our own gateway node. The content does not depend on a server, but on its own content hash (CID): Whoever has that hash can retrieve it — from us, or from any other node in the world. This is how the Abundomy site and money app above run. Also yes public IPFS mentioned.
Open our gateway →
Private IPFS — private, closed swarm
Not everything belongs on the public network. That’s why we’re running on indy.brainfusion.nl one of its own closed IPFS swarm: only our own nodes are allowed to participate, secured with their own swarm key. Files are therefore content-addressed and remain yours not findable on the public IPFS network. Uploading is done with a personal token, sharing via a link.
To Indy →Questions? Please contact us.