Ship code from Git to production
Deploying a microservice shouldn't require a PhD in Kubernetes. But today, shipping a backend service means wrestling with Dockerfiles, Helm charts, CI pipelines, ingress configs, and secret management.
ServiceHub: Connect your Git repo. Push code. Planton builds, deploys, and manages your service across any environment. Vercel for your entire backend.
git push → production
3
Build Modes
4+
Deploy Targets
Git Push
to Production
Multi-env
Promotion
Git to Production
Connect your GitHub or GitLab repo. Planton detects your build method, builds with managed pipelines, and deploys to your target.
Three build modes — Buildpacks for zero-config, Dockerfile for control, pre-built images for CI flexibility
Webhook-triggered pipelines that fire on push, tag, or PR events
Sparse checkout for monorepos — build only what changed
Service Manifest
apiVersion: service-hub.planton.ai/v1
kind: Service
metadata:
name: payments-api
org: acme-corp
spec:
gitRepo:
cloneUrl: https://github.com/acme/payments.git
defaultBranch: main
gitRepoProvider: github
packageType: container_image
pipelineConfiguration:
imageBuildMethod: buildpacks
pipelineBranches:
- mainMulti-Environment Promotion
Define your environments. Push to a branch, trigger the right pipeline. Promote across environments with approval gates.
Dev
Push to main
Staging
Auto-promote
Production
Approval gate
Dev
Push to main
Staging
Auto-promote
Production
Approval gate
Environment Config
▶ Pipeline: spl-a7c3f1 (payments-api)
Trigger: push to main (abc1234)
✓ Build — 2m 18s (Buildpacks)
✓ Deploy — dev (auto)
✓ Deploy — staging (auto)
⏳ Approval — production
Waiting for: platform-teamTag & PR Flows
Deploy on merge to main or on version tag. Configurable triggers per environment.
Sequential Stages
Promotion rules ensure code flows dev → staging → production in the right order.
Approval Gates
Automated or manual approval with configurable rollback policies.
Kustomize Overlays
Environment-specific config in your repo. Variables, secrets, resource limits — all version-controlled.
Everything you need to ship and run services at scale
From a single API to a fleet of microservices — ServiceHub handles the build, deploy, and operate lifecycle.
Deploy Anywhere
Kubernetes, ECS, Cloud Run, Cloudflare Workers — same service definition, different targets. Switch providers without rewriting your pipeline.
Ingress Made Simple
Domain, TLS, routing — Planton handles the Istio and cert-manager plumbing. Point your domain, push your code.
Pod Access
Stream logs, exec into containers, inspect resources — all from the Planton console, with IAM-scoped access.
Debug in production without kubectl config
Stream logs, exec into containers, inspect resources — all from the Planton console or CLI, with IAM-scoped access.
planton service logs
Real-time Logs
Stream logs from any pod and container. Filter by severity, search by keyword.
Container Exec
Exec into running containers for debugging — scoped by IAM role, not cluster access.
Resource Browser
Browse pods, services, and config maps with RBAC-controlled visibility.