Getting Started with Service Hub

This guide walks you through deploying your first service with Service Hub. By the end, you will have connected a Git repository, created a Service, and watched a pipeline build and deploy your code.

Prerequisites

• A Planton account with an organization
• An environment created in your organization (see Platform Getting Started)
• A GitHub repository with application code
• A container registry connection (see Container Registries)

Step 1: Connect Your Git Provider

Service Hub needs access to your Git repositories to clone code and configure webhooks. Navigate to Connect in the web console and add your GitHub connection.

The setup uses a GitHub App installation — Planton creates a webhook on your repository and receives push events to trigger pipelines automatically.

See Git Providers for detailed setup instructions.

Step 2: Create a Service

Navigate to Service Hub in the web console. If this is your first service, the deploy wizard starts automatically. Otherwise, click Add New Service.

The wizard walks you through the configuration:

1. Select your Git provider — Choose GitHub (GitLab support is coming soon).
2. Pick a repository — Browse your connected repositories and select the one to deploy.
3. Name your service — Confirm the repository and give the service a name.
4. Choose a package type — Container image (for Kubernetes, ECS, Cloud Run) or Cloudflare Worker script.
5. Configure the build — Select Buildpacks (auto-detect language) or Dockerfile. Configure the container registry and optionally set project root, trigger paths, and pipeline branches.
6. Configure deployment — Choose Git-based (Kustomize overlays in your repo) or UI-based (configure deployment targets directly in the wizard). Add environments with their cloud provider and resource type.
7. Review and create — Confirm the configuration and create the service.

After creation, Planton configures a webhook on your repository and triggers the first pipeline.

See What is a Service? for a full explanation of each configuration area.

Step 3: Monitor the Pipeline

The first pipeline starts immediately. Navigate to the Pipelines tab on your service detail page to watch progress.

The pipeline progresses through two stages — Build (clone, build artifact, push to registry) and Deploy (provision cloud resources for each environment). Build logs stream in real time. Each deployment environment creates a Stack Job that you can inspect for detailed provisioning output.

See Pipelines for the full pipeline model, trigger types, and manual approval gates.

Step 4: Push Code

From this point forward, every push to a configured branch triggers a new pipeline automatically. Make a change, push it, and watch the build-and-deploy cycle run without manual intervention.

What to Explore Next

• Deployment Targets — Configure where your service runs (Kubernetes, ECS, Cloud Run, Workers)
• Build Methods — Understand Buildpacks vs Dockerfile builds
• Deployment Environments — Control which environments a service deploys to
• Secrets — Inject secrets and variables into deployments
• Ingress — Make your service publicly accessible with a DNS domain
• Monorepo Support — Deploy multiple services from a single repository