From git push to a live app.
Connect your repository. Deplexo builds your code and gives your app an HTTPS address. Your next release starts with a push.
Free tier · No credit card required
Projects / storefront-api
storefront-api
Resources
LiveDeployment complete
Starting application on port 3000Checking application health…Health check passed · https://storefront-api.de.deplexo.comRecent deployments
Builds for your stack
- Node.js
- Python
- Go
- Ruby
- Rust
- Java
- PHP
- Elixir
- Static sites
- Any Dockerfile
- runtimes detected
- 10
- git hosts over OAuth
- 4
- config files required
- 0
- to run one app
- $0
How it works
A push is all it takes.
Connect your repository once. Each push builds your code and brings the next version online.
- 01
Connect a repository
Choose the repos you want to share. GitHub, GitLab, Bitbucket, and Codeberg connect over OAuth, with access you can revoke from one screen.
- 02
Push your code
A push starts a build using your Dockerfile. Or choose automatic detection and let Deplexo generate one for your framework.
- 03
Go live
Once healthy, your app gets its own HTTPS subdomain. Follow build and runtime logs in the dashboard, and roll back to a previous successful build.
Deplexo MCP
Your agent.
Your next deployment.
Connect Claude Code, Cursor, or another MCP client to Deplexo. Deploy from Git, check progress, and read logs from the same conversation.
Connect your agent
Included on every plan
The parts you would otherwise script yourself.
Isolation, routing, logs, and webhooks come with every app.
Secure by default
Every app runs in its own isolated container, so one app cannot see another's files or processes.
Auto subdomains
Each web service is routed to its own subdomain with HTTPS as soon as the first deploy is healthy. There is no DNS to configure.
Resource limits
Every container has hard CPU, memory, disk, and bandwidth caps set by your plan, so each app stays within its assigned limits.
Outgoing webhooks
Deployment events are sent as signed webhooks to any URL you choose, including Discord and Slack.
Real-time logs
Build output and container logs stream to the dashboard while they are written. You never need to SSH into a server.
OAuth, no PATs
Git hosts connect over OAuth and only see the repos you grant. Personal access tokens are never needed.
Before you commit
Where it stops today.
Better to read the limits here than to find them in production.
- One instance per app
- Each app runs as a single container with fixed CPU and memory. There is no autoscaling or load-balanced pool yet.
- No managed databases
- We don't provision Postgres, MySQL, or Redis. Point your app at a hosted database and store the credentials as env vars.
- One data volume per app
- The container filesystem is read-only. Your app can write to one persistent volume, mounted at /data by default and sized by your plan's disk limit, plus a small /tmp that clears on restart.
- One region for now
- Apps run in the EU (Germany). More regions are planned but not available today.
Ship your first app.
Start with one app on the free plan. Add resources when you need them.