Features

Everything for SSH server work. Nothing on the server.

Atomic deployments, a browser terminal, Ansible-style playbooks, cron schedules, SFTP, Terraform stacks, Slack alerts and an AES-256 vault — in one hosted dashboard.

PlainShip apps screen with releases, deploy history and rollback

Deployments

Zero-downtime releases, on every server

Deploy from Git or a local folder. Each release gets its own directory, and a single symlink switch makes it live — so users never see a half-finished update.

  • GitHub, GitLab, Bitbucket, Gitea, Forgejo or any HTTPS Git server
  • Shared folders and .env files carried across releases
  • Healthchecks with automatic rollback on failure
  • Generated systemd units and bash hook functions
  • In-place git pull for legacy apps
Apps screen showing deploy, rollback and release history for each app
Rollback in one click

SSH terminal

A full shell for any host, right in your browser

Open a real interactive terminal with one click. Colours, mouse support and full-screen tools like htop, vim and tmux all work as expected.

  • Multiple tabs and sessions per host
  • Search the scrollback, copy on select, right-click paste
  • Broadcast typing to every open tab
  • Jump hosts, vault keys and strict host-key checks
  • Full UTF-8, emoji and Powerline glyphs
Browser-based SSH terminal showing system information and service logs
Connected in 0.4s

Playbooks & scripts

Automation written in plain, readable YAML

If you know Ansible, you already know PlainShip playbooks. Validate as you type, try a dry run, then save and schedule — every change is versioned.

  • 17 modules: shell, copy, template, file, package, service, git and more
  • Loops, conditions, handlers, tags and registered results
  • Check mode, verbosity levels and start-at-task
  • Version history with diff and one-click restore
  • Saved scripts with {{ placeholders }} asked at run time
Playbook editor with live YAML validation, insert task menu and change notes
Valid — ready to run

SchedulesPro

Cron jobs you can actually see

Run commands, scripts, playbooks, deploys or health checks on a schedule. Pick a preset or write a cron expression and preview the next runs before you save.

  • Presets plus a next-runs preview
  • Pause, resume or run now
  • Last status and full log for every run
  • Runs 24/7 with the built-in scheduler
  • Included in the Pro plan
Schedules screen listing cron jobs with their next run and last status
Next run in 14 min

Console & insights

Know what happened, on which host, and why

Output streams live into a searchable console. Afterwards, every job is saved in history, and insights show success rates, slow runs and trends.

  • Live console with ok, changed and failed counters
  • Filter by tasks, changes or errors
  • Save logs as text, ANSI or an HTML report
  • 7 to 90-day charts with KPIs and exports
Insights dashboard with job runs per day, success rate and slowest runs
7 to 90-day trends

Teams

Share the work, not the passwords

Invite your team into an organization. Each person signs in with their own account, and you decide who can operate, edit or only view a project.

  • Organizations with owner, admin and user roles
  • Private data folder for every account
  • Project sharing as operator, editor or viewer
  • Activity log for every sign-in and change
Users and sign-in screen with organization members and roles
2FA enabled

Terraform stacks

Plan and apply cloud resources from the same project

Keep Terraform files next to your inventory. PlainShip runs init, validate, plan, apply and destroy as jobs, with cloud keys taken from the vault.

  • One stack in terraform/, or a named folder under it
  • Empty, AWS and Oracle Cloud starters
  • Credentials from secrets such as AWS_*, OCI_*, TF_VAR_* or terraform.env
  • State stays in the project. A stack with live resources cannot be deleted until you destroy
  • Every run streams to the console and is kept in History
Terraform stacks documentation
# app.plainship.dev → Terraform → New stack
▶ Init     stack: web
▶ Plan     stack: web
▶ Apply    stack: web

Slack notifications

Hear about failed jobs without watching the dashboard

Paste a Slack incoming webhook once. PlainShip posts when a job fails, when you sign in from a new address, and when a backup finishes or fails.

  • Saved under My profile → Slack alerts
  • Failed jobs on by default. Successful jobs stay off until you turn them on
  • Sign-in and backup alerts, plus a send-test button
  • The webhook is sealed with AES-256-GCM. Job messages leave the log in History
Slack alerts documentation
# Slack incoming webhook, saved in the profile
https://hooks.slack.com/services/…

Failed: terraform apply web
Project: acme · Duration: 42s
Open History & activity for the log.

Files & data

Move files like you move them on your desktop

A dual-pane SFTP browser, drag-and-drop uploads and folder downloads — plus upload and download steps inside your playbooks.

Dual-pane SFTP

Browse local and remote side by side. Rename, chmod, edit and delete without leaving the page.

Whole folders, fast

Upload folders by drag and drop and download them as compressed tar.gz streams with progress.

Server to server

Transfer data directly between hosts, even through a jump host, without touching your laptop.

Browse your code

Open repositories, branches and files from any connected Git provider in a read-only viewer.

Keychain

Generate Ed25519, RSA or ECDSA keys and install them on hosts with one click, like ssh-copy-id.

Command palette

Press Ctrl+K to jump to any host, script, playbook or action in a few keystrokes.

Hosted product

Start at app.plainship.dev

PlainShip is offered as a hosted dashboard. Add a host over SSH, deploy a release, open a terminal — nothing to install on your servers.

  • Hosted app with HTTPS, sign-up and plans
  • Encrypted vault for keys and secrets
  • Atomic releases with one-click rollback
  • No agent or daemon on target servers
PlainShip hosts screen on the hosted dashboard

Under the hood

What an atomic release actually does

Every deploy builds into its own folder, links shared files, passes a healthcheck and only then switches the current symlink. If anything fails, production never notices.

Zero-downtime deployments
Atomic release flow: build into a new release folder, healthcheck, then switch the current symlink
SSH Deploys, Web Terminal, Playbooks & Vault | PlainShip