Platform Tour

Platform TourConsoleNavigation

Platform Tour

This page walks through the Planton web console section by section, explaining what each area does and how to navigate between them. Use it as a reference during your first week on the platform.

Console Layout

The console has three main areas:

  • Header β€” context selector (top-left), search, Deployment Component Store and IaC Module Registry (top-right)
  • Sidebar β€” primary navigation to all platform sections
  • Main content β€” the active page, which changes based on your sidebar selection and context

Context Selector

The context selector sits in the top-left of the header, next to the Planton logo. It shows your current position in the resource hierarchy:

Acme Corp / production
    ↑            ↑
Organization   Environment

Clicking the context selector opens a dropdown that lists your organization and its environments. Selecting a different environment changes what resources, services, and connections are visible throughout the console. Organization-level pages (Connections, Billing, Settings) remain the same regardless of environment selection.

The CLI equivalent is planton context set:

# Set your working context
planton context set --org acme-corp --env production

# View current context
planton context get

The sidebar contains seven sections. Here is what each one does.

Dashboard

The landing page after login. For new users, it shows the getting-started checklist (8 tasks across 4 groups β€” Foundation, Infrastructure, Applications, Team and Operations). For active organizations, it shows resource summaries, recent deployments, and notifications.

Infra Hub

The infrastructure management section. The Infra Hub route activates for cloud resources, infra projects, and environments.

Cloud Resources tab β€” lists all deployed infrastructure in the current environment. Each row shows the resource name, kind (e.g., AWS VPC, GCP GKE Cluster), status, and last deployment timestamp. Click a resource to see its full configuration, stack job history, and outputs.

Infra Projects tab β€” lists Infra Chart deployments. Each Infra Project groups multiple related Cloud Resources deployed as a coordinated unit. The detail view includes a DAG visualization showing resource dependencies and deployment progress.

Environments tab β€” lists environments in the organization with creation details.

Learn more about Infrastructure

Service Hub

The application deployment section. Service Hub manages the full lifecycle from Git repository to running service.

The Service Hub route covers several tabs:

  • Services β€” list of connected Git repositories configured for deployment
  • Variables β€” environment variables grouped and scoped to services
  • Secrets β€” encrypted secrets managed through the Secrets Manager
  • Domains β€” DNS domains and ingress configuration
  • Package Repositories β€” NPM and Maven registries for build-time resolution
  • Hosting Providers β€” deployment targets for Cloudflare Workers (Wrangler credentials)
  • Environment Promotion β€” promotion policies for moving deployments between environments

Learn more about CI/CD

Agent Fleet

An AI agent management area for defining agents, skills, and reviewing execution sessions. Agent Fleet operates independently from infrastructure and application deployment.

Connections

Where you manage credentials and integrations with external services. The Connections page organizes providers into categories: Infrastructure (AWS, GCP, Azure, and others), DevOps Pipeline (GitHub, GitLab, container registries), Infrastructure as Code (state backends), and Managed Services.

The Connections route also includes a Runners tab, where you manage Runner deployments β€” the secure execution agents that run in your infrastructure.

Learn more about Connections | Learn more about Runner

Billing

Subscription and usage management. Contains two sub-pages:

  • Plans β€” view available subscription tiers (Free, Plus, Pro) and your current plan
  • Subscription β€” manage payment methods and view billing history

Learn more about Billing

Settings

Organization-wide configuration with three tabs:

  • General β€” organization name, description, contact email, and logo
  • Manage Members β€” invite new members via email, view current members and their roles, manage pending invitations
  • Teams β€” create teams, add members to teams, and manage team-level permissions

Learn more about Teams and Access

Header Actions

Beyond the context selector, the header provides quick access to two important features:

Deployment Component Store

Click the store icon in the header (right side) to open the catalog of deployable infrastructure components. The store has two sections:

  • Deployment Components β€” individual Cloud Resource templates (e.g., AWS VPC, GCP GKE Cluster, Azure AKS). Filter by cloud provider and search by name. Click Deploy on any component to start the deployment wizard.
  • Infra Charts β€” pre-composed collections of Deployment Components that deploy together as a coordinated unit (e.g., an AWS ECS environment with VPC, cluster, load balancer, and DNS).

IaC Module Registry

Click the IaC Module Registry icon in the header to browse the Pulumi and Terraform modules that back each Deployment Component. This is useful for understanding what infrastructure-as-code runs behind a deployment, or for referencing module parameters.

Context-Driven Content

The console adapts based on your current context:

  • No organization β€” dashboard prompts you to create one
  • Organization selected, no environment β€” organization-level pages (Connections, Billing, Settings) are accessible; environment-scoped pages prompt you to create or select an environment
  • Organization and environment selected β€” all pages show content scoped to that environment

Finding Resources

There are three ways to find what you need:

  1. Sidebar navigation β€” click the section name to see all resources of that type
  2. Deployment Component Store β€” browse or search the catalog when you want to deploy something new
  3. Context selector β€” switch environments to see resources in a different deployment stage

Next article

Getting Started

This guide walks through the first steps on Planton: creating an account, setting up an organization and environment, connecting a cloud provider, and deploying a cloud resource. By the end, you will have working infrastructure deployed to your own cloud account. A modern web browser An AWS, GCP, or Azure account with permissions to create resources Credentials for that account (access keys, service account key, or service principal) Navigate to planton.ai and click Login or Join Beta in the...
Read next article

Β©2026 Planton Cloud Inc. All Rights Reserved.