Miget supports two primary build strategies so you can choose the workflow that best suits each application.

​
Paketo Buildpacks

Paketo Buildpacks automatically turn your source code into production-ready container images.
  • Language detection: Buildpacks inspect your repository to determine which language runtimes and dependencies to install.
  • Layered caching: Subsequent builds reuse cached layers to keep deployments fast.
  • Security focus: Each build produces a detailed bill of materials and receives timely patches for OS and runtime vulnerabilities.
  • Extensibility: Buildpacks are modular. Use the default Paketo Jammy Full builder or supply custom buildpacks to cover any special requirements.
Prefer buildpacks when you want automatic builds with minimal maintenance.

​
Docker Engine

Docker Engine is available when you provide a Dockerfile in your repository.
  • Full control: Define the base image, environment, and commands required to run your application.
  • Compatibility: Works with any language, framework, or toolchain.
  • Consistency: The resulting image runs the same way across development, CI, and production.
  • Ecosystem ready: Integrates with registries, orchestrators, and CI/CD pipelines that understand Docker images.
If Miget detects both a Dockerfile and a buildpack configuration, the Dockerfile takes precedence. You can switch builders in the app settings.