Apps - Hyze Cloud

An app is the main unit you publish on Hyze Cloud: an API, worker, dashboard, bot, or background service running in a managed container.

What an app includes

Every app carries:

Runtime configuration (node, bun, or python)
Environment variables
Logs and build history
Backups
Filesystem access

{
  "name": "api",
  "runtime": "node",
  "memoryMB": 512,
  "exposePort": 3000
}

startupCommand is optional. Omit it (or set "auto") and Hyze detects how to start the app — Vite, Next, Node, static sites, and Python are recognized automatically. Pass a custom command only when you need to override detection.

How an app runs

Every request to a published app goes through the Hyze proxy before reaching your container. The proxy resolves the subdomain, applies rate limits, and forwards traffic to the exposed port.

Client → Hyze proxy → your container

Two practical consequences:

Your app must listen on 0.0.0.0, not localhost
The port configured in exposePort must match the port your server listens on

Limits

Configurable memory per app (memoryMB)
Public proxy rate limits: 80 req/s per IP and 400 req/s per host — see Rate limits

Next steps

Deploy an app

Publish from ZIP or GitHub.

Apps reference

Endpoints for lifecycle, logs, env, and backups.

Last modified on September 1, 2026

​What an app includes

​How an app runs

​Limits

​Next steps