Introducing OpenShip.
An open-source application platform for building, deploying, operating, and scaling applications on infrastructure you own.
Replace deployment tools, managed services, and infrastructure workflows with one open-source platform.
Available today:
- Mail Server (Built in. One click).
• Runs on your own VPS
• Unlimited domains
• Unlimited mailboxes
• Modern webmail included
• Connect with Gmail, Outlook, Apple Mail, Thunderbird, or any IMAP/SMTP client
• Send email directly from your applications using SMTP
• No mailbox subscriptions or API fees
• High email deliverability
- Deployment:
• Deploy any stack
• Git-based deployments
• Zero-downtime deployments
• One-click rollbacks
• Development, Staging, and Production environments
• Multi-branch deployments with isolated environments • Deploy to VPSs, dedicated servers, cloud VMs, or your homelab
- Services:
Provision the services your applications need in one click.
Replace multiple managed providers with services running on your own infrastructure.
• Supabase
• PostgreSQL
• MySQL
• MariaDB
• MongoDB
• Redis
• MinIO
• Meilisearch
• Qdrant
• RabbitMQ
• Kafka
• ClickHouse
• Elasticsearch
...and deploy any other service alongside your applications.
- Operate:
• Live deployment logs
• Live request logs
• Real-time traffic analytics
• Automated backups
• Monitoring
• Secrets management
• Domains
• Automatic SSL
• Environment variables
• Scheduled jobs
• Health checks
-Multi Environments:
• Separate Development, Staging, and Production environments
• Deploy every branch independently
• Test changes before production
• Isolated services, secrets, and configuration per environment
- Security & Teams:
• Team management
• Role-based access control
• IP allow/block rules
• Rate limiting
• Security rules
- Developer Experience:
• Web dashboard
• Native desktop application
• CLI
• REST API
• MCP support for AI agents, just add the mcp and your agent can do the work for you
• Manage your infrastructure without living in SSH
- Coming Soon:
• Multi-server clustering for applications and databases
• One-click load balancing
• Horizontal scaling across multiple servers
• Built-in high availability and failover
• Scale from a single VPS to a cluster with the same workflow
• Just add servers. OpenShip handles the rest.
Open source.
That’s a fair question. There are a few things worth clarifying about our cloud offering.
OpenShip Cloud isn’t limited to physical servers hosted by us. Cloud management is the service we’re providing; your workloads can run on your own infrastructure, while we handle the management and provide support, starting at $5.
Our VM module already serves 500+ cloud customers, with very positive feedback from the community.
As for formal SLAs, we’re actively working on introducing them and expect to have them in place within the next month as we finalize the agreements with our infrastructure providers.
In the meantime, we try to make up for the lack of formal SLA guarantees through responsive support and direct assistance.
We're bringing one-click migration from Vercel and Railway to OpenShip in the next release.
We've already built this for server-to-server and other control planes migrations, so we're extending the same experience to make moving from Vercel and Railway just as easy.
We're bringing one-click migration from Vercel and Railway to OpenShip in the next release.
We've already built this for server-to-server and other control planes migrations, so we're extending the same experience to make moving from Vercel and Railway just as easy.
We previously added MCP to OpenShip so you could control the platform from your coding agents.
But we started thinking: why should you have to leave OpenShip and go through all those connection steps just to use your own agents?
What if you could use your existing coding agent directly inside the OpenShip UI?
You could also let it work automatically based on triggers. For example, get a report when a service goes down or a deployment fails, and let your agent investigate what happened -> then send you message via your notification channel.
That's what we're working on: bringing your existing coding agents directly into OpenShip Desktop.
For example, if a deployment fails, your agent can investigate the issue and you can apply its fix with one click, without leaving OpenShip.
Update to v0.6.7 to use the new multi-environment support for the same project.
Your production environment already serves your customers, but you need a safe place to test the entire product before release.
Now you can:
→ Create multiple isolated environments under the same project
→ Connect each environment to a different branch
→ Test new versions without touching production
→ Configure each environment independently
Just go to Project → branch dropdown → select a branch → create your environment.
Same project. Separate environments. Safer releases.
OpenShip v0.9.9 is out
We strongly recommend updating to v0.9.9, which includes important security fixes, particularly for the Better Auth integration used by OpenShip.
Thanks to everyone who reported issues and helped make OpenShip more secure, Keep it up.
Manage ($5/mo): Tú aportas tus servidores (hasta 2 incluidos, +$3 cada extra). OpenShip mantiene el control plane y los mantiene funcionando. Tus apps corren en tu hardware.
Cloud (desde $12/mo): Ellos proveen el servidor completo (CPU, RAM y disco). No necesitas nada propio. Todo gestionado, precio fijo.
Misma plataforma y dashboard. Puedes migrar apps entre ambos con un clic.
We previously added MCP to OpenShip so you could control the platform from your coding agents.
But we started thinking: why should you have to leave OpenShip and go through all those connection steps just to use your own agents?
What if you could use your existing coding agent directly inside the OpenShip UI?
You could also let it work automatically based on triggers. For example, get a report when a service goes down or a deployment fails, and let your agent investigate what happened -> then send you message via your notification channel.
That's what we're working on: bringing your existing coding agents directly into OpenShip Desktop.
For example, if a deployment fails, your agent can investigate the issue and you can apply its fix with one click, without leaving OpenShip.
Oblien lets you run any image, including standard Docker images, inside hardware-isolated MicroVMs instead of regular containers.
Each VM gets its own kernel and isolation boundary while remaining lightweight.
You get the best of both worlds: keep using your existing Docker images and workflows while benefiting from much stronger isolation.
This is what allows platforms like @openshipio to run their cloud infrastructure with each customer's workload isolated in its own VM, while still taking full advantage of the existing container ecosystem.
3 ways to run OpenShip:
Self-host: free, your servers, full control.
Manage: $5/mo, your servers, we keep them running
Cloud: from $12/mo, no server needed, fixed price
Same platform. Same dashboard.
Your apps move between all three, One click migration any time.