CI/CD
Service Hub
Service Hub is Planton's application delivery platform. It handles the full journey from Git push to production deployment — connecting repositories, building container images, and deploying to Kubernetes, AWS ECS, Google Cloud Run, or Cloudflare Workers.
Pipelines are powered by Tekton and triggered automatically by Git commits. Builds use Cloud Native Buildpacks for zero-config language detection or custom Dockerfiles for full control.
Core Concepts
Services
A Service is the configuration bridge between a Git repository and a deployment target. It defines what to build, how to build it, and where to deploy it. Services support monorepo configurations with per-service trigger paths and project roots.
Pipelines
Automated CI/CD workflows triggered by Git commits. Each pipeline clones the code, builds a container image, pushes it to a registry, and deploys the service. Pipelines are managed by the platform or self-managed using custom Tekton definitions.
Build Methods
How your code gets built into a container image. Options include Cloud Native Buildpacks (auto-detect language and framework), Dockerfiles, and custom Tekton pipelines.
Deployment Targets
Where your services run. Service Hub deploys to Kubernetes (EKS, GKE, AKS), AWS ECS, Google Cloud Run, and Cloudflare Workers.
Learn about Deployment Targets
Deployment Environments
Multi-environment support for deploying services across dev, staging, and production. Each environment has its own configuration, secrets, and deployment history.
Learn about Deployment Environments
Self-Managed Pipelines
Bring your own Tekton pipeline while retaining platform deployment orchestration, status tracking, and manual approval gates.
Learn about Self-Managed Pipelines
Secrets and Variables
Runtime configuration management through organization-scoped and environment-scoped secrets and variables. Secrets are encrypted with envelope encryption and decrypted just-in-time in the Runner. Variables support literal values or dynamic references to infrastructure outputs.
Ingress
DNS, domain routing, and load balancer configuration for exposing services to traffic.
Monorepo Support
Configure multiple services from a single repository with smart triggers, sparse checkout, and per-service project roots.
How Service Hub Fits in the Platform
- Infra Hub provisions the infrastructure where services run (Kubernetes clusters, ECS clusters, etc.)
- Service Hub builds and deploys applications to that infrastructure
- Connections provide Git provider and container registry credentials
Getting Started
- Getting Started Guide — Deploy your first service
- What is a Service? — Understand the core concept
- Pipelines — Learn the CI/CD workflow
- Deployment Stage — Understand deployment execution
- Kubernetes Dashboard — Monitor and debug running services
Next article
