Connect or upload
GitHub repo, ZIP archive, or API — same deploy pipeline.
…
Static hosting
No servers to manage
Deploy your site. Stay online globally.
Connect GitHub or upload a ZIP. Get a live preview in minutes, connect a custom domain, and roll back when you need to — with the same predictable deploy flow every time.
deploy · preview
Connecting
- Upload
- Build
- Publish
- Live
Preview URL
https://preview.ipfshost.io/my-app
docs.example.com
Connected
Rollback ready
…
Regions
…
Deploys today
…
Uptime
…
Operational transparency
Live deploy and uptime metrics on our status page — no marketing fluff.
Built for production
Rollback, release history, and deployment health where you deploy — not buried in logs.
Minutes to first preview
Templates and guided onboarding — ship a static site before you configure DNS.
Use cases
What are you shipping?
Pick a starting point — we open the right onboarding path for your stack.
Every card starts a tailored path. You can change the stack later in the dashboard.
How it works
From repo to live URL
Three steps. No server provisioning.
We build & publish
Framework detection, static output, and global delivery.
Share & scale
Preview URL immediately. Add your custom domain when you're ready.
Scope
What works on the platform
Supported
- HTML / CSS / JS and ZIP static sites
- React, Vue, Astro, Vite, Next static export
- Documentation sites and media bundles
- Web app frontends (static builds)
- WordPress static export
- Laravel frontend /
public/build output
Not supported here
- PHP runtime, MySQL, server sessions
- Dynamic WordPress admin
- Laravel backend, queues, cron
Run backends on your own stack. Ship the static frontend here.
Developers
API & automation
REST API v1, workspace API keys, and scopes for deploy and read.
Deploys today
…
Active projects
…
Uptime
…
Regions
…
FAQ
Common questions
What is IPFS?
IPFS is a way to store files on many nodes at once — like a resilient CDN, not a single server. Your site is addressed by content, so the same build always maps to the same version.
Do I need to run IPFS myself?
No. You upload a ZIP or connect Git — we build, pin, and serve over HTTPS. No nodes, keys, or CLI on your side.
What can I deploy?
Static sites: HTML, React/Vue builds, docs, WordPress or Laravel static exports. Not supported: PHP runtime, databases, or live SSR — keep APIs on your servers.
How is this different from a VPS?
No server to patch or scale. You ship files; we handle build, delivery, and rollbacks. Dynamic backends stay where you already run them.
Can I use my own domain?
Yes. After deploy, add the DNS records shown in the dashboard. Usually live in minutes; globally up to 48 hours.
How fast is the first deploy?
Most ZIP uploads get a preview URL in under two minutes. Git builds depend on your framework and install time.
Can I roll back a release?
Yes — pick a previous deployment in the dashboard and roll back without re-uploading the archive.
How is this different from Netlify or Vercel?
Same familiar flow: Git or ZIP, preview URLs, custom domains, rollback. Under the hood we store on IPFS for durable static hosting — you still never manage servers.
How do I get started?
Open guided onboarding, pick your project type, register a workspace, and deploy from ZIP or Git. You get a live preview URL before touching DNS — no credit card in the wizard.
Ship your first site today
Guided onboarding — preview URL before you touch DNS.