Migrating production infrastructure? Get up to ₹10,000 in migration credits. Apply now
voroaDocs
Deploys

Deploy a pre-built image from a container registry

How deploying an image you have already built differs from building from source, why teams do it, and what a private registry needs for the pull to work.

What this covers

Instead of giving a platform your source code and asking it to build, you can build the image yourself in your own pipeline, push it to a container registry, and ask the platform to run that exact image. Teams do this when the build has to happen somewhere specific, when the same image must be promoted unchanged from staging to production, or when the build needs credentials they will not hand to a hosting provider. In return the platform needs read access to your registry, which means storing a credential, and it can no longer tell you anything useful about a build it never ran.

Deploying a pre-built image from a registry is not available on Voroa today. Voroa builds from your repository.

What you can do today

Last updated August 13, 2026