The Secure, Self-Hosted Edge Gateway IPFS Always Needed, with Logins, API Keys, GUI Control, and Web3 Site Publishing.
truthgate.io for full docs, guides, and live demos.
- Secure User Logins – Role-based accounts protect access.
- API Key Management – Scoped tokens for programmatic control.
- Clean GUI – Manage users, domains, and publishing in minutes.
/ipfs/+/webui/– Native IPFS routes, now behind auth + HTTPS.- Auto SSL & Domains – Custom domains with one-step HTTPS.
- Drag-and-Drop Publishing – Deploy WASM, SPAs, and Blazor apps in seconds.
- Web2/Web3 Hybrid Hosting – Serve both decentralized and traditional users.
- Hardened Edge Gateway – Secure IPFS exposure without the risks.
TruthGate, Kubo, and the matching ipfs CLI run together as one appliance
container. Application state, Kubo repository metadata, and Kubo blocks are
persisted separately by default.
git clone https://github.com/magiccodingman/TruthGate-IPFS.git
cd TruthGate-IPFS
cp .env.example .env
docker compose pull
docker compose up -d
docker compose logs truthgateThe default Compose image is the tested multi-platform stable release:
magiccodingman/truthgate-ipfs:stable
The first-start logs contain a generated password for the admin account.
Open https://localhost, accept the temporary self-signed fallback certificate,
and change the password.
The appliance configures Kubo as a contributing server by default: DHT server mode, TCP/QUIC/WebTransport swarm listeners, content providing, automatic storage sizing, and repository GC are enabled with persistent per-setting overrides. Inspect the live node with:
docker exec truthgate truthgate-kubo-statusFor the full persistence contract, Kubo settings, release tags, image update flow, ARM64/AMD64 publishing, and Docker-based development setup, see DOCKER.md.
To build the production image locally instead of pulling the stable release:
docker compose up --build -dDevelopment with hot reload uses the production definition plus a small override:
docker compose -f compose.yaml -f compose.dev.yaml up --buildThen open http://localhost:8080.
TruthGate is a secure edge layer for IPFS nodes.
Think Netlify, but for IPFS, self-hosted, login-protected, and actually yours.
It solves the problems developers hit with IPFS:
- Node exposure risks
- SSL/domain linking headaches
- CLI-only publishing
- Zero protection for
/apior/webuiroutes - Reliance on public gateways
Head to truthgate.io for installation, configuration, and publishing guides.
I built this out of frustration.
I wanted a way to serve Web3-native apps that actually worked, securely, reliably, and without selling my soul to centralized hosts. Now it’s real.
If you’ve ever wrestled with IPFS routing, SSL certs, or gateway hacks just to get your site online, TruthGate is for you.
Pull requests welcome.
Stars encourage me.
Issues are sacred.
Let’s fix decentralized hosting together.
Solo development done by MagicCodingMan, but under the TruthOrigin umbrella.