Ship merged code to live pods
Connect
SPIRITT
KubernetesKubernetes
Ship it. Keep it running.
SPIRITT gives your organization its own Kubernetes namespace and runs it for you. It packages your apps, deploys them with sound resource settings, exposes them on HTTP routes, runs Postgres with proven restores and keeps every workload healthy.
What you can do with Kubernetes.
A namespace ready on day one
Enable it once and every workspace in your organization deploys to the same namespace, or add named instances for isolated staging and production.
Postgres you can restore
Run Postgres with continuous WAL archiving to your storage bucket, scheduled base backups and a restore proven in a separate cluster.
Secrets kept out of manifests
Workloads read credentials synced from your workspace vault, so keys never sit in code, images or chat.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the services you want deployed and operated.
02
Turn on Kubernetes
Enable the built-in Kubernetes integration for your organization, or for one workspace when its work needs a separate namespace.
03
Delegate an outcome
Ask SPIRITT to deploy a service, stand up a database or recover a failing workload, and get the verified result back.
Hand over a mission.
Choose a mission. Make it yours.
Put Kubernetes to work.
Your namespace, fully operated
Questions
Kubernetes, with SPIRITT.
01What does the Kubernetes integration include?+
It is built into SPIRITT. Enabling it creates a dedicated Kubernetes namespace for your organization with its own service account, access credentials and monitoring access. SPIRITT deploys and operates your workloads there directly, with no cluster to set up first.
02Can teams or environments get separate namespaces?+
Yes. Enabled for the organization, all of its workspaces share one namespace. Add named instances for staging or production, or enable it on a single workspace when that work must stay apart from sibling workspaces.
03What can SPIRITT run there?+
Web apps, APIs, background workers, scheduled jobs and Postgres databases, exposed through HTTPRoute. Workloads run with CPU and memory requests, memory limits and privilege escalation disabled, so they behave well in a shared cluster.
04How are database backups handled?+
SPIRITT runs Postgres with CloudNativePG, archiving WAL and scheduled base backups to your workspace storage bucket. Before you rely on it, SPIRITT writes new data, forces an archive and recovers it into a separate cluster to prove the restore.
05How do workloads get their API keys?+
From your workspace vault. Secrets are synced into the namespace as Kubernetes secrets that workloads reference, so values never appear in manifests, images, logs or chat.
06Can it deploy straight from my repositories?+
Yes. SPIRITT builds images from your GitHub or GitLab code, pushes them to your GitLab container registry, rolls them out in your namespace and reports the live version back on the merge request or pull request.