Launch with control.

Deploy apps to servers you control — a Vercel-like deployment platform for developers, teams, agencies, and AI-built apps. Get previews, domains, SSL, logs, databases, backups, rollbacks, and production safety — on infrastructure you own, without surprise platform bills.

Roadmap · Contributing · Security · Discussions

---

Warning

Plorigo is in early development. The architecture, APIs, and data model are still changing and it is not yet ready for production use. We are building in the open — star the repo and watch the roadmap to follow along, and jump into Discussions to help shape it.

What is Plorigo?

Plorigo is an open-source BYOS (Bring Your Own Server) deployment platform. You connect a server you control — a cheap VPS, a bare-metal box, anything that runs Docker — and Plorigo gives you the deployment experience you expect from Vercel or Railway: Git deploys, preview URLs, automatic SSL, logs, databases, backups, and one-click rollbacks.

Two things make it different:

1. You own the infrastructure. No metered traffic, no surprise platform bills — you pay your server provider, and that's it.
2. Production safety is built in — including for AI-built apps. Plorigo checks secrets, databases, domains, and backups before you go live, explains failures in plain English, and keeps AI agents on a tight leash.

Your AI can read logs and suggest fixes. It cannot delete production data.

Who it's for

• Developers & indie hackers — deploy side projects and SaaS apps on affordable VPS hosts (Hetzner, DigitalOcean, Scaleway, …) with modern DX.
• Coolify / Dokploy switchers — a cleaner dashboard with safer production workflows, better backups, and easier team isolation.
• Vercel / Railway switchers — keep Git deploys and previews; lose the billing anxiety and runtime limits.
• Agencies & freelancers — host many client apps on servers you control, with isolated workspaces and safe client access.
• AI-assisted / "vibe" builders — take an app built with Cursor, Lovable, Bolt, Replit, Claude Code, Windsurf, or v0 and launch it safely.
• Internal tool builders — let teams ship with AI, but deploy with guardrails.

Highlights (planned & in progress)

See the Roadmap for what's shipping when. The platform is being built around:

• 🚀 Deployment engine — deploy from GitHub, Dockerfile, or Docker Compose, with build/runtime logs, health checks, and one-click rollback.
• 🌐 Domains & SSL — custom domains with automatic Let's Encrypt SSL via Caddy.
• 🔑 Secrets done right — per-environment, encrypted at rest, redacted in logs, write-only where possible.
• 🗄️ Databases & backups — Postgres/Redis services, scheduled backups to S3-compatible storage, and restore confidence.
• 👀 Preview environments — per-branch / per-PR previews you can share.
• 🩺 Production Readiness Doctor — catches missing env vars, hardcoded secrets, and unsafe defaults before launch.
• 🤖 Safe AI-agent gateway (MCP) — read logs and create previews; never delete production data.
• 👥 Teams & agencies — workspaces, roles, audit logs, and isolated client access.

Tech stack

Area	Choice
Control plane · agent · CLI	Go
Dashboard	React + TypeScript + Vite, TanStack Router/Query, Tailwind + shadcn/ui
API	ConnectRPC / Protocol Buffers
Database	PostgreSQL (pgx + sqlc), goose migrations
Jobs	Postgres-backed queue
Runtime / build	Docker Engine + BuildKit (Nixpacks fallback)
Reverse proxy / SSL	Caddy
Object storage	S3-compatible (MinIO, R2, S3, B2, Hetzner)
Self-host	Docker Compose

Repository structure

plorigo/
├── apps/
│   └── web/            # React + Vite dashboard
├── cmd/
│   ├── controlplane/   # Go API + workers + web serving
│   ├── agent/          # Go server agent (runs on your servers)
│   └── cli/            # Go CLI
├── internal/           # auth, deployments, servers, secrets, backups, …
├── proto/              # ConnectRPC / protobuf contracts
├── migrations/         # SQL migrations
├── deploy/             # docker-compose, Caddy, systemd
├── docs/               # documentation
└── scripts/            # dev & ops scripts

Getting started

🚧 Installation and self-hosting instructions are coming as the deployment loop lands. Watch the roadmap. Want to help build it? See CONTRIBUTING.md.

License & open core

Plorigo's core is licensed under the GNU Affero General Public License v3.0 (LICENSE).

In plain English:

• ✅ You can self-host Plorigo for free, forever, on your own infrastructure.
• ✅ You can modify it and use it however you like internally.
• ⚖️ If you run a modified version as a network service for others, AGPL requires you to publish your source under the same license. This keeps the project open and prevents closed-source clones.
• 🏢 A separate commercial license is available for organizations that need to embed Plorigo in a proprietary product or want terms other than AGPL — this is part of how the project sustains itself (alongside a future managed cloud).

The Plorigo name and logo are trademarks and are not covered by the AGPL — see TRADEMARK.md. You're welcome to run and fork the code; please don't pass off a fork as the official Plorigo product.

Community & contributing

• 💬 Questions & ideas → GitHub Discussions
• 🐛 Bugs → open an issue
• 🔐 Security → please report privately, see SECURITY.md
• 🤝 Contributing → start with CONTRIBUTING.md and our Code of Conduct

We welcome contributions of all sizes. Because Plorigo handles servers, secrets, and production data, every pull request is reviewed for correctness and safety — see the contribution guide for what that looks like.