Onboarding a small group of alpha users Now onboarding a small group of alpha users
Deploy Crate connects to your cloud accounts, provisions hardened servers, and handles deployments, logs, and monitoring. Same simplicity as Render, fraction of the cost.
Provisioning, deployments, monitoring, maintenance, and secrets. One platform handles all of it.
Connect your cloud account, pick a size. DeployCrate provisions and hardens the server automatically.
Blue-green, canary, rolling. Deploy across servers and environments from a single dashboard.
Server metrics, application logs, and reverse proxy stats. Everything in one place, no external tools.
Continuous uptime monitoring. Get notified the moment something goes wrong.
Security patches and OS updates applied automatically. Your servers stay current without you lifting a finger.
Environment variables and application secrets managed per app, per environment. No .env files on servers.
Cost
Choosing a VPS gives you more compute for less spend. DeployCrate makes sure that decision doesn't cost you 20 hours a month in DevOps work.
Comparing 2 vCPU · 8 GB RAM VPS instances, monthly cost
Control
No vendor lock-in. Setup access is temporary, ongoing operator access is limited, and every server runs in your cloud account under your keys.
They're provisioned in your cloud account under your SSH keys. Cancel your subscription and nothing changes: your servers keep serving traffic, and your apps keep running.
Telemetry, deploy history, configs. Export everything in one click using standard formats, with no proprietary vaults or support ticket required.
| Area | What DeployCrate stores | What DeployCrate can do later |
|---|---|---|
| SSH credentials | Your public key is written to the server during setup. One-time provisioning credentials are cleared after the server is configured and you have saved your keys. | DeployCrate cannot SSH back in or open a shell unless you explicitly grant new access. |
| Cloud provider keys | Stored only when you want DeployCrate to create, resize, or replace servers for features like auto-scaling. | Used for server lifecycle actions you enable. Bring existing servers if you do not want ongoing provider access stored. |
| Crate Operator API | Stores the operator API key and server ID needed for the managed server to identify itself. | Handles deployments, logs, metrics, WireGuard config, and service control through a dedicated operator user. |
| Operator sudo permissions | A sudoers policy is installed for the crate-operator system user. | Limited to DeployCrate units, managed app services, selected journald logs, Docker, node exporter, package updates, WireGuard, and DeployCrate-owned paths. |
| Customer data | Server metadata, configs, telemetry, deploy history, and app settings needed to run the product. | Export it when you leave. Your servers keep running in your cloud account under your keys. |
No Ansible playbooks. No 200-line bash scripts. Just connect, configure, and deploy.
1
Link your Hetzner, DigitalOcean, or any VPS provider. I provision, secure, and monitor them automatically.
2
Point to your repo, pick a deployment strategy, and set your environment variables. That is it.
Environment
DATABASE_URL=••••••••
3
Trigger a deploy. Your code deploys automatically with health checks, rollback support, and real-time logs.
✓ Building image... 12s
✓ Pushing to registry 8s
✓ Deploying to prod-1 15s
✓ Health check passed 3s
Deploy complete v2.4.1
Pricing
I am giving full Business-tier access to 10 teams willing to actively test the platform and provide feedback.
Perfect for side projects and small apps.
$5 per month
Everything small teams need to ship with confidence.
$12 per month
Scale across teams, regions, and workloads.
$24 per month
DeployCrate writes your public key to the server during provisioning. Setup credentials are temporary and cleared after the server is configured and you have saved your keys. After that, DeployCrate does not keep standing SSH access to your server.
Only if you want DeployCrate to create, resize, replace, or scale servers for you. If you bring existing servers, you can avoid ongoing provider-key storage and still use DeployCrate for deployments, logs, metrics, and maintenance.
Your servers run in your cloud account under your keys. The apps keep serving traffic, and the source-available Crate Operator keeps running on the server. You can export your data and continue operating the infrastructure directly.
No. DeployCrate is a managed control plane for servers you own. You bring the cloud account or VPS. DeployCrate provisions, hardens, deploys to, monitors, and maintains those servers without moving your apps onto proprietary infrastructure.
Those tools are great if you want to run and maintain the deployment platform yourself. DeployCrate is managed for you. You get the VPS cost advantage without adding another self-hosted system to patch, monitor, and debug.
Yes. DeployCrate is stack-agnostic and works with containerized apps across languages and frameworks. It is built for teams that want Render-like simplicity without being forced into one ecosystem or provider.
Watch how DeployCrate provisions hardened servers, deploys apps with zero-downtime strategies, and collects telemetry. All without you touching a terminal.
I am onboarding a limited number of teams for free Business-tier alpha access. Cheaper, simpler server management without giving up control.