Keep WordPress.
Delete WordPress hosting.
Edit in a private WordPress in the cloud. Publish as static HTML. No PHP, no database, no attack surface on your live site.
Free during public beta (30 days notice). No card required.
Single-operator. Sign-ups limited at first to keep things smooth.
WordPress is the editor.
Static HTML is the product.
The best parts of WordPress.
None of the ops.
Static means static.
Your published site is pure HTML. No PHP, no database, no server-side processing. That’s why it’s fast and secure. But anything that needs a server won’t work on a static site. Not sure if this is a good fit for what you’re building? Read who Stelae is for.
- Pages, posts, custom post types
- Themes and visual design
- Images, fonts, CSS, JS
- Navigation and internal links
- SEO metadata and sitemaps
- Contact forms → use Formspree, Basin
- Site search → use Pagefind
- Comments → use Giscus, Cactus, Disqus
- WooCommerce / e-commerce → use Snipcart, LemonSqueezy
- Any server-side plugin logic
For your site, your client's site, or your mom's site.
Free during public beta. No card required.
Frequently asked.
What happens when the beta ends?
The free public beta runs at least until 27 July 2026. When it ends, sites convert to the paid plan (€19.90/year). Free sites won’t be grandfathered — at this price, the economics don’t allow it. You’ll get at least 30 days’ notice before the conversion, with a clear opt-out: download your archive and your WordPress backup, cancel your account, no charges. The static site you’ve already deployed keeps running on its host.
What happens if Stelae shuts down?
Your published static site keeps running. It’s hosted on your own account, not on Stelae’s servers. If Stelae ever shuts down, all your data (static exports, WordPress content, database) will remain available for download for at least 90 days. You can also download a full WordPress backup at any time from your dashboard to migrate away whenever you want.
Do I need my own hosting account?
Not necessarily. You can always download your static site as an archive and host it however you like. Or don’t host it at all. If you want auto-deploy, we support statichost.eu (free tier, EU-hosted), Cloudflare Workers, and any git-based host. We handle the deployment; you just provide the account.
What support do I get for €19.90/year?
Platform support is end-to-end: export, deploy, container lifecycle, and billing. If anything breaks there, I’ll fix it. I’m actively working to make static export handle as many real-world WordPress setups as possible. If your site has something that doesn’t survive export cleanly, please email support@stelae.eu. Most of those turn out to be fixable, and your case helps make the platform better for everyone. The docs are a good first stop for general questions.
Can I use any WordPress theme or plugin?
Any theme works. Most plugins work in the editor. Features that need server-side processing at runtime (contact forms, WooCommerce, site search) don’t carry over to the static output, but there are static-friendly alternatives for most of them. The compatibility guide covers what works and what to swap in.
Can I use a custom domain?
Yes, but that’s configured on your hosting provider, not in Stelae. Statichost.eu, Cloudflare Workers, GitHub Pages, and most other hosts support custom domains. Stelae builds and deploys your site. Where it lives and what domain it uses is between you and your host.
How do I migrate away from Stelae?
Download your static site archive and your WordPress backup from the dashboard. Cancel your subscription. Your published static site keeps running on your hosting provider. It has no dependency on us. If you want to continue editing in WordPress, import the backup into any standard WordPress installation.
Is there an uptime SLA?
There’s no formal SLA, because the live site doesn’t depend on Stelae once it’s deployed. Your hosting provider handles uptime for the published site. The WordPress editor uses Stelae’s server, but it sleeps most of the time and only wakes when you’re actively editing. Platform updates are rare, take seconds, and only affect users editing at that moment.
Where is my data?
Everything runs in Germany. Hosting, payments (Mollie, NL), email (Scaleway, FR). All EU companies. No data leaves the European Economic Area. Your WordPress content lives in an isolated container. Your static site lives on whichever host you choose.
Can I use Stelae from outside the EU?
Absolutely. Anyone can sign up, regardless of location. Payments work with all major international cards via Mollie. The WordPress editor runs on EU infrastructure, so you may notice slightly higher latency while editing compared to a local install, but it’s just an editor, not a production site. Your exported static files deploy wherever you choose, with no EU constraint on the output. The EU positioning is about where Stelae’s infrastructure runs, not about who can use it.
Is Stelae environmentally sustainable?
Your published site is plain HTML served by your hosting provider, so visitors trigger no server-side processing on Stelae’s side. Stelae’s editor instances sleep when idle and only wake during active editing, so the platform’s servers stay cold most of the time. Stelae’s own infrastructure does not currently run on 100% renewable energy. The energy advantage is the low absolute consumption from the static-output architecture and sleep-on-idle scheduling, rather than the energy source itself.