Deployment control plane
More compute.Much lesscloud bill.
One instruction turns a repo into a running, routed, monitored app—on PlugLayer compute priced below comparable AWS, Azure, and Vercel infrastructure.
How it works
Three steps. That's the whole model.
No pipeline to assemble, no cluster to babysit, no YAML inherited from a blog post.
Choose compute
Pick a low-cost custom reservation or a dedicated PlugLayer node. We supply the capacity; you choose the size that fits the workload.
Point at your code
A Dockerfile, a compose stack, or an image you already built. PlugLayer reads the shape of your app, resolves ports, env and storage, and picks the deploy path for you.
Get a URL
HTTPS the moment it's healthy. Then logs, metrics, a shell into the running container, and your own domain whenever you want it.
Built for agents
The interface is a sentence.
PlugLayer speaks MCP. Install the plugin, add a scoped token, and your coding agent can inspect the repo, provision a database, deploy, tail logs, and fix a broken rollout — with the same permissions and guardrails as the dashboard.
One control plane
Everything the app needs, in one place.
Compute, deployments, data, domains, and observability share one model — which is why nothing ends up orphaned in a corner of your infrastructure.
Projects
An isolated namespace holding apps, data, domains, compute, and access.
Apps
One deployment with its own env, storage, slug, and rollout history.
Data Layer
Postgres, Mongo, Redis and more — provisioned and wired into your env.
Compute
What you own, what's free, what each app is consuming.
Domains
Registrar-shaped DNS records, verified and routed for you.
Monitoring
Live logs, resource usage, and health, per app.
Jobs
Builds, provisioning, and rollouts tracked with real status.
Marketplace
Curated stacks launched into your own project.
Data Layer
Databases that arrive already connected.
Pick a template and PlugLayer provisions it inside your project — credentials generated at launch, persistent storage attached, connection string delivered to the app that needs it.
Why PlugLayer
The platform without the cloud markup.
PlugLayer supplies the compute and the operating layer, so you ship faster without stacking infrastructure and platform bills.
| Classic PaaS | PlugLayer | |
|---|---|---|
| Compute cost | Cloud markup plus platform fees | Lower-cost PlugLayer capacity |
| Your data | A separately billed managed add-on | Data Layer included with the platform |
| Who can drive it | A dashboard, and maybe a CLI | Dashboard, CLI, CI, and agents over MCP |
| When it breaks | A build log and a support ticket | Logs, task status, and a shell in the pod |
| What you pay for | Seats, apps, and add-ons | Compute — the platform is included |
Questions
Straight answers.
A deployment platform with its own low-cost compute. You bring code; PlugLayer supplies the capacity and handles the build, namespace, database, routing, TLS, and rollout — then keeps giving you logs, metrics, and a terminal after it is live.
No. PlugLayer supplies the compute. Choose a custom reservation or dedicated node, then deploy without setting up an AWS, Azure, or Google Cloud account.
Anything that builds into a container. A repo with a Dockerfile, a docker-compose stack that gets decomposed into apps and managed databases, or an image you already built locally or in CI.
PlugLayer exposes an MCP server. Install the plugin for Claude Code, Codex, Cursor, or any MCP-compatible client, add a scoped API token, and your agent can inspect repos, provision databases, deploy, read logs, and diagnose failures using the same APIs the dashboard uses.
Every app gets an HTTPS URL on a PlugLayer subdomain immediately. To use your own domain, add it and PlugLayer shows the exact DNS records for your registrar, then verifies and routes it for you.
Yes. Generate a GitHub Actions workflow that builds your image, uploads it to the same app, merges env vars from repository secrets, and redeploys — without changing the app's URL.
Put something real on the internet for less.
Choose PlugLayer compute, create a project, and deploy—from the dashboard or straight from your agent.