CONTAINER IMAGE DEPLOYMENTS
Have a container? Give it a home.
Bring your application as an image from Docker Hub, a supported public registry, or your own private registry. iDeployed brings deployment, configuration, release history, and logs into one European platform.
- STEP 01
Choose your image
Use an image from a supported public or private registry, including Docker Hub.
- STEP 02
Configure your application
Set the listening port and environment variables. The platform follows the image’s own runtime user — no UID/GID forms.
- STEP 03
Deploy and inspect
Request a deployment, follow its outcome, and inspect your application’s runtime logs.
A PRECISE STARTING POINT
A tag is convenient. A digest is specific.
Container image tags can change. A tag such as latest is a convenient label, but an immutable digest identifies the exact artifact behind a release. iDeployed inspects and resolves the image so the deployment is associated with its artifact identity.
That traceability matters when you investigate a change, redeploy an existing version, or select a successful historical artifact for rollback.
ORDINARY CONTAINERS, AT HOME
Stock images run unmodified.
The normal flow follows the image’s own runtime user — you are never asked for UID/GID values. Unmodified nginx and Redis images run as-is; Redis privilege drop and background saving work out of the box.
“Run your existing container image” is the promise — not “every image ever published runs with no configuration.” Privileged workloads, host access, unusual kernel requirements, unsupported architectures, or incompatible storage needs remain meaningful boundaries.
CHANGES YOU CHOOSE
Keep configuration and image changes deliberate.
Your active image and your saved image are separate. Saving a new image in application settings does not mean that image has become the active version.
Use Redeploy current version to apply saved environment changes with the exact active artifact. Use Deploy saved image when you explicitly want to select the image saved in your application’s settings.
PRIVATE REGISTRIES
Your registry, connected per project.
Connect a private registry at the project scope and use its images like any other. Credentials stay protected and masked in the dashboard — the normal workflow never reveals stored values back to the browser.
KEEP EXPLORING
YOUR NEXT CHAPTER
Good ideas deserve
to be out there.
Bring your code. Make something people can use.