Self-host ADAMANT IPFS Node
v0.1.0IPFS storage node for app file delivery
- Stars
- 307
- Ports
- 4000 (HTTP REST API), 4001 (libp2p TCP listener for peer connections)
ghcr.io/adamant-im/ipfs-nodeWhat is ADAMANT IPFS Node?
ADAMANT IPFS Node is a self-hosted content-addressed file storage service for application file delivery. It runs as a standalone Node.js service embedding Helia and libp2p with an Express REST API. It avoids the public DHT and Kubo API. Instead, it forms a controlled peer mesh over TCP using Noise and Yamux, where nodes exchange blocks and health data only with configured peers. Features include bounded disk usage with watermark garbage collection, deterministic replica placement via rendezvous hashing with age-based tiering, cross-node repair cycles, health checkpoints with monotonic height, and rate limits with admission control. Configured via a single JSON5 file. Deployable via Docker, Docker Compose, or source on Node.js 24. Requires a TLS reverse proxy and admin API key for production. Used by ADAMANT Messenger for attachment delivery.
Should you self-host ADAMANT IPFS Node?
ADAMANT IPFS Node scores 48/100 on selfhost.directory (how scoring works) and ranks #8 of 15 in File Storage. It has 307 GitHub stars.
It shipped 1 stable release in the past year. The latest, v0.1.0, came out on 30 September 2026.
Setup is advanced: plan for several services and some ongoing maintenance. An official Docker image is available. It is GPL-3.0-licensed and written mostly in Typescript.
Its closest alternative on selfhost.directory is juicefs (73/100, 14 582 stars). It scores higher overall, so compare the two before you pick. See ADAMANT IPFS Node vs juicefs side by side.
Features
- Administrative API key authentication
- Bounded disk usage
- Controlled peer mesh
- CORS Configuration
- Cross-node repair
- Deterministic replication
- Graceful Shutdown
- Health checkpoints
- Health monitoring endpoint
- Rate limits and admission control
- REST API for file upload/download
- Storage metrics and policy API
- Structured JSON logging
- Trusted proxy support
ADAMANT IPFS Node README
More in File Storage
AlarikAlarik is a self-hosted, open-source S3-compatible object storage in Swift with horizontal scaling, erasure coding, and a web console.
armadiettoArmadietto is a self-hosted, open-source RemoteStorage server in Node.js for personal cloud storage with modular (S3-backed) and classic (filesystem) variants.
Aurora FilesSelf-hosted open-source file storage platform with end-to-end encryption, WebDAV access, mobile apps, and OnlyOffice integration for document editing.
beamdropBeamDrop is an open-source, self-hosted file server with S3-compatible API, web UI, shareable links, and Prometheus metrics in a single ~39 MB binary.
cephSelf-hosted, open-source distributed storage cluster offering S3-compatible object, RBD block and CephFS POSIX file services from commodity hardware.
cloudboxioA lightweight Go-based file server you host yourself, offering JWT login, shareable links, a themed web interface, and embedded SQLite storage.
docker-noteaA self-hosted Docker image that packages the Notea note-taking app together with MinIO object storage in a single container, eliminating the need to run MinIO separately.
DriveLiteDriveLite is a self-hosted, open-source Google Drive alternative with end-to-end encryption, MinIO/S3 storage, built with SvelteKit and Go for privacy-first file storage.
ferrishareSelf-hosted file sharing with browser-side encryption so the server never sees content. Single container with SQLite, admin panel, rate limiting, configurable expiration.
fileshelterSelf-hosted file sharing application that lets you upload files and share them via unique URLs with expiration, password protection, and multi-file zip creation.
FrostbaseFrostbase is a self-hosted, open-source Firebase alternative on Cloudflare Workers with auth, realtime DB, SQL, storage, and remote config.
gluster-serverSelf-hosted Docker image packaging GlusterFS for Unraid and Raspberry Pi, enabling persistent storage for Kubernetes and Docker Swarm.
0 comments