How it works

From first host to scheduled release, in five steps.

PlainShip is a hosted dashboard that talks to your servers over plain SSH. Here is what happens at each step, and what it needs from you.

  1. 01 Connect your hosts over SSH
  2. 02 Keep keys and secrets in the vault
  3. 03 Ship a release
  4. 04 Automate the work you repeat
  5. 05 Schedule it and stay informed

Step 01

Connect your hosts over SSH

Add a server with its address, user and key. PlainShip checks the connection and the OS, then lists the host with its groups and tags. Nothing is installed.

  • Any Linux host with SSH and bash
  • Works through a jump host
  • Groups and tags for whole-fleet actions
Hosts list with groups, tags and online status

Step 02

Keep keys and secrets in the vault

SSH keys, tokens and .env files are sealed with AES-256-GCM. Jobs receive them as environment variables, so they never appear in a command line or a log.

  • Import an existing .env in seconds
  • See where every secret is used
  • Reveal for 20 seconds, then hidden
Secrets vault listing values and where each is used

Step 03

Ship a release

Point an app at a Git repo or a folder. PlainShip builds into a new release directory, links shared files, runs the healthcheck and only then switches the current symlink.

  • Live output while it runs
  • Hooks before and after each stage
  • One-click rollback to any kept release
Apps screen with release history and rollback

Step 04

Automate the work you repeat

Turn runbooks into readable YAML playbooks. Dry-run them first, then apply to one host or a whole group and read exactly what changed.

  • Ansible-style syntax, no control node
  • Loops, handlers and tags
  • A full log per host
Playbook editor with YAML tasks

Step 05

Schedule it and stay informed

Put deploys, scripts and checks on a cron schedule. Every run is logged, and failures reach Slack instead of a mailbox nobody reads.

  • Next runs previewed
  • Pause, resume or run now
  • Included with Pro
Schedules list with cron expressions and recent runs

On the server

Connect, run, disconnect

Each job opens an SSH session, runs bash with secrets passed as environment variables, streams the output back and closes. The server keeps nothing from PlainShip but your release folders.

Security details
Agent-based host compared with an agentless host that only needs SSH and bash

Requirements

What you need, and what you do not

On your servers

  • OpenSSH reachable from PlainShip
  • bash
  • A user PlainShip can log in as
  • Git, systemd or sudo only if a job uses them

On your side

  • An account at app.plainship.dev
  • A repo or folder to deploy
  • Five minutes for the first host

Not required

  • No agent or daemon
  • No Docker on the host
  • No inbound port besides SSH
  • No control node to run

FAQ

Before you connect a server

Short answers to what teams ask before the first host.

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 PlainShip Works — Agentless SSH Deploys in Five Steps