Deployment Logs

Every Nept deployment emits two streams of logs:

• Build logs — output from the build command (next build, vite build, docker build, etc.).
• Runtime logs — stdout and stderr from your running app or container.

View logs in the dashboard

Open a project, then click Logs. You can filter by:

• Deployment
• Log stream (build vs. runtime)
• Time range
• Free-text search

Tail logs from the CLI

nept logs --follow

Add --deployment <id> to target a specific deployment, or --type build / --type runtime to filter streams.

Debugging failed builds

If a build fails, the last lines of the build log usually contain the reason:

• Missing dependencies → check package.json.
• Wrong Node version → set engines.node in package.json.
• Missing environment variables → add them via Environment Variables.

Debugging crashes

If your app crashes at startup, the runtime log will contain the stack trace. Common causes:

• Bad database URL — see Databases.
• Port not exposed — check that your app listens on the port Nept expects (usually the PORT env variable).

Retention

Logs are retained for a configurable window. Older logs can be exported via the API.

Next steps

• Environment Variables
• Custom Domains
• Deploy Docker