Testkube Agent Feature Comparison

The below table shows a feature comparison between deploying the Testkube Agent 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 agent provides runner, listener, and webhook behavior; the ❌ for Listener Agents, GitOps Agents, and Webhook Agents means that discrete capability-based agents are only available when connected to the Control Plane.

Features	Testkube Agent in standalone mode	Testkube Agent(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-Agent Environments	❌	✅	Docs
Concurrency and Queuing	❌	✅	Docs
Listener Agents	❌	✅	Docs
GitOps Agents	❌	✅	Docs
Webhook Agents	❌	✅	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