Frontend engineers have long relied on centralized tools to host their sites—services like GitHub Pages, Vercel, or Netlify. But if you’re building for permanence, privacy, or permissionless access, those come with risks: DNS hijacks, takedowns, and opaque trust assumptions.
PinMe is a minimal CLI tool that lets you upload static files directly to IPFS and bind them to an ENS name. One command, zero config, no accounts.
To get started, install PinMe and deploy in seconds:
# Install globally
npm install -g pinme
# Deploy your site
pinme upload /path/to/your/dist
Why Use PinMe?
🔒 No More DNS Risks
PinMe serves your site from IPFS under an ENS name—no DNS records to hijack or manipulate.
🛡️ Always Online, Censorship-Resistant
As long as Ethereum and IPFS exist, your content stays accessible. No takedowns, no downtime.
🧾 On-Chain Integrity
Each deployment logs the IPFS hash on-chain. Anyone visiting your site verifies the content by default—no extra setup.
🚀 Edge-Level Speed
Content is cached by IPFS node operators around the globe, giving you CDN-like performance—minus the centralized stack.
🛠️ No CI/CD Required
Skip GitHub integrations, workflow YAMLs, and CI pipelines. Just pinme upload ./public and you’re live.
How It Works
Step 1- Build your site with your favorite framework:
npm run build # Hexo, Vue, React – all supported
Step 2 – Deploy:
pinme upload ./public
Step 3 – PinMe generates the IPFS hash, writes it to ENS, and provides a .eth.limo gateway for immediate sharing.
PinMe is ideal for Web3 landing pages, open-source apps, or anything where censorship resistance and ownership matter.
Give it a spin — and let your front-end live on-chain.
👉 Learn more at glitterprotocol.io
🔧 GitHub: github.com/glitterprotocol/pinme