Managing Backend Processes & Logs
Understand how to start, stop, or restart processes and read server console logs.
Your applications are isolated within secure sandboxes on our cluster node architecture. You have full process control over starting, stopping, restarting, and inspecting logs directly from the control panel in the console dashboard.
Node Action Commands
Each application details page has a top action control bar containing the following commands:
Spins up the application process and binds it to the designated port. Once active, the ingress gateway starts routing public domain requests to your application container instantly.
Gracefully terminates the app instance. The process is taken offline, releasing port bindings. Visitors will receive a 503 screen. Stopped apps consume 0 billing credits.
Performs a quick stop-and-start cycle. This is the fastest way to clear runtime memory leaks, force cache updates, or apply newly saved .env environmental variables.
Reading Application Logs
Our process monitor splits application output logs into two distinct streams to help you debug errors faster:
Stores successful connections, HTTP routing transactions, and manual console.log() statements.
Stores runtime exceptions, script crash trace stacks, unhandled promise rejections, and server load warnings.