slug: dokploy provider: Dokploy 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: 21 edges: - tag: server spec_file: dokploy-server-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.85 evidence: POST /server.create, POST /server.setup, GET /server.buildServers, GET /server.withSSHKey, POST /server.setupMonitoring reason: Registers, provisions, validates and monitors the physical/virtual servers that host deployments — squarely compute/cloud infrastructure management. - tag: customRole spec_file: dokploy-customrole-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.82 evidence: POST /customRole.create, GET /customRole.membersByRole, GET /customRole.getStatements reason: Role definitions, role membership and permission statements are role-based access control administration, i.e. identity & access management. - tag: deployment spec_file: dokploy-deployment-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.82 evidence: GET /deployment.all, GET /deployment.queueList, POST /deployment.killProcess, GET /deployment.readLogs reason: Operations list, queue, kill and read logs of deployments of applications to servers — deployment orchestration on a PaaS. - tag: application spec_file: dokploy-application-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.8 evidence: POST /application.redeploy; POST /application.start; POST /application.stop; POST /application.saveEnvironment; POST /application.saveGithubProvider reason: Core PaaS surface that creates, starts/stops and redeploys applications from Git providers with environment configuration — deployment orchestration of software to running infrastructure. - tag: backup spec_file: dokploy-backup-api-openapi.yml capability_id: BC-4220.60 capability_id_l1: BC-4220 capability_name: Disaster Recovery & Resilience confidence: 0.8 evidence: POST /backup.manualBackupPostgres; POST /backup.manualBackupMongo; GET /backup.listBackupFiles reason: Scheduled and manual database/webserver backup creation and backup-file listing — backup and restore operations for the running platform. - tag: sso spec_file: dokploy-sso-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: GET /sso.listProviders, POST /sso.register, GET /sso.showSignInWithSSO, POST /sso.addTrustedOrigin reason: Registration and management of single-sign-on identity providers and trusted origins for the platform's own admin login — identity federation, i.e. Identity & Access Management. - tag: docker spec_file: dokploy-docker-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.78 evidence: GET /docker.getContainers, POST /docker.restartContainer, POST /docker.stopContainer, POST /docker.removeContainer reason: Direct lifecycle control of Docker containers on servers is compute/container infrastructure operations, not a business function. - tag: cluster spec_file: dokploy-cluster-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.75 evidence: GET /cluster.getNodes; POST /cluster.removeWorker; GET /cluster.addManager reason: Docker Swarm node management — adding and removing worker/manager nodes is compute infrastructure management for the self-hosted platform. - tag: compose spec_file: dokploy-compose-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.75 evidence: POST /compose.create, POST /compose.saveEnvironment, POST /compose.killBuild, GET /compose.loadServices — deploying Docker Compose stacks reason: Operations create, update, build and deploy Docker Compose application stacks on a self-hosted PaaS — deployment orchestration of software changes to running infrastructure. Alternative reading is IT Infrastructure Management, hence moderate confidence on the sub-capability. - tag: libsql spec_file: dokploy-libsql-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.75 evidence: POST /libsql.create, POST /libsql.start, POST /libsql.stop, POST /libsql.deploy, POST /libsql.saveExternalPorts reason: Provisioning and lifecycle control of a managed libSQL database service instance — database/compute infrastructure management, not a business capability. - tag: redis spec_file: dokploy-redis-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.75 evidence: POST /redis.create, POST /redis.deploy, POST /redis.start, POST /redis.stop, POST /redis.changePassword — vendor "deploys applications, Docker Compose stacks, and managed databases" reason: Operations provision and operate managed Redis datastore instances (create/deploy/start/stop/env), i.e. compute and data infrastructure provisioning — IT Infrastructure Management. - tag: environment spec_file: dokploy-environment-api-openapi.yml capability_id: BC-4210.20 capability_id_l1: BC-4210 capability_name: Environment Management confidence: 0.72 evidence: POST /environment.create, GET /environment.byProjectId, POST /environment.duplicate reason: Environments belonging to projects are created, duplicated and removed — provisioning and stewardship of deployment environments. Some risk this means environment variables, but byProjectId/duplicate indicates environment objects. - tag: previewDeployment spec_file: dokploy-previewdeployment-api-openapi.yml capability_id: BC-4210.20 capability_id_l1: BC-4210 capability_name: Environment Management confidence: 0.72 evidence: GET /previewDeployment.all, POST /previewDeployment.redeploy, POST /previewDeployment.delete reason: Preview deployments are ephemeral non-production environments spun up per branch/PR and torn down again; listing, redeploying and deleting them is stewardship of pre-production environments. Deployment Orchestration is a plausible alternative reading, hence not higher. - tag: domain spec_file: dokploy-domain-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.7 evidence: POST /domain.generateDomain, GET /domain.canGenerateTraefikMeDomains, POST /domain.validateDomain reason: Assigning and validating hostnames/domains routed by Traefik for deployed apps is network/infrastructure configuration. Generic enough that only L2 infrastructure is a reasonable fit. - tag: mariadb spec_file: dokploy-mariadb-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.7 evidence: POST /mariadb.create, POST /mariadb.start, POST /mariadb.stop, POST /mariadb.deploy, POST /mariadb.saveExternalPort reason: The tag manages the lifecycle of a managed MariaDB database service on the PaaS (create, deploy, start/stop, external port, environment, password), which is provisioning and operating data infrastructure rather than any business-domain function. IT Infrastructure Management is the honest cross-industry fit for a devtool/PaaS. - tag: mongo spec_file: dokploy-mongo-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.7 evidence: POST /mongo.create, POST /mongo.deploy, POST /mongo.start, POST /mongo.stop, POST /mongo.changePassword reason: 'Same surface as the other database tags: lifecycle and runtime control of a managed MongoDB instance deployed by the PaaS — compute/storage infrastructure provisioning and operation, not a business capability of the buyer''s domain.' - tag: mysql spec_file: dokploy-mysql-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.7 evidence: POST /mysql.create, POST /mysql.deploy, POST /mysql.saveExternalPort, POST /mysql.changeStatus reason: Managed MySQL service lifecycle on the PaaS — create, deploy, start/stop, reload, credentials. This realises provisioning and operation of data infrastructure, not a domain business capability. - tag: postgres spec_file: dokploy-postgres-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.7 evidence: POST /postgres.create, POST /postgres.deploy, POST /postgres.start, POST /postgres.saveEnvironment reason: Lifecycle management of a managed PostgreSQL database service deployed by the PaaS (create, deploy, start/stop, environment, credentials) — provisioning and running data infrastructure. - tag: rollback spec_file: dokploy-rollback-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.7 evidence: POST /rollback.rollback, POST /rollback.delete reason: Reverting a deployed application to a previous deployment is a production deployment-control action, matching Deployment Orchestration (delivering changes to production safely with controlled blast radius). Thin surface, hence moderate confidence. - tag: settings spec_file: dokploy-settings-api-openapi.yml capability_id: BC-600.40 capability_id_l1: BC-600 capability_name: IT Operations Management confidence: 0.7 evidence: POST /settings.reloadServer, POST /settings.cleanUnusedImages, POST /settings.cleanStoppedContainers, POST /settings.cleanDockerPrune, POST /settings.reloadTraefik reason: Housekeeping and runtime maintenance actions on the host and Docker daemon (prune, reload, clean queues) — day-to-day IT operations and automation rather than any business capability. - tag: stripe spec_file: dokploy-stripe-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.7 evidence: GET /stripe.getCurrentPlan, POST /stripe.upgradeSubscription, GET /stripe.getInvoices, GET /stripe.canCreateMoreServers reason: 'Commercial subscription surface for the hosted offering: plan retrieval, checkout, subscription upgrade, seat/server entitlement check and invoice listing. Spans plan/entitlement, modification and invoicing, so L1 Subscription Lifecycle Management only.'