Skip to main content
These tools are available only for supported runtime apps and are intentionally constrained.

​
Restart

Restart is currently supported for runtime apps where the platform can safely restart the managed service. For Python apps, restart requires:
  • the latest deployment status is success
  • the runtime has been provisioned correctly
Node.js / Express.js and Next.js SSR runtime flows also participate in managed runtime restart behavior when the platform has provisioned a healthy runtime service.

​
Runtime logs

Current runtime-log behavior:
  • runtime app logs are currently available only for Python apps
  • logs must be enabled in app settings first
  • logs can be tailed and cleared from the customer flow
If runtime logs are disabled, the API rejects the request instead of silently returning an empty log.

​
Terminal access

Current terminal behavior:
  • terminal is currently available only for Python apps
  • terminal requires a successful deployment first
  • commands can be executed directly or through the terminal websocket
Current API constraints:
  • command is required
  • timeout is limited
  • working directory is constrained by the runtime context
Terminal access is an operational convenience, not a substitute for deployment configuration. If your change should persist across rebuilds, save it in source or in app settings instead.

​
Gunicorn tuning

For Flask and Django apps that run with Gunicorn, current settings support:
  • gunicorn_workers
  • gunicorn_worker_class_enabled
  • gunicorn_worker_class
Plan-aware worker limits are enforced at the API layer, so invalid forged values are rejected.

​
Common reasons these tools are unavailable

  • the app is not Python
  • no successful deployment exists yet
  • runtime logs are disabled
  • the app is paused due to overdue billing