Supported frameworks

How detection works

Project files and repository structure inform the detected framework and build settings. Review the result against the commands that work in your repository. Framework-specific handling exists for Next.js, Nuxt, Astro, SvelteKit and Laravel.

Choose a build method

• Use the standard automatic build path when its detected configuration fits your app.
• Use a repository Dockerfile when you need explicit system dependencies or control over the image build.
• Use Compose only for an application structure supported by the Compose setup flow. Review the services and primary application before deploying.

Monorepos and runtime settings

• Set the root directory to the application you are deploying.
• Keep package manifests and lockfiles consistent.
• Use a production start command, the configured container port, and a health-check path that your app can answer.

If a build fails

Read the build log before changing settings. Check missing dependencies, runtime versions, root directory and required build variables. A Dockerfile build from a repository is different from deploying a prebuilt registry image.

• Quickstart
• Environments
• Limits & FAQ