Advanced Web Application Tools on GreatHosts

1. Start with what your plan already includes

The same GreatHosts CP can expose different entitlements depending on the selected hosting plan. Do not assume that seeing a menu item means the service is free on every plan. The product table is the first place to check what is included.

• Included features require no separate add-on order.
• Plan limits and included services can differ between hosting tiers.
• If a capability is not included, use Add/Upgrade Services to add it to the shared plan before considering a VPS.

2. NodeJS instances

The live GreatHosts CP exposes a NodeJS area and an Order NodeJS Instances workflow. This confirms that NodeJS can be part of the managed hosting environment without requiring a VPS solely for the runtime.

• The CP can show that no NodeJS instance exists yet and offer an order path.
• Quantity can be selected when ordering available instances.
• Exact price and current availability are deliberately not hard-coded in this guide.

3. Redis and Memcached

Redis and Memcached are exposed in GreatHosts CP as application services. They can be useful for caching, sessions or application-specific workloads when the software supports them.

• Confirm whether the selected plan already includes the service.
• If not included, use the available add-on workflow rather than assuming VPS is necessary.
• Application configuration still has to point to the service details supplied after activation.

4. Varnish and Supervisor

Varnish and Supervisor are also visible in the current GreatHosts CP. Varnish is an application-side caching option; Supervisor is intended for managed background-process control where the service is available.

• Do not enable Varnish merely because it exists; confirm that the application is compatible with the caching model.
• Use Supervisor only for workloads supported by the managed environment.
• If a required daemon or system service cannot be represented by the managed tools, that becomes a stronger KVM signal.

5. PHP, Python, SSH and cron

The same Web Tools area exposes PHP Settings, Python Settings, SSH/Shell Access and Cron Jobs. These controls cover many normal development and scheduled-task needs without operating an entire server.

• Use PHP Settings for supported PHP configuration rather than editing server-wide settings.
• Use Python Settings for the managed Python environment.
• SSH availability and limits remain plan-dependent.
• Cron is appropriate for scheduled work; do not use it as a substitute for a permanently running service.

6. The managed-hosting boundary

The add-on model extends the life of shared hosting, but it does not turn shared hosting into a root server. KVM is still the correct step when the project needs unrestricted packages, kernel/system configuration, persistent services outside the managed controls, stronger isolation or sustained resource ownership.

• Add capability first when that solves the requirement cleanly.
• Upgrade plan when resource headroom—not server control—is the problem.
• Move to KVM when control or isolation becomes the actual requirement.

7. Order and verify before changing architecture

For any plan-dependent capability, verify the current product table and the account Add/Upgrade Services screen. The CP calculates the current amount due for the remaining account term before confirmation.

• Do not rely on an old screenshot for current pricing.
• Record the service details after activation.
• Test the application end to end before removing the previous configuration.

Services related to this guide