Hosted access
Jant is built for self-hosting first. Hosted access exists for the smaller set of cases where you already know Jant is the right system, but running it yourself is the wrong tradeoff.
What this is
Hosted access is deliberately small.
It is not:
- broad self-serve hosting
- public signup
- a free tier
- a hosted trial funnel
If self-hosting works for you, that is still the recommended path.
Good fit
Hosted access usually makes sense when:
- you want Jant specifically, not a generic blog host
- you do not want to manage runtime, storage, backups, upgrades, and billing yourself
- you are comfortable with a manual email-based review instead of instant checkout
What hosted access includes
Hosted Jant covers the operational layer around your site:
- the hosted Jant runtime
- managed storage and operational backups
- upgrades, account management, and billing
- custom domains, exports, and the normal Jant publishing surface
You still own your content. If you ever want to leave, export remains available.
Pricing
| Item | Price |
|---|---|
| First hosted blog | $10.46/year |
| Each additional hosted blog | +$5/year |
| Shared media storage included | 10 GB across the account |
| Shared storage upgrade | 50 GB total for +$25/year |
Additional blogs join the same billing account. If you add one partway through a paid year, Stripe may prorate it onto the current renewal cycle.
How access works
The path is simple:
- Email [email protected].
- Explain what you want to run, why self-hosting is the wrong fit, and what kind of help you actually need.
- If it looks like a fit, you will get invite access and can create the account and blog from there.
This stays manual on purpose. The goal is to help the small set of people who need hosted Jant, not to turn Jant into a general hosting product.
If self-hosting is workable
If you can run Jant yourself, the public docs remain the better starting point: Introduction to Jant, Getting Started, Deploy on Cloudflare, Deploy with Docker, and Configuration.