Shared Hosting, Managed Platforms, and VPS
Shared hosting is suited to supported, relatively standard workloads such as many PHP websites. Managed platforms reduce server administration for modern applications. A VPS provides greater control but makes the owner responsible for configuration, security, deployment, monitoring, and recovery.
What You Will Be Able to Decide
- Compare shared hosting, managed platforms, VPS hosting, and dedicated resources.
- Explain why runtime support matters when choosing hosting.
- Identify the operational work hidden behind a self-managed VPS.
- Ask a consultant who owns deployment, security, monitoring, backups, and recovery.
A product has been built. It now needs a place to run.
The hosting recommendation may include terms such as shared hosting, managed platform, VPS, Node.js VPS, PHP hosting, dedicated server, container, reverse proxy, or process manager.
These are not merely pricing categories.
Each choice changes how much control the team receives and how much operational responsibility it accepts.
For a personal application, start with the time you can give the service each month. A small private tool may be well served by a managed platform; a VPS only makes sense when the control is worth the updates, monitoring, backups, and recovery work you will own.
Put the Tested App Online One Step at a Time
For the request-tracker practice app, use a managed platform that supports the project's actual output. A static browser app can often be deployed as built files; an app with server functions needs compatible server hosting. Ask the agent to identify which you have before choosing a provider. Shared PHP hosting is not automatically suitable for a Node.js application.
Use the provider's temporary HTTPS address first. A domain is your chosen website name; DNS directs that name to the host; HTTPS protects the connection. You can add a custom domain after the temporary address works. Keep the domain and hosting accounts under your control.
- Save the tested source version and ask for the exact build command, output folder, runtime needs, and deployment instructions for this project.
- Create or select your own hosting project. Review current pricing, usage limits, and billing controls before confirming it.
- Connect the repository or upload the build output using the provider's supported method. Check that the uploaded folder is the build output, not an arbitrary source folder.
- Supply the required configuration through the host's settings. Keep secrets out of browser-delivered variables. Use separate test and production values.
- Deploy to the temporary URL, read the build/deployment log, and open it in a separate browser session.
- Repeat add/edit/delete/export, reload, phone-width and any account-boundary checks. Verify that the real service data source is the intended one.
- If a custom domain is needed, follow the host's exact DNS instructions, verify HTTPS, and retest routes directly and after reload.
Use the Log to Fix Deployment Errors
A build failure means the host could not prepare the app; a runtime failure happens after it starts. Copy the relevant error message after removing secrets and ask the agent to compare the local and hosting environments. Common differences include runtime versions, missing configuration, a wrong output folder, or a service that accepts requests from the preview address but not the public one.
If the home page loads but a nested URL fails on refresh, ask whether the project uses browser routing, server routes, or generated files and which host configuration fits it. Do not fix a broken API or permission check by opening access to everyone. Diagnose the actual failed step.
The preview works but deployment fails. Inspect this sanitized log and the project's deployment configuration. Explain whether this is a build, runtime, routing, or external-service issue. Propose the smallest change, describe its risk, and rerun the relevant checks. Keep the working release available for rollback.Prepare Recovery Before Inviting Users
Rollback means returning to a previous working release. Use the host's release history or redeploy the saved source version, and check that you can identify the version being served. A database change may prevent old code from working; ask for a compatible migration and recovery plan before altering production data.
Source history is not a database backup. For shared data, schedule backups, specify the maximum tolerable data loss, restore a backup into a separate environment, and confirm the records are usable. For the browser-only demo, export records and disclose that clearing storage or switching website address/browser can remove access to them.
Name who checks error logs, renews the domain, updates dependencies, responds to a failed integration, and reviews spending. Enable suitable cost notifications or caps where the provider supports them, and check what they actually enforce. Test the contact route and record how to disable a malfunctioning app. A VPS adds system patching, access management and recovery work; choose it when somebody has accepted that responsibility.
Keep a One-page Operating Note
- Public URL, project owner, support/contact route, and intended users.
- Repository and deployed version; exact start, check, build and deployment instructions.
- Data location, access rules, backup/restore evidence and deletion procedure.
- Configuration names and where to set them, with secret values excluded.
- Monthly fixed costs, usage-based services, alert settings and shutdown procedure.
- Last tested date, known limitations, rollback steps and the next small improvement.
When Is Static Hosting Enough?
Static hosting delivers pre-built files without requiring a long-running application process for each page request.
It can fit informational websites and frontend outputs that do not need server-side application logic at request time. A static interface may still communicate with APIs or managed services for dynamic product data.
The important question is whether the product can be prepared ahead of time or requires application logic to run when a user makes a request.
When Is a Managed Platform the Sensible Default?
A managed application platform allows a team to deploy an application without managing most of the underlying server.
The platform may handle:
- builds
- deployment
- SSL
- scaling
- logs
- environment variables
- rollbacks
- preview environments
This is similar to hiring a managed venue rather than renting an empty building.
The team still brings the product. The venue handles much of the infrastructure required to operate it.
Managed platforms are often useful when:
- launch speed matters
- the team is small
- traffic is moderate or uncertain
- the platform supports the application runtime
- reduced operational work is worth the platform cost
Technical term
VPS
VPS means virtual private server. A VPS is an isolated virtual machine with allocated computing resources. The customer usually receives greater control over the operating system, runtime, networking, and installed software.
Think of a VPS as renting an unfurnished commercial unit. The tenant has more freedom. The tenant must also arrange and maintain more of what makes the space usable.
What Work Does a VPS Leave with You?
A VPS may require the team to configure:
- the operating system
- firewall rules
- user access
- Node.js or PHP
- a process manager
- a reverse proxy
- SSL certificates
- deployments
- backups
- monitoring
- security updates
Technical term
A reverse proxy receives incoming web requests and forwards them to the correct application process.
It acts like a receptionist directing visitors to the correct office.
Technical term
A process manager keeps an application process running and can restart it after a crash or server reboot.
When Should a Node.js App Run on a VPS?
A Node.js application may run as a long-lived process on a VPS.
A typical setup may include:
User request
→ DNS
→ Web server or reverse proxy
→ Node.js application process
→ Database or external serviceThe VPS provides control, but the application does not become reliable merely because it starts successfully.
The team still needs:
- a repeatable deployment process
- environment variable management
- logs
- restart behaviour
- backups
- access control
- security updates
- rollback instructions
When Does PHP Hosting Reduce Deployment Work?
Many shared hosting products are designed around PHP applications.
A PHP application matching the provider’s supported environment can often be deployed with less server work.
A PHP application can also run on a VPS when the team needs more control.
The decision is therefore not “PHP means shared hosting” or “Node.js means VPS.”
The real question is whether the application fits the provider’s supported environment and whether the team wants to accept server responsibility.
When Would a Dedicated Server Be Justified?
A dedicated server gives one customer control of a physical machine.
A VPS is virtualised. Several virtual servers may run on the same physical hardware while remaining isolated from one another.
Most early-stage products do not need a dedicated physical server. A dedicated server may become relevant when there are specific performance, isolation, compliance, or hardware requirements.
Which Hosting Choice Matches Your Operating Capacity?
What Should You Check Before Choosing a Hosting Plan?
Hostinger provides commercial hosting and VPS options that may be relevant to standard websites, PHP applications, and self-managed server deployments.
The correct plan depends on the runtime, database, expected traffic, deployment method, and the team’s ability to manage infrastructure.
Avoid selecting a plan only because its advertised server resources appear large. First confirm:
- whether the application runtime is supported
- whether long-running processes are allowed
- whether root access is required
- whether backups are included or separately configured
- who will manage security updates
- how deployments will be performed
- how the application will be restored after failure
Disclosure: This lesson contains an affiliate link. Brownsmith Dynamics may receive a commission if you purchase through it, at no additional cost to you.
View Current Hostinger PlansWhat Should You Ask a Consultant?
- Why does this application require this hosting model?
- Which infrastructure tasks remain our responsibility?
- How will deployments work?
- How will we reverse a failed deployment?
- Where are backups stored?
- Who installs security updates?
- How will we know when the application is failing?
- Can another developer reproduce the server setup?
Key takeaway
Key Takeaway
Hosting cost includes more than the provider’s monthly invoice. It also includes the human work required to deploy, secure, monitor, and recover the product.
Continue the Beginner Path
Use the same fictional request-tracker project through planning, building, testing and deployment. Each stage gives you an artifact to carry into the next.
Reuse the Guide with Your AI Assistant
The bd-guide-skillsfolder turns this path into a reusable skill. Open its SKILL.md, follow your assistant's skill-loading instructions, and ask it to guide your own small app through the four stages. Read the scope and permissions before use.
A Relevant Companion Skill
Website SEO guardrails — Check public routes, canonicals, indexing and migration behavior before promoting the app.