A self-hosted Platform-as-a-Service (PaaS) for deploying Deno applications.
Denploy MUST run on your own infrastructure. It CANNOT run on:
- ❌ Deno Deploy (serverless)
- ❌ Vercel, Netlify (serverless)
- ❌ Cloudflare Workers (edge runtime)
Denploy MUST run on:
- ✅ Your own VPS/Server (DigitalOcean, Linode, AWS EC2, Hetzner, etc.)
- ✅ Local development machine
- ✅ On-premises server
- ✅ Any machine where you have root/sudo access
Why? Denploy spawns child processes, manages Nginx configs, and stores files on disk - features not available in serverless environments.
- 🚀 Deploy Deno apps via web upload (single files or ZIP)
- 🌐 Automatic subdomain routing (myapp.denploy.local)
- 🔐 User authentication and management
- 📊 Real-time deployment logs via WebSocket
- 🔄 App lifecycle management (start, stop, restart)
- 🔧 SSH access for app configuration
- 📦 Environment variables management
- ⚡ Built with Deno, Hono, and Deno KV
- Runtime: Deno 2.x
- Framework: Hono
- Database: Deno KV
- Reverse Proxy: Nginx
- Real-time: WebSockets
- Scheduling: Deno Cron
-
Prerequisites:
- Deno 2.x installed
- Linux, macOS, or WSL2 (Windows)
-
Clone the repository:
git clone <repository-url>
cd Denploy- Run the platform (no .env needed for local testing):
deno task dev-
Access the dashboard at
http://localhost:3000 -
Register an account and deploy your first app!
Note: For local testing, .env is optional - defaults work out of the box. For production deployment, see DEPLOYMENT.md.
deno task dev- Start development server with watch modedeno task start- Start production serverdeno task test- Run testsdeno task check- Type check
User Browser → Nginx → Platform (Hono) → Deno KV
↓
User Apps (Deno processes)
MIT