Package versions can differ between image releases and existing deployments. For the complete installed package list and exact versions in your deployment, inspect your environment.
PHP
The PHP-FPM and Octane images include PHP, Composer, Node.js, npm, and Yarn Classic. PHP-FPM uses Nginx. Octane uses FrankenPHP with Caddy instead. Both PHP images include ImageMagick 7, compiled from source, with themagick command and compatibility commands such as convert and identify. They also include Ghostscript and Poppler utilities for document processing.
Shared PHP packages
The following packages are explicitly installed in both PHP images:
The HEIF library and its codec plugins come from Debian’s Bookworm backports repository. PHP-FPM also explicitly installs
nginx and gettext-base.
The images install additional runtime libraries required by their compiled PHP extensions. Development packages used only to compile PHP extensions or ImageMagick in the image builder are not part of this list. See PHP extensions for extension availability.
Shared packages for other runtimes
The Node.js, Bun, Deno, Go, Python, Ruby, and Rust images explicitly install the following packages. Each runtime’s section lists its additional packages and bundled tools.
These images include Node.js, npm, and Yarn for frontend asset builds, even when your application’s primary language is not JavaScript. In the Go, Python, Ruby, and Rust images, changing the language version does not change the bundled Node.js version.
Node.js
The Node.js image includes Node.js, npm, Yarn, and pnpm, in addition to the shared packages.
The Python packages support native Node.js dependency builds through
node-gyp.
Bun
The Bun image includes Bun, Node.js, npm, Yarn, and Deno. It also bundles thevercel, create-hono, and create-elysia command-line tools.
In addition to the shared packages, the image explicitly installs make, g++, and autoconf. Cloud does not install Python in this image, so dependencies that build native modules with node-gyp may fail.
Deno
The Deno image includes Deno, Node.js, npm, Yarn, and Bun. It also bundles thevercel, create-hono, and create-elysia command-line tools.
In addition to the shared packages, the image explicitly installs make, g++, and autoconf. Cloud does not install Python in this image, so dependencies that build native modules with node-gyp may fail.
Go
The Go image includes the Go toolchain, Node.js, npm, and Yarn Classic, in addition to the shared packages.
The image inherits additional build tools from the upstream Go image. Cloud does not add Python to this image, so dependencies that build native modules with
node-gyp may fail.
Python
The Python image includes Python, pip, Node.js, npm, and Yarn Classic, in addition to the shared packages.
Cloud installs uv, Poetry with its export plugin, or Pipenv during your application build when the corresponding dependency files require them. These tools are not preinstalled in the base image.
Ruby
The Ruby image includes Ruby, RubyGems, Bundler, Node.js, npm, Yarn Classic, Bun, Deno, and Corepack. Corepack’s package manager shims are not enabled by default. The image also bundles the Spinel Ruby compiler and itsspin command.
The following packages are installed in addition to the shared packages:
The Ruby image includes libvips for Rails image variants. Its dependencies include ImageMagick and Poppler shared libraries, but not their command-line tools. The image does not include FFmpeg, Chromium, or wkhtmltopdf by default. Adding a gem does not install those system tools. See the Rails image-processing guidance for Active Storage configuration.
Rust
The Rust image includesrustc, Cargo, rustup, Clippy, rustfmt, Node.js, npm, and Yarn Classic, in addition to the shared packages.
Clang and libclang are not included by default. Crates that require them need an alternative that works with the installed toolchain. See the Rust deploy guide for build configuration.
Static sites
Static site generators use their language’s image during the build. The final image starts from the Node.js base image and serves the generated files with Nginx. It includes the Node.js image’s packages, but does not start a Node.js application server. Only the generated web root carries over from the build stage. Language tools, application dependencies, and add-ons from the build stage do not carry over to the serving image. Plain HTML sites use the Node.js serving image without a language build step.Optional add-ons
FFmpeg, Chromium, and wkhtmltopdf are not default tools in the images described here. An add-on can provide software that your base image does not include. Available add-ons appear under General Settings > Build configuration > Add-ons. Cloud filters this list by your environment’s language and organization. Saving an add-on selection requires a redeployment to install it in your application’s image. Your build commands run without root privileges, so they cannot install system packages withapt-get. If a required tool is missing and no suitable add-on is available, use an alternative dependency or perform that processing in a separate service.
Add-ons marked Private Cloud are available to all Private Cloud organizations. Add-ons marked On request require Laravel to grant your organization access. Organizations outside Private Cloud need that access for every add-on, including those marked Private Cloud. If an add-on you need does not appear in your environment’s settings, contact support to request access.
Shared add-ons
The following add-ons support PHP-FPM, Octane, Node.js, Bun, Deno, Go, Python, Ruby, and Rust:
The Puppeteer add-on supplies Chromium with browser libraries and fonts. Your application still declares its own Puppeteer package dependency.
PHP-FPM and Octane
PHP environments also support the following language-specific add-ons:
The PHP base images already include the ImageMagick 7 command-line tools. The ImageMagick add-on adds the
imagick PHP extension so your application can call ImageMagick from PHP code. The PHP Datadog add-on provides the Datadog PHP tracer and trace agent.
Ruby
Ruby also supports a separate Datadog add-on (datadog-ruby). This add-on is available on request.
Static sites
Plain HTML sites do not support build add-ons. For static site generators, selected add-ons apply only during the language build. They do not carry over to the final serving image.Inspect your environment
The exact installed inventory includes inherited packages, resolved dependencies, and any selected add-ons. From your environment’s Commands tab, you may list installed operating system packages and their versions:dpkg. It does not list tools copied into the image or compiled from source, such as Composer or the PHP image’s ImageMagick installation. Check those tools directly, for example in a PHP environment: