01
SOURCE
Start with the code you have.
A Dockerfile, a compose stack, or an image from CI. PlugLayer inspects the real shape of the app before it proposes a deploy.
DockerfileComposeOCI image
The PlugLayer platform
One path fromsource to service.
Code, affordable compute, data, routing, and operations are one connected system. Deploy quickly without giving up visibility when the app is live.
PLUGLAYERThe operating flow
Four states. One continuous line.
No handoff from a deployment product to a collection of infrastructure consoles.
02
PLACEMENT
Land it on PlugLayer compute.
Choose low-cost custom capacity or a dedicated node. Placement checks available CPU, memory, and storage before a rollout begins.
Capacity checkIsolated projectPersistent storage
03
RELEASE
Watch it become a live service.
Build, route, issue TLS, verify health, and preserve the same URL through every redeploy. The whole operation stays visible as a job.
HTTPSHealth checksRollout history
04
OPERATE
Stay in the same control plane.
Read logs, open a terminal, inspect usage, attach a domain, or let your coding agent diagnose the failure without assembling another toolchain.
LogsTerminalMetricsMCP
A small vocabulary
The product model fits on one screen.
Learn four objects and every deploy, page, and agent action becomes predictable.
The boundary01
Project
Apps, data, domains, compute, and access live together.
The workload02
App
Image, environment, storage, placement, URL, and history.
The truth03
Job
Every build, provision, and rollout reports real state.
The edge04
Domain
Immediate HTTPS, then your domain when you are ready.
Ship the app. Keep the whole system visible.
Start with a repository and end with a service you can deploy, inspect, and operate from one place.