How to Choose Between Shared and VPS or Dedicated Hosting for an AI-Built Website or App

If you built a website or app with an AI coding assistant or builder, it may need more from a server than a typical website does. This article helps you decide whether your project fits Bluehost Shared Hosting or needs a VPS or Dedicated server. You will give a prompt to your AI assistant, it will inspect your project and answer a set of questions, and it will recommend a hosting type based on the Shared Hosting limits listed below.

Bluehost Shared Hosting Limits

Bluehost Shared Hosting is built for websites that run on PHP and MySQL and are managed through cPanel. Review the limits below before you run the prompt. Bluehost sets the PHP limits on Shared Hosting, and they cannot be increased.

Staying within the file count and database limits matters because exceeding them can slow your site and affect other accounts on the server. If an account stays over the limits, Bluehost may ask you to reduce usage, and in some cases the account may be suspended or terminated. For details, see Server Resource Limitations: Inode Count and Database Usage and Database Limits.

How to Check Your Project

Follow these steps to run the check.

1. Open the AI assistant or coding tool that has access to your project's files. It needs to be able to read your code, configuration files, and dependencies.
2. Copy the entire prompt from the next section and paste it into the assistant.
3. Review the answers. For each question, the assistant should answer Yes, No, or Unsure and name the file or package that supports its answer.
4. Read the recommendation at the end. Confirm every item marked Unsure before you choose a hosting plan.

The Prompt

Select Copy in the box below, or select everything in the box and copy it yourself, then paste it into your AI assistant.

Review this project's codebase, config files, and dependencies, then answer every question below with a specific answer (Yes / No / Unsure, plus evidence such as the file or package name). Do not guess. If you can't tell, say "Unsure" and say what would need to be checked. At the end, give a hosting recommendation using the rules provided.

SHARED HOSTING PLATFORM LIMITS (the PHP limits cannot be raised)
- Access: user-level only (no root/sudo), AlmaLinux 9, standard cPanel
- Backend: PHP 8.x is the primary backend. No Node.js, Ruby, or Go apps, and no persistent/long-running processes.
- Python: limited support. Python is preinstalled (it may not be the latest version) and scripts can run as CGI scripts (.py files with 755 permissions). Installing your own version of Python requires Bluehost Support to add the account to the Compiler group. Python apps that need a persistent server process (for example uvicorn or gunicorn) are not supported. Bluehost Support cannot help with custom Python configurations.
- Disabled PHP functions: exec and shell_exec are disabled
- Database: MySQL 8 only
- Database privileges: database users do not have SUPER privileges
- Database size and tables: up to 5,000 tables or 10 GB across all databases on the account, and up to 5,000 tables or 5 GB in any single database
- PHP max_execution_time: 60 seconds
- PHP max_input_time: 60 seconds
- PHP memory_limit: 512 MB
- PHP post_max_size and upload_max_filesize: 64 MB each
- Process limit: 25 concurrent processes per account (web requests, cron jobs, and scripts all count)
- Cron jobs: minimum interval of 15 minutes (nothing can run more often than once every 15 minutes)
- CPU limit: 25% of the server's CPU time for up to 90 seconds, in addition to the PHP and Apache limits. This applies to cron jobs and scripts too, so nothing can run for long.
- Network ports: Bluehost can open outbound ports on shared servers for connections to third-party services, but additional inbound ports are not opened. VPS and Dedicated servers can open whatever ports they need.
- File count: maximum of 200,000 inodes per account (each file and folder counts as one)
- Email users: shared accounts include 2 email users (mailboxes) on the server. Paid cPanel Email plans add more: cPanel Email Basic (3 to 10 mailboxes), cPanel Email Plus (11 to 20 mailboxes), and cPanel Email Premium (unlimited mailboxes). The plans are tied to the hosting plan, not to a single domain.
- Email sending: shared accounts start with a limit of 200 emails per hour per domain. cPanel Email Basic and Plus keep the 200 per hour limit. Only cPanel Email Premium raises it, to 1,000 emails per hour per domain. Reaching a mailbox or sending limit can block new mailboxes or outbound email until the plan is upgraded. For plan details and current pricing, see https://www.bluehost.com/help/article/bluehost-paid-cpanel-email-overview or visit bluehost.com.
- PCI DSS: Shared hosting is not PCI DSS compliant, but can do so if credit card data os handled by a compliant processor like Stripe. Any project where card data touches the server (stored, processed, or transmitted) requires VPS or Dedicated hosting, which can be made PCI compliant (see https://www.bluehost.com/help/article/pci-compliance). Payments handled entirely by a PCI compliant payment provider are fine, whether through a hosted checkout or redirect (Stripe Checkout, PayPal) or an embedded provider iframe or JavaScript element (Stripe Elements), because no card data reaches the server. Warning for embedded elements: they only keep card data off the server if the integration is built correctly.

A. LANGUAGE AND RUNTIME
1. What language(s) and framework(s) does the backend use (PHP, Node.js, Python, Ruby, Go, other)?
2. If PHP: what minimum PHP version does it require? Is it compatible with PHP 8.x?
3. If it isn't PHP: does it need a running server process (for example node server.js, Next.js/Nuxt server-side rendering, uvicorn, gunicorn, pm2)?
4. If the backend is Python: which Python version does it need, which third-party packages does it require, and can it run as plain scripts (for example CGI) without a persistent server process? Shared hosting has Python preinstalled, which may not be the latest version. Installing your own version requires Bluehost Support to add the account to the Compiler group.
5. Is it a static site or client-side-only app (React/Vue/Vite) that builds to plain HTML/JS/CSS files? If so, does it work when only the built output folder is uploaded?
6. Does it rely on serverless or edge functions (Vercel, Netlify, Cloudflare Workers, Supabase Edge Functions) for backend logic?

B. DATABASE AND STORAGE
7. Which database does it use (MySQL/MariaDB, PostgreSQL, MongoDB, SQLite, Supabase/Firebase or another external service, none)?
8. If MySQL: does it work on MySQL 8?
9. Does it need Redis, Memcached, Elasticsearch, a message queue, or any other service installed on the server?
10. Roughly how much disk space does it need now and in 12 months (code, database, uploads)?
11. Roughly how many files and folders will the project contain, including dependency folders such as node_modules or vendor, build output, caches, and uploads? Shared hosting allows a maximum of 200,000 per account.
12. Roughly how many database tables will it have, and how large will the database be, now and in 12 months? Could any single database exceed 5,000 tables or 5 GB, or could all databases combined exceed 5,000 tables or 10 GB? Does the project store images or other files as blobs in the database?
13. Does it need database privileges beyond a standard database user, such as the SUPER privilege (for example changing global MySQL server settings)? Database users on shared hosting do not have SUPER privileges.

C. SERVER ACCESS AND SYSTEM REQUIREMENTS
14. Does any setup step require root or sudo (installing system packages, editing system config, firewall rules)?
15. Does it require Docker or containers?
16. Does it need non-standard PHP extensions, command-line tools (ffmpeg, ImageMagick, Puppeteer/headless Chrome), or compiled binaries?
17. Does it need WebSockets or other persistent connections, or additional inbound ports?
18. Which third-party services does it connect to, and on which ports? Does any service need to connect in to the server on a port other than the standard web ports? Bluehost can open outbound ports on shared servers, but additional inbound ports are not opened. VPS and Dedicated servers can open whatever ports they need.
19. Does it need custom web server configuration beyond .htaccess (nginx rules, extra Apache modules, reverse proxy)?

D. BACKGROUND WORK AND SCHEDULING
20. Does it use background workers or queues that must run continuously (Laravel queue workers, Celery, Sidekiq, BullMQ)?
21. Does it use scheduled tasks? List each one, how often it must run, and roughly how long it runs. Does any task need to run more often than every 15 minutes? (Note: frameworks like Laravel expect a cron entry that runs every minute for their scheduler. That will not work on shared hosting.)
22. Does it do heavy processing (video, large image batches, big imports/exports, scraping, AI/ML inference)?
23. Does it spawn child processes, run parallel jobs, or shell out to other programs? Does any PHP code call exec or shell_exec, which are disabled on shared hosting? How many processes run at once?

E. CHECKS AGAINST THE SHARED LIMITS
24. Can any single request, cron job, or script take longer than 60 seconds, or use heavy CPU for more than a short time (long imports, report generation, calls to slow AI APIs, large file processing)? Remember that cron jobs and scripts are also subject to the 25% CPU / 90 second limit.
25. Are uploads or form submissions ever larger than 64 MB in total?
26. Could any single request need more than 512 MB of memory (large image processing, big data sets, big spreadsheets)?
27. What is the expected number of monthly visitors and peak concurrent users? (Each active request uses a process, so a large number of simultaneous users, long-running requests, or concurrent cron/background tasks can reach the 25-process limit.)
28. Is guaranteed performance or uptime critical (e-commerce, bookings, a business-critical app)?

F. SECURITY AND COMPLIANCE
29. Does the project accept card payments?
   - Which provider or gateway does it use (Stripe, PayPal, Square, Authorize.net, a WooCommerce payment plugin, a custom integration)?
   - Where do customers type their card details: (a) on a page hosted by the provider after a redirect, (b) in a provider iframe or JavaScript element embedded in the project's own page, or (c) in a form on the project's own server that sends the card data to our backend or the provider?
   - If the answer is (b), does any code on the project's server read, log, or receive the card fields (for example custom card input fields, or form posts that include card data)?
   - Does the code, database, or logs ever contain card numbers or CVVs?
30. Does it handle other regulated or sensitive data (health records, government IDs)?
31. Does it need an isolated environment or dedicated IP?

G. EMAIL
32. Does the app send email (transactional, newsletters)? Roughly how many per day or month, and what is the most it could send in any one hour from a single domain? Shared accounts start with a limit of 200 emails per hour per domain, which can be increased to 1,000 per hour per domain only with the cPanel Email Premium plan.
33. How many email users (mailboxes) does it need on the server, for example mailboxes on your domain? Shared accounts include 2. Paid cPanel Email plans add mailboxes: cPanel Email Basic allows 3 to 10, cPanel Email Plus allows 11 to 20, and cPanel Email Premium allows unlimited.

DECISION RULES
- Shared hosting fits only if ALL of these are true: it's static, PHP 8.x with MySQL 8, or Python that runs as plain scripts without a persistent process; everything runs inside normal web requests; it needs no root access, extra services, or persistent processes; it needs no additional inbound ports (outbound connections to third-party services are fine); it does not need the SUPER database privilege or the PHP exec or shell_exec functions; every scheduled task can run at an interval of 15 minutes or longer; no request needs more than 60 seconds, 512 MB of memory, or 64 MB of upload/POST data; no cron job or script needs to run for long or use heavy CPU beyond the 25% CPU / 90 second limit; it stays within 200,000 files and folders and within the database size and table limits; it would not send more than 1,000 emails per hour from a single domain; traffic and concurrency are low to moderate and unlikely to approach 25 simultaneous processes; and it does not handle cardholder data or other regulated data. Payments through a PCI compliant payment provider's hosted checkout or redirect (answer a) or its embedded iframe or JavaScript element (answer b) do not count as handling cardholder data, as long as the server never sees the card fields.
- VPS or Dedicated is needed if ANY of these is true: it needs Node.js, Ruby, or Go on the server; it needs a Python application server or any Python process that must stay running (for example uvicorn or gunicorn); it needs a persistent process, queue worker, WebSockets, or additional inbound ports; it needs root, Docker, Redis, PostgreSQL, or any other service; it needs the SUPER database privilege or the PHP exec or shell_exec functions; it needs custom server configuration; any scheduled task must run more often than every 15 minutes; any workload can exceed the 60 s / 512 MB / 64 MB limits or the 25% CPU / 90 second limit; it could exceed 200,000 files and folders or the database size and table limits; it could send more than 1,000 emails per hour from a single domain; it could regularly exceed 25 concurrent processes; it needs guaranteed resources; card data passes through or is stored on the server (answer c, card numbers or CVVs appearing in code, database, or logs, or custom card fields in an embedded integration that post to the server); or it handles other regulated data.
- Recommend Dedicated over VPS if traffic is high, the workload is resource-intensive, or the client needs full hardware isolation.
- Operating system note: Unlike shared hosting, VPS and Dedicated servers do not require AlmaLinux 9 with cPanel. Other images are available, including Ubuntu 22.04 and 24.04, Debian 12 and 13, Rocky Linux 8 and 9, and AlmaLinux 9. If the project depends on a particular operating system or distribution, check it against this list.
- A static front end that uses an external backend service (Supabase, Firebase, a third-party API) can run on shared hosting, since only the built files are hosted.
- Email: Shared accounts include 2 email users and start with a limit of 200 emails per hour per domain. Paid cPanel Email plans add mailboxes: cPanel Email Basic (3 to 10), cPanel Email Plus (11 to 20), and cPanel Email Premium (unlimited). Only cPanel Email Premium raises the sending limit, to 1,000 emails per hour per domain. If the project needs more than 2 email users or more than 200 emails per hour from a domain, do not decide on this alone. List the cPanel Email plan it would need as an item to confirm before purchase in the final output (Basic, Plus, or Premium for mailboxes, and Premium for more than 200 emails per hour), and say that bluehost.com has current pricing and plans. If it needs more than 1,000 emails per hour from a single domain, VPS or Dedicated is needed.
- Python note: If the recommendation is Shared and the project needs a Python version other than the one preinstalled, you must include this note in the final output: "This project needs a custom Python version. Installing it requires Bluehost Support to add your account to the Compiler group. Bluehost Support cannot help with custom Python configurations."
- Embedded iframe warning (answer b): If the project uses an embedded provider iframe or JavaScript element, the recommendation may still be Shared, but you must include this warning in the final output: "This project uses an embedded payment element. It only keeps card data off the server if it is implemented exactly as the provider documents. Confirm that no custom card input fields exist, that card data is never sent to or logged by the project's own backend, and that the provider's official library is loaded directly from the provider. If any of these is not true, VPS or Dedicated is required."

Finish with: (1) your recommendation (Shared, VPS, or Dedicated), (2) the specific answers that drove it, (3) any "Unsure" items to confirm before purchase, including any email needs above the starting email limits (more than 2 email users or more than 200 emails per hour per domain), and (4) anything that would need to change in the project to make it fit on shared hosting, including a list of any scheduled tasks that would need to be rescheduled to an interval of 15 minutes or longer, or shortened to fit the CPU limit, any code that relies on exec, shell_exec, or the SUPER database privilege, any Python version or package requirements that depend on Compiler group access, and any clean-up needed to stay within the file count and database limits.

Understanding Your Results

Use the assistant's recommendation and the answers behind it to choose a hosting type.

If the Recommendation Is Shared Hosting

Shared Hosting is likely a good fit when the assistant reports a static site, a PHP 8.x site with a MySQL 8 database, or a Python project that runs as plain scripts, as long as it runs entirely within normal web requests and stays inside the limits listed above. A static front end that uses an external backend service, such as Supabase, Firebase, or a third-party API, can also run on Shared Hosting, because only the built files are hosted.

Your project may still fit if the assistant lists changes to make, such as rescheduling scheduled tasks to an interval of 15 minutes or longer, shortening tasks that run for too long, replacing code that relies on exec or shell_exec, or cleaning up files and database tables to stay within the limits.

Shared accounts include 2 email users and start with a limit of 200 emails per hour per domain. Paid cPanel Email plans add mailboxes, and cPanel Email Premium raises the sending limit to 1,000 emails per hour per domain. Plans are based primarily on mailbox usage. cPanel email runs on the same server as your website, so heavy email use can take resources your website needs. If your project needs more than the starting limits, confirm your email needs before you choose a plan. For plan details, see Bluehost: Paid cPanel Email Overview. For current pricing and plans, visit bluehost.com.

If your Python project needs a version other than the one that is preinstalled, contact Bluehost Support and ask to be added to the Compiler group before you install it. Bluehost Support cannot help with custom Python configurations. For installation steps, see How to Install Python on a Hosting Server.

If the Recommendation Is VPS or Dedicated Hosting

A VPS or Dedicated server is likely needed when any of the following applies:

• The backend uses Node.js, Ruby, or Go.
• The backend uses Python and needs an application server, or any process that must keep running, such as uvicorn or gunicorn.
• The project needs a persistent process, a queue worker, WebSockets, or additional inbound ports.
• The project needs root access, Docker, Redis, PostgreSQL, or any other service installed on the server.
• The project needs the SUPER database privilege, or needs to call the PHP exec or shell_exec functions.
• The project needs custom server configuration.
• A scheduled task must run more often than every 15 minutes.
• Any request can exceed 60 seconds, 512 MB of memory, or 64 MB of upload data.
• A cron job or script needs to run for long or use heavy CPU, beyond the 25% CPU limit.
• The project could exceed 200,000 files and folders, or the database limits of 5,000 tables or 10 GB across all databases, or 5,000 tables or 5 GB in a single database.
• The project could send more than 1,000 emails per hour from a single domain.
• The project could regularly exceed 25 concurrent processes.
• The project needs guaranteed resources or an isolated environment.
• The project handles sensitive or regulated data.

A Dedicated server is usually chosen over a VPS when traffic is high, the workload is resource-intensive, or you need full hardware isolation. For current options, see VPS Hosting and Dedicated Hosting on bluehost.com.

If Your Project Accepts Card Payments

How card details reach your project decides which hosting type fits.

• Hosted checkout or redirect: Customers pay on a PCI compliant payment provider's own page, such as Stripe Checkout or PayPal. No card data reaches your server, so Shared Hosting can still fit.
• Embedded payment element: Customers enter card details in a PCI compliant payment provider's iframe or JavaScript form on your page, such as Stripe Elements. Shared Hosting can still fit when the integration is built exactly as the provider documents.
• Card data on your server: Your own form or backend receives, logs, or stores card numbers or CVVs. This requires a VPS or Dedicated server, which can be made PCI compliant.

Choosing a VPS or Dedicated server does not by itself make a project PCI DSS compliant. Compliance also depends on how you configure the server and build the application. For more on PCI compliance, see How to Achieve PCI Compliance with Bluehost Hosting.

Frequently Asked Questions

Can my AI assistant migrate my site or app to Bluehost?

Yes. Many AI coding assistants can handle a migration, as long as they have the proper credentials, such as an SSH key or login for both your current host and your Bluehost server. Results depend on the tool and your project, so back up your site and data first. For the general steps, see How to Switch to VPS Hosting on Bluehost.

Bluehost also offers a paid migration service, described in Migration Services: Website and Email Migration. It generally covers websites, not apps, and it may run into issues if your project needs any work or retooling to run on the new server, because Bluehost does not provide development support. Bluehost Support and migration services do not troubleshoot or deploy apps. For current pricing and plans, visit bluehost.com.

Will Bluehost Support deploy or troubleshoot my app?

No. Bluehost Support and migration services do not deploy or troubleshoot apps, and Bluehost does not provide development support. Many AI coding assistants can deploy your project once you give them an SSH key or login. For steps, see What is SSH Access and How to Enable It in Your Hosting Account.

Can I move from Shared Hosting to a VPS later?

Yes. The general steps are to purchase a VPS plan, transfer your website files and database, update your domain’s DNS settings, wait up to 48 hours for DNS to propagate, and cancel your old plan after you confirm everything works. For details, see How to Switch to VPS Hosting on Bluehost. For migration help and its limits, see the migration question above.

Can I use Shared Hosting if my app relies on a service like Supabase or Firebase?

Often, yes. A static front end that uses an external backend service, such as Supabase, Firebase, or a third-party API, can run on Shared Hosting, because only the built files are hosted. Bluehost can open outbound ports on Shared Hosting so your project can connect to third-party services, but additional inbound ports are not opened. If your project also needs a server process, root access, other services running on the server, or additional inbound ports, you need a VPS or Dedicated server, which can open whatever ports they need. The prompt in this article checks for this.

Can I choose a different operating system on a VPS or Dedicated server?

Yes. VPS and Dedicated servers do not require AlmaLinux 9 with cPanel. You can choose from other operating system images, including Ubuntu 22.04 and 24.04, Debian 12 and 13, Rocky Linux 8 and 9, and AlmaLinux 9.

Can my AI assistant buy and set up a VPS for me?

In some cases, yes. Bluehost’s MCP server lets an MCP-compatible AI assistant purchase a Self-Managed VPS for you. It is available to US customers paying in USD, and you add or change payment methods in your browser. For setup steps, see How to Set Up Bluehost MCP Server to Your AI Assistant.

Can I run Node.js, Docker, or other services on Bluehost?

Not on Shared Hosting, which gives you user-level access only and does not support Node.js apps or persistent processes. VPS and Dedicated servers include root SSH access, so you can install the runtimes and services your project needs. For what Bluehost Support covers on a VPS, see Bluehost VPS Hosting Scope of Support.

Other Resources

These Bluehost pages can help once you have chosen a hosting type. For current pricing and plans, visit bluehost.com.

Choosing and Moving to VPS or Dedicated Hosting

• VPS & Dedicated Hosting: Getting Started Guide — a consolidated list of articles for accessing, securing, backing up, and managing a VPS or Dedicated server.
• Bluehost VPS Hosting: Features, Self-Managed vs. Managed — differences in responsibilities, technical expectations, security, and maintenance.
• Bluehost VPS Hosting Scope of Support — details on the Self-Managed and Fully-Managed support levels.
• What to Expect with Bluehost Self-Managed VPS — what changes when you step up from shared hosting to a Self-Managed VPS.
• How to Switch to VPS Hosting on Bluehost — migration steps and upgrade options for moving to a VPS.
• Migration Services: Website and Email Migration — paid migration service for websites and email.

Setting Up and Securing Your Server

• What is SSH Access and How to Enable It in Your Hosting Account — enable SSH on Shared, VPS, and Dedicated servers.
• How to Connect to a Self-Managed VPS or VDS Using an SSH Key — connect over SSH with the matching private key.
• Bluehost Self-Managed VPS: How to Secure Your Server After Setup — basic security steps to take right after you deploy a new server.
• How to Set Up a VPS: Step-by-Step Guide for Beginners — Bluehost blog.
• How to Set Up and Optimize a Node.js VPS for Scaling Startups? — Bluehost blog.

Automating With AI Assistants

• Bluehost's MCP server (https://mcp.bluehost.com/mcp) — connect it to an MCP-compatible AI assistant to look up account details and purchase a Self-Managed VPS. Available to US customers paying in USD.
• How to Set Up Bluehost MCP Server to Your AI Assistant
• Overview: The Model Context Protocol (MCP) and MCP Servers
• Bluehost's MCP Server FAQ
• SSH Key Setup and App Deployment on a Self-Managed VPS via MCP — how SSH access is set up before your server is provisioned and what to expect as your assistant deploys your application.
• Agent Hosting — an always-on environment for custom automation workflows and AI applications.

Hosting Product Pages

• Web Hosting
• VPS Hosting (Self-Managed)
• Managed VPS Hosting
• Virtual Dedicated Server
• Dedicated Hosting