APCO CloudShip apps to the web in one command.

A mini-PaaS for shipping apps. Push source or an existing OCI image and it goes live at .apco.space — with managed Postgres or MariaDB, logs, and analytics. Built to be driven by humans and AI agents alike.

Quickstart

CLI reference

For AI agents

🚀

Deploy in seconds

apco deploy builds static/SSR source with Railpack or pulls and digest-pins an existing OCI image, then serves it on a TLS subdomain.

How deploys work

🗄️

Managed databases

Pro projects choose Postgres or MariaDB and get isolated Production, Preview, and Dev databases, with exact-channel DATABASE_URL injection and a channel-aware Database Studio.

Managed databases

⚡

Realtime, built in

The @apco/db and @apco/realtime SDKs give your app typed SQL and server-sent-events pub/sub with no extra infrastructure.

Realtime guide

🤖

Agent-first

Every command speaks --json, and an MCP server (apco mcp) exposes deploy, logs, env, metrics, and database tools so AI agents can run the platform.

The agent contract

🔁

GitHub App deploys

Push your Production branch or open a pull request. GitHub Checks follow the build, every PR gets an isolated Preview, and fork code stays blocked until a maintainer approves the exact SHA.

Configure the App

🔧

Hybrid dev

apco dev runs local HMR, and apco dev --sync pushes to a live dev-.apco.space preview channel without touching production.

Hybrid dev

📊

Analytics & metrics

Per-project requests, bandwidth, status codes, top paths and referrers, approximate unique visitors, and container CPU/RAM/disk — no setup, no third-party script.

Analytics