CTFreak vs Control-M
How does CTFreak compare to Control-M by BMC Software? Here is a feature-by-feature comparison.
| CTFreak | Control-M | |
|---|---|---|
| Deployment | ||
| Self-hosted / on-premise | Yes | Yes |
| No external runtime | Yes
Single Go binary.
|
No
Requires a Java runtime.
|
| Docker install | Yes
2GB RAM minimum recommended.
|
No |
| Linux install | Yes
1GB RAM minimum recommended.
|
Yes
24GB RAM minimum recommended.
|
| Windows install | Yes
4GB RAM minimum recommended.
|
Yes
24GB RAM minimum recommended.
|
| Offline license | Yes
Requires Sovereign Edition.
|
Yes |
| Remote execution | ||
| Agentless mode | Yes | No |
| SSH remote protocol | Yes | Yes
Requires an agent to broker the SSH connection.
|
| WinRM remote protocol | Yes | No
Uses WMI, not WinRM, to reach agentless Windows nodes.
|
| Concurrent multi-node fan-out | Yes
A Task can target a set of Nodes, executed concurrently.
|
Yes
Uses Host Group option.
|
| Concurrent multi-database fan-out | Yes
A Task can target a set of Databases, executed concurrently.
|
No |
| Scheduling | ||
| Business calendar support | Yes | Yes |
| iCal calendar sync | Yes | No |
| Per-task timezone scheduling | Yes | Yes |
| Orchestration | ||
| Task workflows | Yes | Yes |
| Identity & access | ||
| OpenID Connect | Yes | Partial
Requires the separate BMC Helix Single Sign-On (RSSO) add-on as broker.
|
| SAML | No | Yes |
| LDAP | No | Yes |
| Role-based access control | Yes | Yes |
| Multiple simultaneous SSO providers | Yes | No |
| Security | ||
| Encrypted secret storage | Yes | Yes |
| Encryption key rotation | Yes | Yes |
| Integration and extensibility | ||
| REST API | Yes | Yes |
| OpenAPI specification | Yes | Yes |
| Incoming webhook trigger | Yes | No |
| User interface | ||
| Responsive web UI | Yes | No |
| Pricing | ||
| Free edition | Yes | No |
| Open source edition | No | No |
| Public pricing | Yes | No |
| Self-service online purchase | Yes | No |
Last reviewed: