MCP-native platform

Deploy from
your AI.

Say "deploy this" to your AI coding assistant. Pep builds, provisions, and ships your app — live URL in seconds. No dashboard. No CLI. Just conversation.

claude — ~/my-app

Works with any MCP client

Claude Code
Cursor
Windsurf
Gemini CLI
OpenCode
...and any MCP client

Three steps. Zero config.

01

Write your code

Any framework, any language. Pep auto-detects your stack — Next.js, Django, Rails, Express, static sites, you name it.

~/my-app $ ls
package.json  src/  tsconfig.json
# that's it. no pep.yml, no Procfile.
02

Say "deploy this"

Your AI reads the codebase, constructs the deployment manifest, and calls Pep's MCP deploy tool. You just talk.

> Deploy my app to pep

AI calls pep.deploy()
with auto-detected manifest
03

App is live

Docker image built. Database provisioned. SSL configured. Your app is live on a *.pep.dev URL.

Build complete (nixpacks)
Machine deployed (iad)
Health check passed

https://my-app.pep.dev

Everything you need. Nothing you don't.

Smart Detection

Static site? Nginx. Server app? Nixpacks. Pep scans your codebase and auto-selects the right build strategy.

Auto Databases

Needs Postgres? Neon serverless provisioned. SQLite? Fly volume mounted. DATABASE_URL injected automatically.

Scale to Zero

Machines sleep when idle, wake on first request. Perfect for side projects — you only pay for what you use.

Custom Domains

Every app gets a *.pep.dev subdomain with automatic SSL. Bring your own domain when you're ready.

3 MCP Tools

deploy, status, logs — that's the entire API. Your AI can deploy, check health, and debug without leaving the conversation.

Zero Config

No YAML files. No CLI flags. No infrastructure-as-code. Your AI writes the manifest. Pep does the rest.

Watch a real deploy

pep deploy — url-shortener