Devployer
Dashboard

Deployments

Nixpacks

Nixpacks builds your app from a Git repository without a Dockerfile. Devployer detects the stack and configures runtime (JDK, PHP, Node, etc.) for supported frameworks.

Use this when you want the simplest GitHub deploy. Prefer Dockerfile when you already have a Dockerfile and need full image control.

For deploy from Cursor, Dockerfile is the recommended default — see Deploy with MCP.

Before you start

  • A Devployer account and a project with an environment
  • A public or private GitHub repository
  • Optional: Cursor MCP for deploy-from-chat — see MCP

1. Create the app in Devployer

  1. Open your project and environment
  2. Add resource → Public GitHub or Private GitHub
  3. Select your framework (Laravel, Spring Boot, Quarkus, Angular, …)
  4. Under Build pack, choose Nixpacks
  5. Set the runtime version if shown (Java / PHP / Node)
  6. Pick a plan and complete payment when asked
  7. Finish creation (you can leave instant deploy off to deploy later from MCP)

2. Framework guides

3. Deploy from Cursor (MCP)

MCP only deploys with Dockerfile — you cannot choose Nixpacks from chat.

  1. Connect MCP — MCP guide
  2. Ensure a root Dockerfile (the agent creates one for the stack if missing)
  3. Ask to deploy — see Deploy with MCP

To stay on Nixpacks, deploy from the Devployer portal (not MCP).

Tips

  • No Dockerfile is required for the standard portal path
  • If you deploy from MCP, the app is treated as Dockerfile (/Dockerfile)
  • After deploy, open the public URL from the app page in Devployer

Quick checklist

  • App created with Nixpacks in Devployer
  • Plan/payment completed if required
  • Deploy from the portal (Nixpacks) or MCP (Dockerfile + root Dockerfile)
  • Public URL loads when the build finishes