A self-hosted AI website builder runs its editing software on hosting you control. In VoxelSite, the AI creates PHP, HTML, CSS, and JavaScript files there. You choose the hosting and the AI provider; the published website can keep running without the Studio.
Where AI generation runs
VoxelSite’s Studio runs on your PHP server. Generation requests go to the AI provider you connect: Claude, OpenAI, Gemini, DeepSeek, or an OpenAI-compatible service. You supply an API key and pay the provider for usage. The optional AI Router sends bounded routing requests to TypeSafe with a separate key.
Your website files stay on your hosting. VoxelSite sends prompts and the site context needed for generation to that AI service. Review that provider’s data handling before sending client or confidential information. See the AI engine documentation for the generation workflow.
Hosting requirements
Start with PHP 8.2 or newer, PDO SQLite, and the extensions listed in the requirements. SQLite stores Studio state in local files; you do not need a separate MySQL server. VoxelSite compiles Tailwind CSS with PHP, so installation does not require Node.js, npm, or a frontend build step.
Shared hosting is the primary target. A VPS also works, but brings more server administration. Confirm that your host allows writable site directories, outbound HTTPS requests to your AI provider, and the required PHP extensions. For Nginx, use the documented rewrite configuration. Apache uses .htaccess rules.
- Check the server requirements before choosing a plan.
- Follow the installation guide to upload the files and create the owner account.
- Connect an AI provider, create a small site, preview it, and publish when it is ready.
Running costs
VoxelSite is free software released under AGPL-3.0. There is no recurring VoxelSite platform subscription. A domain, hosting, AI generation, and any email service you use remain separate costs. Visitors load generated pages without making AI requests.
Budget for backups, updates, and someone who can restore the installation.
Backups and maintenance
You or your hosting provider handle the server. Back up the website files and the Studio’s data. Test restoration and apply updates. Client handovers should name the owner of the domain, hosting account, AI key, and maintenance responsibility.
The Studio’s snapshots help undo editing changes. Keep a separate backup off the server for recovery. Read the update guide before replacing an installation.
Choosing a managed builder
A managed builder handles the editor, hosting, and platform maintenance through one service. Choose it if that saves work you cannot take on. For a complex store or application, check the required features first.
Start with the website builder comparisons, or try the Studio demo before setting up a server.