Native runtimes: how Voroa builds without a Dockerfile
How a build system detects your language from the repository, installs the right runtime, and produces a running service with no container file from you.
What this covers
A native runtime build means the platform reads your repository, works out what language and version you need, installs it, installs your dependencies, and runs your build, without you writing any container configuration. It is the default on most modern platforms because it is the fastest path from a repository to a running service, and because the platform can then keep the base image patched for you rather than leaving that job with you. The trade-off is less control: if your application needs an unusual system package, detection cannot help you.
A reference page describing how Voroa detects and builds each runtime is not published in the docs today. The language guides below cover the stacks that are documented, and the build and start commands page covers how to override what runs.