Finding the best Instatic hosting is less about price than about three specific things a provider either handles or leaves to you: two persistent volumes, one encryption key, and HTTPS on a port that should never face the internet.
Instatic itself is genuinely light. The committed minimum is 512 MB RAM, one CPU core, and 2 GB of disk, because published pages are baked to static files rather than rendered per request.
That lightness means almost any platform is a candidate for best Instatic hosting. It also means almost any platform can run it badly, by putting your database on ephemeral storage or regenerating the secret key on every deploy.
So this guide ranks six routes on what they actually persist, not on headline specs. Verified September 2026.
Table of Contents
Quick Summary: Best Instatic Hosting by Goal
| If you want to… | Use this | From | Setup time |
|---|---|---|---|
| Everything configured on your domain | xCloud | $24.99/mo | Minutes |
| Deploy from a template and iterate | Railway | Usage-based | Minutes |
| A managed pod without a VPS | InstaPods | Flat monthly | Minutes |
| One control plane across many apps | Coolify | Free, Cloud $5/mo | An hour |
| The lowest possible bill | Hetzner Cloud | €5.49/mo | An evening |
| A familiar cloud with deep docs | DigitalOcean | $24/mo | An evening |
Best Instatic hosting for studios and freelancers: xCloud, because both volumes, the secret key, the reverse proxy, and HTTPS are configured before you log in, with unlimited sites per server.
Best for a quick evaluation: Railway, which has official templates for both the SQLite and Postgres editions.
Cheapest if you already run servers: Hetzner plus your own Docker setup, where a 2 GB box costs €5.49 a month.
What the Best Instatic Hosting Must Get Right
Everything that separates the best Instatic hosting from a cheap deployment traces back to these three.
| Requirement | What it is | If a host gets it wrong |
|---|---|---|
| Persistent data volume | SQLite database, configuration, users, pages, auth state | The whole site vanishes on the next container recreate |
| Persistent uploads volume | Every image, video and font | Pages render with broken media |
A stable INSTATIC_SECRET_KEY | Encrypts stored secrets | Saved credentials and TOTP MFA seeds become unreadable |
The third one is the quiet killer. If a platform regenerates the key on each deploy, nothing errors. Your pages load fine. Then someone with two-factor enabled cannot log in, and nobody connects that to last Tuesday’s deploy.
There is a fourth item that is about security rather than data. The production server listens on port 3001, and that port should be bound to localhost with a reverse proxy terminating HTTPS in front of it. A host that exposes 3001 directly has handed you a problem.
Our Instatic backup guide covers protecting all three components yourself regardless of which route you pick.
Instatic Hosting Server Requirements
| Tier | RAM | CPU | Disk | Suits |
|---|---|---|---|---|
| Committed minimum | 512 MB | 1 core | 2 GB | One small site, no media |
| Realistic | 4 to 6 GB | 2 to 4 cores | 50 to 100 GB | Personal sites, studio projects |
| Media heavy | 16 GB | 6 cores | 200 GB | Many uploads, concurrent editors |
That minimum comes from the deployment template’s committed floor, and it is low because of the architecture: one Bun process, SQLite, static output, and almost no work at request time.
What actually pushes you higher is uploads and concurrent editors, not traffic. A site with a thousand visitors a day and a hundred photos needs more disk than CPU. If you have not deployed yet, our hosting guide walks the whole setup, and the Instatic explainer covers what the software is.
How We Ranked Each Instatic Hosting Route
Each candidate for best Instatic hosting was scored on six criteria, weighted toward what breaks.
- Does it persist both volumes? Not one, both.
- Is the secret key stable across deploys? The single most-missed requirement.
- Is HTTPS handled and port 3001 kept private? Security and function together.
- What does it really cost per month? Including storage, not just compute.
- How long from signup to a claimed owner account?
- Who handles updates? This is pre-1.0 software with migrations on start.
Master Comparison Table
Ranked on persistence and key handling first, price second, because the best Instatic hosting is the kind that still has your site next month.
| Rank | Route | Type | From | Both volumes | Stable key | Setup |
|---|---|---|---|---|---|---|
| 🥇 1 | xCloud | Managed | $24.99/mo | ✅ Yes | ✅ Yes | Minutes |
| 🥈 2 | Railway | PaaS template | Usage-based | ✅ Yes | ✅ Generated | Minutes |
| 🥉 3 | InstaPods | Managed pod | Flat monthly | ✅ Yes | ✅ Yes | Minutes |
| 4 | Coolify | Self-hosted PaaS | Free, Cloud $5/mo | ⚠️ You configure | ⚠️ You set it | An hour |
| 5 | Hetzner Cloud | Raw VPS | €5.49/mo | ❌ You configure | ❌ You set it | An evening |
| 6 | DigitalOcean | Raw VPS | $24/mo | ❌ You configure | ❌ You set it | An evening |
The 6 Best Instatic Hosting Routes {#routes}
🥇 1. xCloud, Best Managed Instatic Hosting Overall
xCloud deploys Instatic 0.0.18 pinned by digest, which matters more than it sounds for pre-1.0 software: your install does not silently jump versions because someone pushed a new latest tag.
It generates a stable INSTATIC_SECRET_KEY that persists across restarts and recreations, and mounts both named volumes: instatic_data for the SQLite database, configuration, users, pages, and auth state, and instatic_uploads for media.
Key features
- Both persistent volumes configured, so everything survives restarts
- A stable encryption key rather than one regenerated per deploy
- Port 3001 bound to localhost, with only the nginx reverse proxy publicly exposed
- HTTPS and a free SSL certificate on your own domain from the first request
- Server backups and snapshots plus automatic security updates
- Unlimited sites on every tier, across 30-plus server locations
Pricing
| Plan | Price | Specs |
|---|---|---|
| Cloud VPS 6 GB | $24.99/month | 6 GB RAM, 4 vCPU, 100 GB NVMe SSD, 30 TB bandwidth |
| Cloud VPS 16 GB | $59.99/month | 16 GB RAM, 6 vCPU, 200 GB NVMe SSD, 30 TB bandwidth |
| Cloud VPS 24 GB | $84.99/month | 24 GB RAM, 8 vCPU, 300 GB NVMe SSD, 30 TB bandwidth |
Already own a server? Bring your own starts free for one server and 10 sites, then $5 per server per month from two to five, dropping to $3 at eleven or more.
You still complete first-owner setup yourself at /admin, which is the correct design: no provider should hold your admin password. Do it immediately after deployment, because an unclaimed owner account can be taken by anyone who reaches the page.
Best for: Freelancers and studios who want the three hard requirements handled and unlimited sites on one server, which is what best Instatic hosting means at scale.
Note: xCloud has no official partnership with the Instatic project. This is a deployment and management option for the open source software, and Instatic updates remain yours to plan.
🥈 2. Railway, Best Template for a Quick Start
Railway is the best Instatic hosting route for a fast trial, with official templates for both database options, which is unusual and genuinely useful.
The SQLite template runs the official Docker image with a Railway volume mounted at /app/storage covering the database, media uploads, fonts, plugin packages, and published artifacts. Public HTTPS networking and automated health checks are included, and INSTATIC_SECRET_KEY is generated automatically so encrypted credentials and TOTP secrets work without a manual setup script.
The Postgres template provisions three components instead: the Instatic web service on corebunch/instatic:latest, a managed postgres-ssl:18 instance for content, users, sessions, and settings, and the same /app/storage volume. It runs database migrations on boot and configures trusted proxy headers for secure admin access.
Railway does not publish a fixed price for either template; cost follows its usage-based model across compute and storage.
Best for: Developers evaluating Instatic, or teams wanting the Postgres edition with managed database backups.
Worth knowing: The Postgres template pins latest, which is worth changing to a specific tag before you put real work on it.
🥉 3. InstaPods, Best Managed Pod Without a VPS
InstaPods offers Instatic as a managed pod with a flat monthly fee and a deployment measured in seconds rather than minutes.
The appeal is the shape of it: no VPS to secure, no compose file, no proxy configuration, and a predictable invoice rather than usage metering. For a single personal site that is often exactly the right amount of infrastructure.
Check the current price and resource allocation on their site before committing, since pod platforms adjust tiers regularly.
Best for: Individuals running one site who want a fixed monthly cost and nothing to administer.
4. Coolify, Best Control Plane for Several Apps
Coolify is not a host. It is an open source, self-hostable PaaS that sits on servers you already rent and gives them a deployment interface.
Self-hosting Coolify is free forever under Apache 2.0. Coolify Cloud is $5 a month for two connected servers, plus $3 a month per additional server, dropping to about $4 a month on annual billing. Cloud manages Coolify itself, not your applications, so you still supply the VPS.
The important caveat for Instatic specifically: Coolify gives you the interface, and you are still responsible for defining both persistent volumes and setting a stable secret key. Nothing does that for you.
Best for: Developers running several self-hosted apps who want one control plane rather than one Instatic install.
5. Hetzner Cloud, Cheapest Raw VPS
Hetzner has earned its reputation, and after the 15 June 2026 price adjustment it is still the cheapest credible European option.
| Plan | RAM | Price (excl. VAT) |
|---|---|---|
| CX23 | 2 GB | €5.49/month |
| CX33 | 4 GB | €8.49/month |
| CX43 | 8 GB | €15.99/month |
The CX23 at €5.49 comfortably clears Instatic’s 512 MB minimum, and CX33 is a sensible starting point once media is involved.
You get a server and nothing else. Docker, both volumes, the secret key, the reverse proxy, certificates, and backups are all yours. Run through our VPS security checklist before the server holds anything real.
Best for: Experienced operators in Europe optimizing for the lowest infrastructure bill.
6. DigitalOcean, Best DIY Cloud for Documentation
DigitalOcean costs more than Hetzner and returns some of it in documentation quality and a control panel most developers already know.
| Basic Droplet | Specs | Price |
|---|---|---|
| 4 GB / 2 vCPU | 80 GiB SSD, 4,000 GiB transfer | $24/month |
| 8 GB / 4 vCPU | 160 GiB SSD, 5,000 GiB transfer | $48/month |
The 4 GB Droplet at $24 is a comfortable home for a real Instatic site. Note it is roughly three times Hetzner’s CX33 for similar RAM, which is the ecosystem premium you are choosing to pay.
Best for: Teams already standardized on DigitalOcean who value familiarity over unit cost.
Best Instatic Hosting Cost in Practice
The headline number is never the whole bill, and the best Instatic hosting on paper is rarely the cheapest row. Here is what each route actually costs.
| Cost line | One personal site | Studio, several sites | Media-heavy portfolio |
|---|---|---|---|
| Compute | $6 to $25 | $25 to $60 | $60 to $85 |
| Storage growth | Minimal | $2 to $10 | $10 to $30 |
| Domain and TLS | About $1, TLS free | Same | Same |
| AI provider usage | Your own keys | Your own keys | Your own keys |
| Backups | Often included | Often included | Often included |
| Your time | 1 to 3 hours a month | 2 to 4 hours a month | 2 to 4 hours a month |
The compensating factor for managed routes is that Instatic has no per-site licence, so one server can hold every project you run. That is what changes the arithmetic for a studio, and it is the same trade covered in our Instatic vs Webflow comparison.
For the broader hosting decision, this comparison of shared, VPS, and cloud hosting and the managed versus self-managed question cover the fundamentals.
5 Instatic Hosting Mistakes That Cost People Their Site {#mistakes}
Mistake 1: One volume instead of two. Persisting the database but not uploads gives you a complete site full of broken images. Both, always.
Mistake 2: Letting the platform regenerate the secret key. Nothing errors. Then TOTP two-factor login stops working for everyone and nobody knows why. Set the key explicitly and store it off the server.
Mistake 3: Exposing port 3001 publicly. Bind it to localhost and put a reverse proxy in front. The application expects to sit behind one.
Mistake 4: Delaying first-owner setup. After deployment there is no admin password, and anyone who reaches the setup screen can claim the owner account. Complete it within minutes of the site going live.
Mistake 5: Tracking latest on pre-1.0 software. Migrations run on start. Pin a version, back up both volumes and the key before upgrading, test the new image somewhere disposable, and keep a rollback ready.
Pick a Route and Deploy This Week
The best Instatic hosting for you comes down to one question: do you want to own the volumes, the key, and the proxy configuration yourself.
If yes, Hetzner plus your own Docker setup is the cheapest credible route and it costs you an evening. If no, a managed route removes all three hard requirements and the recurring hour that comes with them.
Either way, three things stay yours regardless of provider. Claim the owner account immediately, keep an off-server backup of both volumes plus the secret key, and test a restore before you need one.
So pick the row in the summary table that matches your situation and deploy it this week. Then build something with the Instatic tutorial, and if you are still comparing tools, the wider open source website builder roundup puts Instatic in context.
Ready to skip the volumes, key, and proxy setup? Deploy Instatic on xCloud in one click.
If you have found this blog helpful, feel free to subscribe to our blogs for valuable tutorials, guides, knowledge, and tips on web hosting and server management. You can also join our Facebook community to share insights and engage in discussions.
Frequently Asked Questions
What is the best Instatic hosting provider?
For studios and freelancers, xCloud, because both persistent volumes, a stable encryption key, HTTPS, and a localhost-bound port 3001 are configured before you log in, with unlimited sites from $24.99 a month. For a quick evaluation, Railway’s official templates are the fastest route.
Is managed Instatic hosting worth it over a raw VPS?
It depends whether you want to own the volumes, the secret key, and the proxy config. A VPS is cheaper on paper; managed removes the three requirements that cause the worst failures. One lost secret key usually costs more than a year of the difference.
What are Instatic’s server requirements?
The committed minimum is 512 MB RAM, one CPU core, and 2 GB of disk, which is low because published pages are static files. A realistic starting point for a working site is 4 to 6 GB of RAM and 50 GB or more of disk once media uploads begin.
What makes one Instatic hosting route better than another?
Three things, in this order: both volumes persisted, a stable secret key across deploys, and port 3001 kept private behind HTTPS. A route that gets all three right is better than a cheaper one that does not, regardless of specs.
How much does Instatic hosting cost?
Between roughly €5.49 and $85 a month depending on route. A raw VPS starts at €5.49 with Hetzner or $24 with DigitalOcean, managed platforms run $24.99 to $84.99, and PaaS options bill by usage. The software itself is free under MIT.
Can I host Instatic on Railway?
Yes. Railway publishes official templates for both the SQLite and Postgres editions. Both mount a persistent volume at /app/storage and generate INSTATIC_SECRET_KEY automatically, with the Postgres template also provisioning a managed database and running migrations on boot.
Can I run Instatic on shared hosting?
No. Instatic runs a persistent Bun process and needs writable volumes for its database and uploads, neither of which shared hosting provides. A VPS or a container platform is the realistic floor.
Which port does Instatic use, and should it be public?
Port 3001 in production, and it should not be publicly reachable. Bind it to localhost and terminate HTTPS on a reverse proxy in front, which is how managed deployments configure it by default.
Do Instatic hosting providers back up my site automatically?
Server-level snapshots may run at the infrastructure layer, but that is not the same as an application-aware backup you have tested. Keep your own off-server copy of both volumes and the secret key, and run a restore drill yourself.
Does my host update Instatic for me?
Generally no, and that is appropriate for pre-1.0 software where migrations run on start. Pinned images stay pinned until you act. Back up both volumes and the key, read the release notes, test the new image, and keep a rollback plan before upgrading.
