slug: upsun provider: Upsun generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 16 edges: - tag: Environment spec_file: upsun-environment-api-openapi.yml capability_id: BC-4210.20 capability_id_l1: BC-4210 capability_name: Environment Management confidence: 0.9 evidence: POST /projects/{projectId}/environments/{environmentId}/branch branch-environment; POST .../deactivate deactivate-environment; POST .../merge merge-environment reason: Full lifecycle of ephemeral per-branch development and staging environments (activate, branch, pause, merge, redeploy) is provisioning and stewardship of non-production environments. - tag: Autoscaling spec_file: upsun-autoscaling-api-openapi.yml capability_id: BC-4220.50 capability_id_l1: BC-4220 capability_name: Capacity & Performance Management confidence: 0.85 evidence: GET /projects/{projectId}/environments/{environmentId}/autoscaling/settings get-autoscaler-settings Retrieves Autoscaler settings, schemas AutoscalerCPUPressureTrigger, AutoscalerScalingCooldown reason: Operations configure auto-scaling triggers, cooldowns and instance bounds for running services — squarely auto-scaling policy within capacity and performance management of the platform. - tag: Environment Variables spec_file: upsun-environment-variables-api-openapi.yml capability_id: BC-4210.60 capability_id_l1: BC-4210 capability_name: Configuration & Secrets Management confidence: 0.85 evidence: POST .../environments/{environmentId}/variables 'Add an environment variable'; schemas EnvironmentVariable, EnvironmentVariablePatch reason: CRUD over runtime configuration values consumed by deployed application services — directly configuration (and secrets) management for releases. - tag: Invoices spec_file: upsun-invoices-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.85 evidence: GET /organizations/{organization_id}/invoices 'List invoices'; schemas Invoice, InvoicePDF reason: Customer-facing invoice retrieval and PDF statements for the vendor's usage-based subscription billing, matching invoicing & statement management. - tag: MFA spec_file: upsun-mfa-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.85 evidence: '''Confirm TOTP enrollment''; ''Enable organization MFA enforcement''; schema OrganizationMFAEnforcement' reason: TOTP enrollment, recovery codes and organization-wide MFA enforcement are authentication/identity and access controls. - tag: Subscriptions spec_file: upsun-subscriptions-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.85 evidence: POST /organizations/{organization_id}/subscriptions create-org-subscription Create subscription; GET .../estimate Estimate the price of a subscription; GET .../current_usage Get current usage for a subscription reason: 'Plainly the commercial subscription surface of a SaaS/PaaS: create, update, price-estimate, plan (ProjectPlan), addons and usage alerts. L1 Subscription Lifecycle Management is clear; the operations straddle provisioning, modification and usage/estimation so no single L2 is named.' - tag: Support spec_file: upsun-support-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.85 evidence: POST /tickets create-ticket Create a new support ticket; GET /tickets/priority List support ticket priorities reason: Creation and update of customer support tickets with priorities and categories — inbound customer contact capture and routing. Unambiguous customer service surface. - tag: User Access spec_file: upsun-user-access-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.85 evidence: POST /projects/{project_id}/user-access grant-project-user-access Grant user access to a project; schemas ProjectPermissions, UserProjectAccess reason: Grant, update and revoke of per-user project permissions is squarely access management; the ProjectPermissions schema confirms authorisation semantics rather than any business-domain meaning. - tag: Team Access spec_file: upsun-team-access-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /projects/{project_id}/team-access grant-project-team-access Grant team access to a project; DELETE /teams/{team_id}/project-access/{project_id} Remove project access for a team reason: Granting and revoking team entitlements to projects is authorisation administration — Identity & Access Management. Some chance it would be filed as tenant/platform access control instead, hence 0.8. - tag: Tickets spec_file: upsun-tickets-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.8 evidence: GET /tickets list-tickets List support tickets reason: Read side of the support ticket store ('List support tickets', schema Ticket) — customer inquiry handling. Single read operation, so slightly below the Support tag's confidence. - tag: Project Variables spec_file: upsun-project-variables-api-openapi.yml capability_id: BC-4210.60 capability_id_l1: BC-4210 capability_name: Configuration & Secrets Management confidence: 0.78 evidence: POST /projects/{projectId}/variables create-projects-variables Add a project variable reason: CRUD over project variables (environment/config values consumed by deployed applications) maps to management of runtime configuration and secrets for product services. - tag: Deployment spec_file: upsun-deployment-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.75 evidence: GET /projects/{projectId}/environments/{environmentId}/deployments list-projects-environments-deployments Get an environment's deployment information reason: Exposes deployment records for an environment including routes (UpstreamRoute, RedirectRoute, ProxyRoute), i.e. the delivery of software changes to a running environment. Read-only, so slightly below top confidence. - tag: Repository spec_file: upsun-repository-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.75 evidence: GET /projects/{projectId}/git/commits/{repositoryCommitId} get-projects-git-commits Get a commit object reason: Git blob, commit, tree and ref access is source-control interrogation, which falls under software construction (source control) practice. - tag: Deployment Target spec_file: upsun-deployment-target-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.7 evidence: POST /projects/{projectId}/deployments create-projects-deployments Create a project deployment target reason: Creates and updates deployment target configurations (Dedicated/Enterprise/Foundation) that determine where and how a project is deployed — deployment orchestration configuration rather than a business capability. - tag: Environment Backups spec_file: upsun-environment-backups-api-openapi.yml capability_id: BC-4220.60 capability_id_l1: BC-4220 capability_name: Disaster Recovery & Resilience confidence: 0.7 evidence: POST .../backup 'Create backup of environment'; POST .../backups/{backupId}/restore 'Restore an environment snapshot'; schemas Backup, EnvironmentRestoreInput reason: Operations create, list, delete and restore environment backups/snapshots, which is backup-and-restore resilience operations for the hosted service. Some ambiguity with per-tenant export/restore, hence 0.7. - tag: Records spec_file: upsun-records-api-openapi.yml capability_id: BC-4250.10 capability_id_l1: BC-4250 capability_name: Usage Metering confidence: 0.7 evidence: GET /organizations/{organization_id}/records/usage list-org-usage-records List usage records reason: Usage and plan records per organization on a usage-priced platform are the metered consumption feed underpinning rating and billing analytics; schemas Usage, PlanRecords support this.