Ship it. Own it. AI-powered deploys to servers you own.

Shipown has an AI terminal operator. With your own Anthropic, OpenAI or DeepSeek API key, you describe a problem in plain language — a 502 from Nginx, a crashed PM2 process, a full disk — and the model inspects the server and proposes one shell command at a time, with its reason. You approve each command before it runs, and destructive ones such as recursive deletes, reboots, firewall flushes or stopping SSH are always held for confirmation. The AI never runs on Shipown's servers: requests go from your computer to the provider you chose.

Managed platforms run your app on their runtime and their account. Shipown deploys to a server you already rent or own, over plain SSH, and installs no agent to do it. You keep the smooth workflow without handing over the infrastructure.

Those are self-hosted platforms you install on a server: a web dashboard and its services run there, and apps are deployed as Docker containers. Shipown is a desktop app instead. Nothing of it is installed on the server — it connects over SSH and uses what is already there — so Node apps can run directly under PM2 and static sites straight from Nginx, with no Docker required, while Dockerfile and Compose apps are deployed too. It also adds an AI terminal for diagnosing the server.

Deployment flows cover Node applications run by PM2, static sites served by Nginx, and supported Dockerfile or Compose projects. Configure the build command, output, port and environment for your project. Other languages have no native deployment runtime here; a compatible container may be an option. Check the supported environments and limitations before choosing a setup.

No. Node applications run directly under PM2 and static sites are served by Nginx, on a server with no Docker at all. If you do use Docker, Shipown deploys to it as well — a Dockerfile or a compose file, with releases, health checks and rollback — and manages the containers already on the server: every container inspected, published and internal ports mapped, CPU and memory gauges, crash loops called out, start, stop, restart, a shell inside the container, and its logs. It can also install Docker on a server that has none.

A Linux VPS, cloud VM or bare-metal server you control and can reach over SSH. Compatibility depends on its OS, architecture, permissions and runtime prerequisites. See /docs/supported-environments for the current scope and verification status.

Shipown opens the deployment SSH connection from your desktop to your server. The desktop app also uses a hosted licence service for activation and periodic validation, with limited offline grace, and a hosted update service. GitHub, package registries, certificate services and optional AI providers may be used by the flow you choose. A cloud-hosted VPS is a valid target.

Private key files are read by the desktop main process for SSH authentication. Deployment sends project files and environment values to your selected build or target machine as needed. Licence and diagnostic requests are separate from that transport. The optional AI terminal sends prompts and command output to your chosen provider, so review output for secrets before sharing it.

Only to the provider you choose (DeepSeek, Anthropic Claude, or OpenAI), and only while you actively interact with it. The AI operator sends your prompt and the terminal outputs of the commands it runs under your own encrypted API key. Shipown does not intercept or store this telemetry. Destructive commands (reboots, rm -rf, firewall changes, stopping SSH) are never executed automatically without your explicit confirmation.

Shipown-managed apps can return to a retained release when its files or image are still available. Detected runtime failures trigger recovery attempts, which can themselves fail if the server is unreachable or prerequisites are missing. A running process without an HTTP response can be retained with a warning. Database migrations and persistent data need a separate recovery plan. See /docs/troubleshooting for recovery steps.

No. Shipown tells you when a branch has moved ahead of what a server is running, and how many commits are waiting, but a person still presses deploy. Automatic deployment on push is not part of it.

No. Shipown is a commercial product and its source is not published. What runs on your servers is plain SSH and shell — nothing is installed to phone home — but the desktop application itself is licensed, not open.

Every plan starts with a free 30-day trial and no card is asked for until you buy. What you get is a licence key with an expiry and a device limit — typically two machines. Activation is checked by the licence server rather than by the app, so a key can be extended, replaced, or have a device slot freed without reinstalling anything.

Windows, as an .exe installer, macOS, as one .dmg for Apple Silicon and Intel, and Linux, as a .deb for Debian and Ubuntu. All three come from the same download server the app updates from, so the file on the download page and the file an update fetches are the same file.