Resource inventory (A-Z)
Flat checklist of product objects and capabilities you may have permission to use. Exact UI labels vary by deployment. For file-level diligence, use your account team under NDA (see Technical verification).
Domain guides: Object storage - Load balancing - DNS - Billing - Agent platform - Integrations - Scaling groups - K8s API proxy.
Account (personal)
- Profile, password, 2FA, WebAuthn
- Account API keys (automation as user)
- Login / recovery
Organization
- Organization profile & status visibility
- Projects (list, create, open)
- Memberships & invites
- Roles (custom RBAC)
- Authentication providers (IdP for Loopback login)
- Payment methods
- Invoices & cost summaries
- Domains
- DNS records & DNS record zones (org scope)
- Network bridges between org-local networks
- Monitoring sources
- Notification channels
- Bundles: repositories, bundles, environments, manifests, cluster resources, revisions, deployments, operations (build/deploy/discover)
- GitHub / GitLab OAuth setup for bundles
Project
- Project metadata & billing hints
- Object storage (buckets, credentials, policies) - v2/v3 API families
- Load balancers, targets, services (project scope)
- DNS zones (project scope)
- Monitoring objects, conditions, states, alerts
- Bundle environments / revisions (project-scoped navigation helpers)
Networking (organization + workspace)
- Networks: WireGuard overlays scoped to organization or workspace (and legacy system-class cases in some deployments); managed workspace overlays are created on workspace create when managed networking is enabled for that template
- IPv4 overlay addressing is allocated from a shared private carrier-grade NAT-style space (automation); IPv6 overlays are not offered on the default path today
- Network bridges (organization scope) pair two networks so both meshes can communicate
- Host-level mesh refresh re-applies WireGuard configuration across the relevant organization and workspace networks (used after membership changes or agent drift; ties into WGLB where enabled)
Workspace
- Workspace CRUD & metadata
- Kubernetes workspace: version, upgrade list, upgrade trigger
- Kubeconfig (admin) & OIDC kubeconfig & OIDC settings
- Kubernetes API proxy: cluster summary, nodes, ingress, LB services, Helm releases, volumes, cordon/uncordon/drain
- Kubernetes events & deployments listings
- Kubernetes secrets (product workflows) - permission gated
- Maintenance schedule & toggles (OS + Kubernetes patches)
- Transfer workspace to another project
- Compute profiles listing (with pricing overrides)
- Hosts (list paginated, create, lifecycle ops)
- Host: power, firewall attach/detach (layered with org/workspace firewalls), LB fabric hooks (WGLB re-apply, LBFW metrics where enabled)
- Scaling groups
- Agent tokens (mint/list/revoke)
- Shell sessions to hosts
- Firewalls & firewall rules (workspace - may be environment gated)
- Load balancers, targets, services (workspace scope)
- DNS zones (workspace scope)
- Workspace API key (used by platform integrations; not kubectl)
Platform software catalog
- Kubernetes applications (operator/admin - catalog CRUD & revisions)
- Customer consumption of catalog via cluster state (see workspace provisioning doc)
Cross-cutting
- Agents: install script download, binary updates (system routes)
- Monitoring parameters registry (system)
- Ecosystems / service providers / compute providers (often operator-tuned; some org routes)
Explicitly operator / system (typically not tenant)
- Organization admin, internal billing engines, render manifests, build credentials, deployment status internals, POC health aggregates