Filify

Filify is a Vercel like deployment platform engineered with decentralized infrastructure. The platform provides a familiar continuous deployment experience - GitHub integration, automated builds, and one-click deployments - while leveraging Filecoin and ENS to eliminate single points of failure inherent in traditional cloud platforms.

When you deploy through Filify, your application is built on Fluence's decentralized compute marketplace, packaged into Content Addressable Archive (CAR) files, and stored on Filecoin using the Filecoin Pin. This makes it resilient to failures. Applications are served via Ethereum Name Service (ENS) domains, which resolve on-chain to IPFS content identifiers, providing human-readable addressing without DNS vulnerabilities.

The platform delivers enterprise deployment capabilities - automatic deployments, builds, and deployment management - without the architectural weaknesses of centralized infrastructure.

Filify's architecture centers on two major protocols: Filecoin for storage and ENS for addressing.

Storage Layer: When a deployment is triggered, the backend builds the project and packages the output directory into a Content Addressable Archive (CAR) file using IPLD libraries. The frontend then uses filecoin-pin to upload this CAR to Filecoin storage providers.

Naming Layer: Once the content is on Filecoin and retrievable via IPFS, we update the user's ENS domain to point to it. The backend prepares the ENS resolver transaction and encodes it as a contenthash value. The transaction calldata is sent to the frontend, where the user's connected wallet (via Reown AppKit/WalletConnect) signs and broadcasts the setContenthash transaction on Ethereum mainnet. The backend then verifies the resolver's contenthash matches the expected value, ensuring the ENS domain correctly resolves to the IPFS content.

Infrastructure: The backend is hosted on Fluence's decentralized compute marketplace, ensuring the platform itself has no single point of failure.