TemperShip
Request access
Open navigation

DEPLOYMENT & INFRASTRUCTURE CONTROL PLANE

One control plane. Any deployment target.

TemperShip gives platform teams a desired-state model for deploying applications, connecting managed services, and governing infrastructure without surrendering ownership.

Available hosted or self-hosted. Your infrastructure stays yours.

Request early accessExplore the platform
Docker ComposeKubernetesCloud runtimes

checkout-api / production

healthy

APPLICATION SPEC

Source
main@8fc19d2
Build
Dockerfile
Strategy
rolling

RELEASE ROUTE

#184

Image built and scanned

registry/app@sha256:91c…

42s

Health checks passed

3 / 3 replicas ready

18s

Promoted to production

compose-prod-01

live

DESIRED STATE → VERIFIED RELEASE

VISUAL INFRASTRUCTURE CANVAS

See your environment. Plan every change.

Design applications and infrastructure as one connected system. Compare desired and actual state, inspect drift, and review proposed changes before anything reaches a provider.

commerce / production / topology

DesiredActualDriftProposed
desired

Public gateway

shop.example.com

update

checkout-api

3 → 5 replicas

observed

Compute target

cluster-prod-eu

PostgreSQL

drift

backup retention 7d → 30d

Secret binding

ready

external://prod/checkout

  1. 01

    Draft

  2. 02

    Validate

  3. 03

    Plan

  4. 04

    Approve

  5. 05

    Apply

  6. 06

    Reconcile

ONE APPLICATION MODEL

Define the workload once. Place it where it belongs.

TemperShip carries the same application intent across targets, translating it into the right runtime configuration for each environment.

Compose first
Connect remote servers, run web and worker processes, manage application routes, and roll back failed releases.
Kubernetes ready
Target existing clusters with namespace isolation, routing, jobs, limits, probes, and rolling deployments.
Cloud extensible
Connect cloud accounts and use provider-native compute, networking, identity, and managed services.

DURABLE OPERATIONS

A deployment is a record, not a shell script.

Every build, infrastructure change, rollout, and rollback is persisted, observable, resumable, and safe to retry.

  1. 01

    Fetch commit

  2. 02

    Resolve build

  3. 03

    Build image

  4. 04

    Scan artifact

  5. 05

    Deploy release

  6. 06

    Verify health

  7. 07

    Promote or roll back

THE WHOLE PLATFORM SURFACE

Manage deployments and infrastructure from one place.

TemperShip keeps deployment and infrastructure state consistent across the UI, API, provider integrations, and eventually the CLI.

Managed services
Bind databases, caches, storage, queues, search, and email without coupling the application to where they run.
Edge and domains
Model traffic, DNS, TLS, health, and gateway topology independently from the workload orchestrator.
Unified operations
Follow build logs, runtime logs, provider events, metrics, and incident timelines from the same release record.
Governed changes
Validate topology, capabilities, cost, and policy before apply. Require approvals and approved templates where they matter.
Runners and agents
Run builds and infrastructure changes on managed or customer-hosted runners. Outbound agents avoid open management ports and resolve customer-custodied secrets where policy allows.
Cost allocation
Break down local usage and cloud spend by team, project, environment, application, service, and cost center.

YOUR INFRASTRUCTURE STAYS YOURS

Choose the control plane. Keep your infrastructure.

Use TemperShip as a hosted service or run the control plane yourself. Your workloads, infrastructure, and credentials stay in accounts you control.

Hosted shared
A managed control plane with strict tenant isolation.
Hosted dedicated
An isolated, managed deployment for your organization.
Fully self-hosted
Run the same product and resource model in your environment.

control-plane.profile

customer controlled

Control plane
hosted dedicated
Runner pool
customer-hosted
Connectivity
outbound mTLS
Infrastructure
customer-owned
Secret custody
external store

DEPLOYMENT TARGETS

Start practical. Expand without a rewrite.

TemperShip starts with an end-to-end Docker Compose experience, adds Kubernetes portability, then expands into cloud compute and managed services behind the same provider-neutral contracts.

  1. FOUNDATION

    Docker Compose

    Remote hosts, visual topology planning, Git-based builds, processes, secrets, edge routing, health checks, logs, and rollback.

  2. PORTABILITY

    Kubernetes

    Existing clusters, namespace isolation, workload generation, routing, jobs, resource policy, and rolling releases.

  3. EXPANSION

    Cloud services and compute

    Provider-native data services, edge infrastructure, clusters, containers, functions, and isolated workloads.

EARLY ACCESS

Help shape the platform your team needs.

Join the TemperShip early-access list for build updates, preview availability, and opportunities to influence platform priorities.

By subscribing, you agree to receive TemperShip product updates. Confirm your address to join. Read our privacy notice.