pep.dev

What it is

Pep.dev positions itself as a “deployment platform for coding agents.” It is not a traditional human-operated PaaS; instead, it exposes deployment capabilities to MCP-compatible agents. Claude Code, Cursor, Windsurf, Codex, Gemini CLI, and others can all connect via MCP. A typical workflow is to add @pepdev/mcp with a single command, then tell the agent “Deploy my app to pep.” The agent reads the repository, automatically generates a deployment manifest, and calls the deployment tool.

Core capabilities

The product is deliberately minimal in design: the main copy states that the API has only 3 MCP tools — deploy, status, and logs. On the platform side, it handles Docker image builds, machine deployment, health checks, and assigns each app a *.pep.dev URL with automatic SSL. Custom domains are also supported. For stack detection, static sites are served via Nginx, while server-side applications use Nixpacks. For databases, Postgres is automatically provisioned on Neon serverless, while SQLite is mounted on a Fly volume, with DATABASE_URL injected. Scale to Zero lets machines sleep when idle and wake on the first request, making it a good fit for low-traffic projects.

Pricing and openness

The page only says “you only pay for what you use,” but does not disclose specific billing units, free quotas, plans, spending limits, or payment methods. It also does not mention whether the product is open source or closed source, or whether self-hosting is available. As a result, it is hard to assess whether Pep is suitable for teams that require private deployment, compliance audits, or predictable costs.

Pros and cons

The main advantages are its short onboarding path, zero YAML, zero CLI flags, and zero IaC, which reduces the friction between an agent writing code and getting it online. Automatic databases, SSL, logs, and status checks also cover the key steps needed to launch small applications. The downside is that the available information feels more like a landing page than full documentation: production-grade limits, regions, SLA, security boundaries, rollback strategy, and detailed docs are missing. The API surface is simple, but that also means advanced deployment controls remain unclear.

Who it is for, and access from China

Pep is better suited to indie developers, heavy AI coding users, hackathons, and side projects that need to quickly obtain a public URL. We would not recommend using it for critical production systems before more information is available. Access from mainland China is not discussed in the source material; payment methods and domestic network stability are also unknown. Alternatives to compare include Vercel, Netlify, Railway, Render, Fly.io, Cloudflare Pages/Workers, Zeabur, and others.