You built a site with AI. It looks good in the preview. Now you want it on your own domain, available when your laptop is closed. Do you need a VPS, or is web hosting enough?
The answer depends on what your project needs to run, not on whether an AI wrote the code. At SharpHeberg, the choice is between web hosting with Plesk and a Linux VPS with root access. Start with the app, then choose the offer.
Before ordering, check one thing: does your project produce static website files, or does part of it need a running server? A React interface, a Next.js app and a Docker project can have different hosting requirements, even when they look similar in a browser.
Three projects, three starting points
| What you built | Where to start at SharpHeberg |
|---|---|
| A landing page, portfolio or site exported as HTML, CSS and JavaScript | Check web hosting and its domain, file-serving and routing configuration. |
| Several compatible sites or small frontend projects | Compare Web Pro and Web Business before renting separate servers. |
| An app needing a backend runtime, workers or Docker | Check the web platform's runtime limits; choose Linux VPS when you need system-level control. |
Illustrative starting points, not workload-capacity guarantees. Check compatibility and plan allowances before ordering.
1. “My AI-built site exports to static files”
Suppose you have built a portfolio or landing page and the production build gives you HTML, CSS, JavaScript and images. The host serves those files; it does not need to run your development server just to display the site.
A client-rendered React project built with Vite can work this way: Vite's static deployment guide describes publishing its build output, normally the dist directory. Some Next.js projects can also use a static export, but features that require a server cannot simply be included in that export.
SharpHeberg web hosting is an option to examine first. It provides a Plesk account and SSL certificates. For one compatible exported site, Web Basic offers one website, 5 GB of NVMe storage and one MySQL database. A static site does not necessarily need that database.
Check the exported files, domain configuration and routing requirements before deployment. A page working at the homepage does not prove its nested URLs work when opened directly.
Also check what is outside the frontend. A contact form, login or dashboard may depend on an API or database hosted elsewhere. Uploading the frontend does not automatically recreate those services, and private credentials must not be placed in browser-delivered JavaScript.
Compare SharpHeberg web-hosting offers.
2. “I keep building new projects”
You have a portfolio, a landing page for a side project and a small site for a client. That is three projects, not automatically three VPS subscriptions.
If all three fit the web platform, Web Pro is worth checking: three websites, 20 GB of NVMe storage and three MySQL databases. Verify that each project fits the platform and that their combined needs fit the account.
Web Business lists unlimited website and MySQL database counts, with 50 GB of NVMe storage. Unlimited site slots do not mean unlimited computing power or storage. Choose it for the allowances you need, not because every AI-generated project is guaranteed to fit.
If several projects need a custom server environment, they may instead share one VPS when its resources and configuration permit. Separate servers can still be appropriate for isolation or operational reasons. The useful question is what the projects need, not how many repositories you have.
Compare Web Pro and Web Business before taking on server administration you do not need.
3. “My app needs a backend or services that keep running”
A site with server-rendered pages, API routes, background jobs or a custom database setup is a different hosting job from a folder of static files. Identify the processes that must run and the services they depend on.
A backend does not automatically mean a VPS. SharpHeberg's web-hosting offer also lists Node.js support. Check the required runtime version, start command, build process and background-process needs against that platform before ruling it out.
If the deployment requires Docker Compose, system packages or control over server-level services, SharpHeberg Linux VPS is the relevant offer to examine. The plans provide root access, and the VPS page confirms KVM virtualization and Docker support.
VPS Linux Start is listed with 8 GB RAM, 2 vCores and 20 GB NVMe storage. Assess all three against your app. Container images, databases, logs and uploads consume disk space; processes and traffic determine CPU and memory needs. This configuration is a candidate, not a capacity guarantee for an arbitrary app.
Compare the Linux VPS configurations.
The AI built the app. Who will run the server?
Root access gives you freedom to shape the environment. It also means arranging operating-system updates, access security, deployment, monitoring and recovery. A coding assistant can help with those tasks, but buying a VPS does not automatically deploy or maintain your app.
Check the support scope if you want someone to administer your custom stack. With web hosting, you work within the platform's tools and limits; with a VPS, you take control of more of the environment.
Choose the hosting from the project you actually have
- A compatible static export? Start with SharpHeberg web hosting.
- Several compatible projects? Check Web Pro or Web Business and their total allowances.
- Docker or system-level control? Compare SharpHeberg Linux VPS plans and size the server around the app.
Not sure what your AI generated? Find the build command, output directory, start command if needed, and external services it depends on. Share those requirements with SharpHeberg support—not your passwords or secret values—and we can help identify the relevant offer.
Plan specifications checked on 29 October 2026 against the linked offer pages. Project examples are illustrative, not deployment or workload-capacity tests. Check current prices and the selected billing period before ordering.