Testkube Runner Feature Comparison

The below table shows a feature comparison between deploying the Testkube Runner in Standalone Mode vs when it is connected to the Testkube Control Plane - Read More.

The Control Plane column applies to both On-Prem and Cloud deployments of the Control Plane.

In standalone mode, a single Runner provides execution, listener, and webhook behavior. The ❌ for the listener, GitOps, and webhooks rows means those capabilities are only available as separately deployed Runners when connected to the Control Plane.

Features	Testkube Runner in standalone mode	Testkube Runner(s) connected to Control Plane	Read More
TestWorkflows	✅ - ⚠️ see limitations above	✅	Docs
Test Logs/Artifacts	✅ - ⚠️ via CLI/API only	✅	Docs
Webhooks	✅	✅	Docs
Kubernetes Event Triggers	✅	✅	Docs
Test, Suites, Sources, Executors	✅	✅	Deprecated - Read More
Testkube CLI	✅	✅	Docs
REST API	✅ -⚠️ Unauthenticated	✅	Docs
Dashboard	❌	✅	Docs
Environment Management	❌	✅	Docs
Multi-runner Environments	❌	✅	Docs
Concurrency and Queuing	❌	✅	Docs
Listener capability	❌	✅	Docs
GitOps capability	❌	✅	Docs
Webhooks capability	❌	✅	Docs
Control Plane Resource Storage	❌	✅	Docs
SSO Integration	❌	✅	Docs
SCIM Integration	❌	✅	Docs
RBAC/User Mgmt	❌	✅	Docs
Resource Metrics	❌	✅	Docs
Reporting/Insights	❌	✅	Docs
Workflow Health & Flakiness	❌	✅	Docs
Status Pages	❌	✅	Docs
Advanced Log/Results Debugging	❌	✅	Docs
Teams	❌	✅	Docs
Resource Groups	❌	✅	Docs
JUnit Reports	❌	✅	Docs
Audit Logs	❌	✅	Docs
AI Agents	❌	✅	Docs
AI Assistant	❌	✅	Docs
MCP Server	❌	✅	Docs
Test Discovery	❌	✅	Docs