# OpenShip vs Netlify

URL: https://openship.io/compare/netlify

Give your site and its supporting services the same home.

[Migrate to OpenShip](https://openship.io/migrate/from-git)

## Why choose OpenShip

Serve a static site directly at the edge, or deploy a full application alongside workers and databases. OpenShip adds native Compose, integrated mail administration and a choice of managed Cloud or your own infrastructure. Your frontend can grow into a broader stack without requiring a separate deployment panel for each part.

### A direct path to your application

OpenResty serves traffic without routing requests through the OpenShip API or database. Edge analytics aggregate in memory, and static sites can be served as files without a persistent application process.

[Explore this capability](https://openship.io/features/traffic-analytics)

### Your infrastructure. Your control plane.

Choose managed Cloud, an always-on self-hosted dashboard or optional Desktop. Keep the same deployment workflow as your infrastructure changes.

[Explore this capability](https://openship.io/features/deploy-anywhere)

### A mail server, built in

Operate domain mailboxes, webmail and mail DNS from OpenShip, with an external relay for outbound delivery. Keep email administration alongside your applications.

[Explore this capability](https://openship.io/features/mail)

## The practical differences

| What matters | OpenShip | Netlify |
| --- | --- | --- |
| Where your apps run | Managed OpenShip Cloud, or your own servers. | Provider-managed infrastructure. |
| Deployment model | Git, images, native Compose, static sites and workers; connected Swarm and k3s from self-hosted or desktop controllers. | Web deployments, functions and Netlify platform services. |
| Control plane | Always-on self-hosted web dashboard, managed Cloud or optional Desktop. Dashboard, CLI, API, SDK and MCP access. | The provider hosts and operates the control plane. |
| Build resources | Choose controller or destination builds on supported paths; retain reusable caches with storage-aware cleanup. | Builds and deployment artifacts use the provider's supported pipeline. |
| Operating responsibility | Cloud infrastructure is managed. On your servers, you retain server responsibility. | The provider operates the platform; you configure your applications. |

## Three ways to run OpenShip

### Self-hosted web dashboard

Run OpenShip on your infrastructure for an always-on dashboard, team access, webhooks and automation. Deploy on the same server or manage connected servers.

[Get started](https://openship.io/docs/getting-started/installation)

### Managed OpenShip Cloud

Let OpenShip operate the platform and managed compute. Your projects share the CPU, memory and storage of their Cloud Space.

[Get started](https://openship.io/pricing)

### Optional desktop app

Keep the control plane on your Mac, Windows or Linux computer when you want to manage servers without exposing a public dashboard. Deployed workloads keep running when the app closes.

[Get started](https://openship.io/download)

## Where Netlify fits

Netlify combines web deployments with functions and platform services. It fits teams whose sites and workflows rely on Netlify's deployment and integration model.

## Plan your move

Repository and data migration

Bring the repository and environment variables. Review netlify.toml, redirects, functions, forms and stored data; platform-specific behavior needs an explicit replacement or external service.

[Open migration guide](https://openship.io/migrate/from-git)

## Check the details

Reviewed on 2026-11-16

- [Netlify Functions](https://docs.netlify.com/build/functions/overview/)

[OpenShip documentation](https://openship.io/docs)
