MoDPR v1.5.0
Build it. Store the digest. Deploy the exact bytes.Observe it. Promote it. Roll it back.
MoDPR is a private container registry plus a local PaaS control plane. You tag USER/name:tag with the modpr CLI. The Hub stores the image. Projects deploy that immutable digest as a service — tags are aliases, never runtime identity.
01
Login with modpr
The same username as this website. The CLI authenticates against this registry, not a public catalog.
02
Push to your namespace
modpr build and modpr push store USER/name:tag here. A digest identifies the exact bytes.
03
Deploy the digest
Projects → staging → create a service. MoDPR pins the digest, checks policy, and runs replicas on this host.
What MoDPR does
A public catalog is a list of images for the internet. MoDPR is the registry you push into, the table of tags you inspect, the engine that can run those images, and the control plane that deploys an immutable digest.
Projects
Organization / project / environment / service. Deploy the digest, promote staging to production, roll back, inspect the artifact graph. Administrators use the Projects tab; developers deploy with the CLI.
Open projects →
Registry
Private repositories under your username. Sign in to see them. Push with modpr. Start still runs a tag on the host engine.
Open registry →
Image management
Digest table plus the filesystem layer stack. Tags (sidebar) is the named-tag list and modpr pull. Shared layers are reused on the next pull.
Open image management →
Catalog
Public images you can start on this host, plus the private tags you pushed. Project marks identify those public names only.
Open catalog →
Host engine
Containers, volumes, and networks on this server. Start pulls or uses the image here — not only a remote pull to your laptop.
Open host engine →