Your docs are static.Hosting should be cheaper.
Mintfree takes a Mintlify repo, builds it, and gives you a live docs URL. Webhooks and custom domains are there when you need them, not before.
Why Mintfree
If the docs are already static, the hosting should stay boring
That is the whole pitch. Connect GitHub, build the site, publish it, and avoid turning docs hosting into a bigger product decision than it needs to be.
Keep the repo you already use. Mintfree handles the hosting part.
Get a Mintlify site online without buying into another docs platform.
Start with a hosted URL, then add webhooks and a custom domain when you need them.
Before
Paying for more platform than the job calls for
After
Repo in, docs site out
Short path to launch
Connect the repo, deploy it, and share the URL without rebuilding your whole docs setup.
Lower overhead
Pay for the part you actually need: getting a static docs site online and keeping it there.
Extras when you want them
Turn on auto-deploys and add your domain later, once the basic setup is working.
Features
The small set of features most docs teams actually need
Mintfree is narrow on purpose. It handles the repo-to-URL part and leaves the rest alone.
GitHub
Use the repo you already ship docs from
Choose the Mintlify repo, kick off a deployment, and keep GitHub as the source of truth.
Publishing
Get a live docs site without the ceremony
The flow stays simple: clone the repo, build the static site, publish the result.
Webhooks
Turn on redeploys when pushes should go live
Leave auto-deploy off while you are testing, then enable it when your docs should update on every push.
Domains
Launch first, point your domain when it is ready
Start on a Mintfree URL, handle DNS on your timeline, then move to `docs.yourcompany.com`.
Workflow
Three steps. Nothing weird.
You should be able to explain the deployment flow in one breath. This one holds up pretty well.
Connect GitHub
Authorize GitHub once so Mintfree can see your repos and start deployments.
Choose a Mintlify repo
Pick the repository with `docs.json` and the docs content you want to publish.
Deploy and share
Mintfree builds the site, gives you a hosted URL, and keeps follow-up deploys straightforward.
Deployment Status
docs-acme.mintfree.app
Repository connected
GitHub access works
Mintlify files detected
`docs.json` found
Static build running
Installing packages and generating files
Global publish
Push the finished docs site to the edge
Auto-Deploy
Optional webhook
Turn it on when pushes should redeploy the docs automatically.
Domain
Bring your hostname
Start on Mintfree, then point `docs.yourcompany.com` when DNS is ready.
Lower hosting bill
Useful if your docs are already static and you do not want to pay for extra platform on top.
Simple path to launch
Connect the repo, run the build, get the URL, move on with your day.
Global delivery
Serve the finished docs site from a fast edge network without stitching together extra services.
One place to check status
See deploy state, logs, domain setup, and webhook status without digging around.
Start now
If your Mintlify docs already work, stop overpaying to host them
Mintfree handles the boring part: take the repo, build the site, and keep a live URL online for the team.