Agentless SSH deployment

Agentless deployment over plain SSH.

PlainShip is a hosted dashboard for the server work you already do: deploy code with atomic releases and one-click rollback, run Ansible-style playbooks, open a browser terminal and keep SSH keys in an encrypted vault. Nothing is installed on your servers.

Free plan, no credit card Any Linux host with SSH Nothing installed on your servers

PlainShip dashboard listing hosts, groups and live SSH status
0
agents to install, update or patch on your servers
1 click
to roll back to the previous release
AES-256
GCM vault for keys, tokens and passwords
Flat
price per organization — never per server

Runs on any Linux host you can SSH into

  • Ubuntu
  • Debian
  • Rocky Linux
  • AlmaLinux
  • Alpine
  • Amazon Linux
  • Fedora
  • Hetzner
  • DigitalOcean
  • AWS EC2
  • Oracle Cloud
  • Linode
  • OVHcloud
  • Raspberry Pi
  • Bare metal

Inside the product

The screens your team opens every day

Real screenshots from app.plainship.dev — not mock-ups.

Atomic releases with a real rollback

Each deploy builds into its own release folder, passes a healthcheck, then switches the current symlink. The previous release stays one click away.

See every feature
PlainShip apps screen with atomic release history and rollback

Who it is for

Built for the people who keep servers running

Not an enterprise control plane. A focused dashboard for the SSH work you already do.

How it works

From first host to scheduled release

  1. 01

    Add a host

    Paste an address and pick a key. PlainShip connects as the user you already use — nothing is installed.

  2. 02

    Ship a release

    Point an app at a Git repo. Build, healthcheck and an atomic symlink switch, with live output.

  3. 03

    Automate the repeat work

    Turn the steps you trust into playbooks, dry-run them, then put them on a schedule.

The full walkthrough
app.plainship.dev · Apps → api
▶ Deploy api @ main

Why agentless

Your servers stay exactly how you built them

PlainShip connects over SSH, runs the job with bash and disconnects. No daemon to patch, no inbound port to open, no credentials left on disk.

How we handle keys and access
An agent-based host needs a daemon, updates and an open port; an agentless host only needs SSH and bash

Compare

Honest about where PlainShip fits

Coolify, AWX and CI pipelines solve real problems. Here is when a hosted SSH dashboard is the better tool — and when it is not.

Case study

We stopped treating production as a private script on someone’s laptop. The same dashboard customers see is how we ship.

PlainShip engineering

  • < 2 minTypical production release
  • 1 clickRollback when a healthcheck fails
  • 0 agentsInstalled on application servers
How we deploy PlainShip with PlainShip

Clients about us

A calmer way to ship and stay on call

Short perspectives drawn from common team workflows. They are illustrative composites, not verified customer endorsements.

Illustrative composite

“We stopped shipping from whoever happened to have the laptop with the right key. The client fleet lives in one place now.”
Agency engineering leadComposite example · Agency team

Illustrative composite

“Terraform builds the boxes. The deploy and on-call work finally has one place the whole team can understand.”
Platform engineering teamComposite example · Platform ops

Illustrative composite

“We kept our servers and pipeline. We just stopped being nervous about the deploy step.”
SaaS co-founderComposite example · SaaS team

Illustrative composite

“The jobs did not change. What changed is that we can finally see what ran and whether it worked.”
IT operations leadComposite example · IT operations

Illustrative composite

“A new teammate can find the last release, open a shell, and follow the same process without collecting keys from three people.”
Product engineering teamComposite example · Product team

The marks and quotes above are placeholders for design purposes, not actual client logos or testimonials.

FAQ

Questions teams ask first

Agents, Docker on servers, Coolify, Ansible, keys and pricing.

What does “agentless” mean?

PlainShip connects to your servers over standard SSH and runs small bash scripts. Nothing is installed on the server — no Docker agent, no daemon to update, monitor or secure.

Do my servers need Docker?

No. Target servers only need SSH access and bash. Git, systemd and sudo are used when a job asks for them. PlainShip itself is the hosted dashboard at app.plainship.dev.

Can I self-host PlainShip?

No. PlainShip is a cloud (SaaS) application only, at app.plainship.dev. There is no self-hosted edition, download or CLI to install — sign in from the browser or the mobile app.

How is PlainShip different from Coolify?

Coolify is strong when you want containers and a PaaS-style stack. PlainShip is for SSH and VMs: atomic releases, playbooks, a browser terminal and a vault — without putting an agent on the host. Read the Coolify comparison for details.

How is PlainShip different from Ansible / AWX?

PlainShip uses familiar Ansible-style YAML and adds a hosted UI, atomic deploys with rollback, schedules, a secrets vault and team accounts — without running a heavy control node or agents. Read the AWX comparison for details.

How do you keep SSH keys safe?

Keys, tokens and passwords live in an AES-256-GCM vault. Jobs receive them as variables; they are not pasted into command lines. Workspaces are private to your organization.

Agentless SSH Deployment Dashboard | PlainShip