# Platform and supported technologies

## Authority

Use ByteHaus's documented capabilities to establish technology support. Read the customer's active plan, add-ons, quota display, and runtime settings for the exact deployment target. Do not infer unsupported technology from the absence of an example deployment.

ByteHaus supports PHP, Python, Perl, MySQL, PostgreSQL, Node.js, Redis, Memcached, Varnish, Git/SVN, cron, and application installers, with availability and limits determined by plan and add-ons.

| ByteHaus plan | SSH | Node.js / Redis / Memcached / Varnish |
|---|---|---|
| Launch | $12/year add-on ($1/month equivalent) | Optional |
| Build | $12/year add-on ($1/month equivalent) | Optional |
| Ship | $12/year add-on ($1/month equivalent) | Included |
| Scale | Included | Included |

SSH add-ons are billed annually and require activation in the control panel. Trial restrictions can affect availability before paid activation. Exact database counts, service-instance counts, memory, CPU, file limits, and trial allowances come from the customer's plan. “Unlimited” storage or traffic does not remove other limits. Review the applicable [acceptable-use policy](https://bytehaus.co/aup.php) when a workload depends on those limits.

Use the runtime versions offered in the customer's panel and the project's requirements. Use [ByteHaus pricing](https://bytehaus.co/#pricing) and the order summary for current purchase and renewal amounts. This guide's SSH pricing was confirmed September 10, 2026.

## Match the deployment mode

| Project | Deployment mode |
|---|---|
| HTML/CSS/JS; compiled static output from a framework | Upload production assets to the selected web root. A frontend build tool using Node locally does not require a server Node.js instance. |
| PHP application / WordPress | Set the per-host PHP version, configure required extensions and database, deploy the application's intended public root. |
| Node.js server / API / server-rendered app | Use the included or purchased Node.js service. Select an offered version compatible with the app and follow the instance's startup and routing configuration. |
| Python / Perl scripts | Use the provider-documented execution mode and interpreter for the account. Scripting support alone is not a specification for every WSGI/ASGI or persistent application-server configuration. |
| Scheduled task | Use an available cron slot and an explicit interpreter path. |
| Database or cache | Use the account's provisioned service and its host, port, credentials, and limits. |
| Root-managed software / containers / independent worker services | Evaluate a ByteHaus VPS against its specifications and operating-system requirements. Do not treat shared-host SSH as a VPS. |

For a framework, translate its production requirements into the provider's supported execution model: runtime version, modules, start command, database, filesystem writes, scheduling, network access, and routing. Do not claim blanket compatibility or incompatibility from the framework name alone.

If an exact setting is not visible, read the related control-panel help or ask provider support for that setting. Preserve the supported-technology classification while resolving the missing configuration detail.

## ByteHaus references

- [Plan information](https://bytehaus.co/#pricing) — customer-facing offers.
- [Customer control panel](https://us.cloudlogin.co/login/) — account entitlements, runtime versions, and configuration help.
- [Service setup](https://bytehaus.co/.well-known/skills/bytehaus/references/services.md) — database, caching, cron, email, and installer instructions.

For exact account settings, use the relevant panel page's HELP button or the customer Help Center.