Home/Solutions/Platform teams
For platform teams

Golden paths, without the tickets.

Describe each stack once and let teams deploy it themselves, inside your guardrails.

Book a demo See pricing
A template with Docker services and a Helm chart
Real Shipfast screen · sample data
Sound familiar?

The platform team became the bottleneck.

Built by handEvery environment, every cloud.
A queue of ticketsDays for a namespace or a domain.
DriftStaging and production stop matching.
Golden paths

Publish the recipe. Let teams self-serve.

Teams create apps from your templates, changing only what you allow.

  • From the images, charts and YAML you have
  • Defaults per environment
  • See every app a change affects
More on templates
Template change · Client web stackworker image v2.15
3 apps affectedReview before it ships
client-portalmeridian-prodready
booking-apibrightsmileready
storefrontlarkspurneeds approval
IllustrativeSample apps
Guardrails

Freedom for teams. Rules for production.

Roles decide who deploys. Risky settings are caught at render.

  • Approvals per application
  • Keycloak SSO and GitHub sign-in
  • Activity log with diffs
More on security
Render check · workerkubesec
spec:  containers:  - name: worker    securityContext:      privileged: true
BlockedPrivileged container. Remove privileged: true to continue.
IllustrativeChecked before it reaches a cluster
Any cloud

One way to run every environment.

Create or connect clusters, or deploy straight to VMs.

  • EKS, GKE and VKE with Terraform
  • Connect any cluster; it dials out
  • Deploy to VMs, no Kubernetes needed
More on provisioning 
# Connect an existing cluster: copy the command from Shipfast
$ kubectl apply -f https://<your-workspace>/k8s/apply/<token>
# Installs the agent. It dials out to Shipfast: no inbound ports, no VPN.
✓ meridian-prod configured · first sync complete
Token valid for 15 minutesFull guide in the docs
What changes

Same people. Less toil.

New service for a team
BeforeA ticket and a weekAfterSelf-serve from a template
New environment
BeforeCopy, paste and driftAfterA new app from the same recipe
Production change
BeforeWhoever has kubeconfigAfterApproved by role, logged with a diff
FAQ

Questions, answered.

All questions
Do teams need Kubernetes knowledge?

No. They work with templates and applications; the platform team decides what goes into the template.

Can we keep our existing Helm charts?

Yes. Templates mix Docker images, Helm charts and Kubernetes YAML.

Can different teams have different permissions?

Yes. Roles decide who can create, deploy, approve and view, per application.

Does it work across clouds and on-prem?

Yes. The same templates run on EKS, GKE, VKE, AKS, on-prem clusters and VMs.

Now onboarding pilot teams

Ready to ship faster?

Bring one app. We'll connect a cluster and ship a release with you.

Book a demo See pricing