Feedo is currently in open beta. Everything is free — no payments, no tokens. We are actively working on the tokenomics layer, which is expected to be ready within about a month. Until then, feel free to use the network as much as you need — we just ask that you exercise fair use and be reasonable with the storage you consume.
We're building what everyone else only dreamed about.
Feedo is the first fully decentralized search engine.
No central servers. No censorship. No filter bubbles controlled by a single company. We're destroying Web2's grip on information — one search query at a time.
Feedo is proud to be the official Decentralized Hosting Partner for global developer communities.
We are currently powering the infrastructure for CodeStorm 2026. Over a thousand developers are building the future of the web on our nodes.
Are you participating in a hackathon and want to deploy your project to the Feedo network? It takes less than 3 seconds!
- Install the Feedo Developer CLI.
- Initialize your project (
feedo init). - Deploy your site to the decentralized network (
feedo deploy).
For the full setup and deployment guide, please visit our Feedo SDK Repository (Developer CLI).
Today, the internet is controlled by three or four massive corporations. They decide what you see, what you don't see, and who gets to exist online. You can be deplatformed, shadowbanned, or wiped from the index not because you broke a law, but because they simply didn't like it.
Web3 started with a beautiful dream. The plan was right. True digital freedom. But somewhere along the way, we took a wrong turn. We got addicted to the money. Tokens, speculation, gambling on memes while the one thing that actually matters was left behind. Search. Discovery. The ability to find anything.
Think about it: we have decentralized money (Bitcoin), decentralized contracts (Ethereum), decentralized storage (IPFS) — but when was the last time you searched for something on a decentralized network? You can't. The search box still belongs to them.
That changes now.
Feedo is how we fix Web3. With a search engine that nobody controls, nobody censors, and nobody can shut down.
The dream was never about the money. It was about freedom. We're bringing it back.
Feedo is built on three independent layers that work together as a single search engine — without a single central server.
A P2P network of nodes that agree on who owns what. Names, content hashes, and identity records are validated through a PBFT consensus protocol with a reputation-based rotating committee. No single node controls the truth.
Key features: PBFT consensus, DID identity system, DNS-like name resolution, on-chain treasury via PporTreasury.sol on Polygon, 25-node testnet verified.
All content — websites, social posts, profiles, and arbitrary files — is stored using Reed-Solomon erasure coding. Every file is split into data shards + parity shards and distributed across the Kademlia DHT. If nodes go offline, the network self-heals and rebuilds lost shards automatically.
Key features: Erasure coding (30+15), Kademlia DHT storage, proactive self-healing, TTL-based garbage collection, censorship-resistant by design.
Content is converted into dense vector embeddings using machine learning models. These vectors are stored locally and indexed for semantic search — meaning you find what you mean, not just what you type. Multiple search nodes form a federated network: each node knows which semantic clusters live where, and queries are routed intelligently without a central coordinator.
Key features: Vector semantic search (384-dim embeddings), CLIP image embeddings, federated P2P search via KMeans centroids, LanceDB for local vector storage, real-time indexing via WebSocket pub/sub.
Together, these three layers form a complete search engine with no central authority, no single point of failure, and no censorship.
feedo/
├── microservices/
│ ├── consensus-node/ # PBFT consensus & name resolution (Rust)
│ ├── storage-node/ # Erasure-coded P2P storage (Rust)
│ └── search-node/ # Vector semantic search engine (Python)
├── contracts/ # PporTreasury.sol (Polygon smart contract)
└── feedo_explorer/ # Flutter cross-platform admin & search app
Each microservice has a documentation suite covering technical architecture, node operations, and production deployment.
| Document | Audience | Description |
|---|---|---|
| Technical Docs | Developers | Architecture, PBFT consensus, modules, API, testing |
| Operator Guide | Node operators | Prerequisites, config, monitoring, troubleshooting, upgrades |
| Deployment Guide | DevOps | Zero-config bare-metal deployment via install.sh, systemd, hardening |
| Roadmap | Everyone | Scaling plan from 25 to 10,000+ nodes |
| Document | Audience | Description |
|---|---|---|
| Technical Docs | Developers | Architecture, erasure coding, P2P protocol, modules, API |
| Operator Guide | Node operators | Quick start, quotas, monitoring, troubleshooting, upgrades |
| Deployment Guide | DevOps | Zero-config bare-metal deployment via install.sh, systemd, hardening |
| Roadmap | Everyone | 5-phase scaling plan (Phase 1 ✅ done) |
| Document | Audience | Description |
|---|---|---|
| Technical Docs | Developers | Architecture, vector search, federated search, modules, API |
| Operator Guide | Node operators | Prerequisites, config, monitoring, troubleshooting, upgrades |
| Deployment Guide | DevOps | Zero-config bare-metal deployment via install.sh, systemd, hardening |
| Roadmap | Everyone | 5-phase scaling plan (Phase 1 ✅ done) |
Feedo identity is wallet-native — there are no usernames or passwords.
- DID = your wallet address (
did:feedo:0x…). Connect any EIP-6963 wallet (MetaMask, Coinbase Wallet, Rabby, Trust, Brave, Phantom, OKX…). - Register once by signing
feedo register <did>— you receive 500,000 free credits. - Usage key — a separate key that signs requests but can't move funds, so your wallet's private key never leaves your wallet (or a server).
Three ways to create an identity:
- Website — open https://feedo.ink/identity.html, connect a wallet, register, and generate a usage key in one flow.
- CLI —
feedo init(creates a wallet + registers the DID), thenfeedo usage-key+feedo delegate. - SDK —
registerDid/register_did, plus delegated mode viausageKey/usage_key.
See the SDK docs for the full usage-key & delegation reference.
All three core nodes have integration tests covering real P2P scenarios.
# Consensus — 25-node PBFT test
cd microservices/consensus-node
cargo test --test integration_test_25
# Storage — erasure coding + DHT test
cd microservices/storage-node
cargo test --test integration_test
# Search — publish + query + relevance test
cd microservices/search-node
python tests/full_cycle_test.py| Test | Status | What it validates |
|---|---|---|
| 25-node consensus | ✅ Passed | PBFT, epoch rotation, fault tolerance (kill 5/25 nodes) |
| Storage integration | ✅ Passed | Upload, download, delete, erasure coding |
| Search pipeline | ✅ Passed | Publish site → index → search → relevance check |
Detailed roadmaps for each layer are available in their respective directories:
- Consensus Node Roadmap — scaling from 25 to 10,000+ nodes
- Storage Node Roadmap — from 10 GB to unlimited storage, cloud storage protocol
- Search Node Roadmap — from full replication to semantic sharding, GPU inference, DuckDuckGo-level quality
Join our Discord server to ask questions, meet the team, or apply for the technical co-founder role!
- 🐙 GitHub — Feedo SDK
- 🌐 Website — feedo.ink
- 💬 Discord — Join the Feedo Discord
- 𝕏 X — @andrii_shumko
- ✉️ Email — andrii@feedo.ink
Feedo is fully open-source and community-funded. No VCs. No tokens. Just builders.
Apache 2.0 License — see LICENSE for details.