Web terminal

Web terminal

Every service has a built-in terminal in the dashboard: a shell opened directly inside the running container, with no SSH or configuration.

Opening the terminal

In the service panel, Terminal tab. The session opens inside the active container, in the same environment as your application: same files, same environment variables, same binaries.

Typical use cases

# Inspect the files actually deployed
ls -la /app

# Check an environment variable
echo $DATABASE_URL

# Run a one-off migration
npx prisma migrate deploy

# Open a database client
psql $DATABASE_URL

What you need to know

• The shell lives inside the container. A redeploy or a service restart closes the session, and any manual file change is lost (the redeployed image starts fresh from the build state).
• Don't edit code live: this is the classic anti-pattern. Fix it in the repository and redeploy. The terminal is for diagnosing, not patching.
• Depending on the image, the available shell may be bash or sh (Alpine images).

Alternatives depending on your need