suparship — you push, it ships

Why teams choose suparship

Ship in hours, not release trains

Every pull request gets a live preview; every merge ships itself. Ideas reach users the same day they're written — with production safely gated behind one click.

Own everything. Locked into nothing.

Runs on your clusters, stores its state in your git repos, and builds on open CNCF standards. No per-seat pricing — and leaving means keeping everything, as plain Helm and git.

Platform leverage without the headcount

The golden paths an internal platform team would spend a year building — installed in an afternoon, operated by one or two people.

Simple like a PaaS. Flexible like Kubernetes.
Transparent like GitOps.

⎈

Bring your own Helm charts

No golden-cage templates. Any chart from any registry is a suparship app — the platform contract is just a handful of ((platform.*)) tokens and rendered env objects.

⎇

Preview environments per PR

Every pull request gets its own environment with its own URL, built at the PR's image tag and torn down on merge. Composed apps preview all components together.

⇧

Gated promotions

Merge to ship staging; one click for prod. Kargo drives the pipeline, each stage gated on the health of the one before — and rollback is one click too.

⌘

GitOps all the way down

Everything suparship does is a commit to your gitops repo, synced by Argo CD. Nothing hidden, nothing imperative — the audit trail is git log.

⚿

Secrets done right

HashiCorp Vault or 1Password as the backend; per-cluster read tokens sealed with sealed-secrets and delivered by External Secrets. Developers just name a variable.

⧉

A developer UI on vanilla charts

Platform engineers curate which values developers see; devs get a clean form and env-scoped variables — no YAML spelunking, and the chart underneath stays plain, unmodified Helm.

What your developers see

From the one-command demo: a React + FastAPI + Postgres app through the whole golden path.

suparship project dashboard with app health per environment — **Project dashboard.** Apps with live health per environment and their URLs — what a developer sees when they log in.

suparship create-app wizard configure step — **Create an app, end to end.** Pick a template, name the app, configure the component through curated fields — targets, namespace, delivery, variables, all one page.

suparship developer values form with curated fields — **A curated form, not a values dump.** Platform engineers pick which Helm values each chart exposes. Untouched fields keep inheriting; Advanced still shows everything.

suparship advanced values editor with platform tokens — **The same contract in YAML.** Your override is seeded as commented lines — uncomment to own one. ((platform.*)) tokens wire values to platform-managed objects.

suparship app detail: staging to prod pipeline with a live PR preview — **Each app is a pipeline.** Staging promotes to prod, and the pr-1 badge is a live preview environment from an open pull request.

suparship previews page with a live per-PR environment — **Every PR gets its own environment.** Built at the PR's image tag, with its own URL and its own database. Merged? It's gone.

suparship promote to prod confirmation — **Production is one click — and gated.** Promotion re-tags the exact staging release to prod via Kargo. Rollback is one click too.

suparship app variables and secrets with environment scopes — **Variables & secrets, scoped.** App-level values apply everywhere — with a guardrail reminding you that includes production. Each env and cluster overrides.

suparship resolved variables with source attribution — **See what an env actually gets.** The resolved view merges the whole hierarchy and attributes every key — extended, overridden, or inherited.

suparship per-component variable and secret curation — **Secrets, curated per component.** The database sees exactly the keys it needs, nothing else — nothing sensitive lives in chart values.

suparship template gallery — **Any Helm chart is a template.** No golden-cage DSL. Bring your own charts, curate them once, and developers self-serve from the gallery.

suparship template platform overlays with tokens — **Platform overlays per env and cluster.** Org values layered on any template — with ((platform.*)) tokens and a live effective-values pane. Smaller staging, larger prod.

Built for both sides of the platform

For developers

Push code — previews, staging, and prod URLs just appear
Configure with a form, not a values file: variables, secrets, and the knobs your platform team chose to expose
Status, logs, and diagnostics for every environment in one place — no kubectl required

For platform engineers

Curate the chart catalog and the guardrails; developers self-serve inside them
Every action lands as a commit in your gitops repo — reviewable, revertible, auditable
One control plane, many clusters: bind each environment to the cluster it belongs on

Batteries included

One-click rollback to any previous deployment
Suspend / resume environments — scale to zero, keep the data
Multi-cluster environments from a single control plane
SSO (any OIDC provider) with team-based RBAC
Local users via one-time invite links — no IdP required
Project API tokens for CI
Composed apps: many charts, one app, one pipeline
Full config export as Helm values — credentials included, sealed for git

How it works

Platform team installs

One Helm install on a cluster with Argo CD + Kargo. Connect the gitops repo, registry, and secrets backend in the UI — then commit the sealed export to git.

Platform team curates templates

Bring the org's Helm charts — or any public chart — into the template registry. Layer platform, environment, and cluster defaults on top, and choose exactly which values developers see.

Developers launch and ship

Developers create apps from those templates, fill in the curated values and secrets, and push code. PRs get previews, merges reach staging, and prod is one gated click away.

Try it in one minute

No cluster needed for a first look — the demo mode runs everything in-process. Or bring up a full local platform (GitOps, CI, previews, promotion) on a kind cluster.

Read the guided tour →

# quick look — no cluster required
$ git clone https://github.com/suparcloud/suparship
$ cd suparship && cp .env.example .env
$ task dev
→ http://localhost:5173  (admin@local / admin123)

# the real thing — local kind cluster, end to end
$ task up && task demo:shipnotes