GitLab
vs
Saltstack

Decision Kit

Decision Kit

Summary

SaltStack Platform is a Python-based open-source configuration management software and remote execution engine. Supporting the “Infrastructure as Code” approach to deployment and cloud management, the configuration management and orchestration tool enables system administrators to automate server provisioning and management tasks. The master-slave architecture of Salt permit it to work as both a push and a pull system.

GitLab is a complete DevOps platform, delivered as a single application that includes not only configuration management, but also capabilities for project management, source code management, CI/CD, and monitoring. GitLab is designed for Kubernetes and cloud native applications.

Resources

Feature Comparison
FEATURES

Cloud Native

GitLab and its CI/CD is Cloud Native, purpose built for the cloud model. GitLab can be easily deployed on Kubernetes and used to deploy your application to Kubernetes with support out of the box.

Kubernetes integration

Vulnerability Management

Empower your entire team, and not just Security, to act on security findings with a unified interface for scan results from all GitLab Security scanners.

Learn more about Vulnerability Management

Container Host Monitoring and Blocking

Monitor and optionally block malicious or unusual activity like process starts, file changes, or opened network ports in running containers.

Learn more about Container Host Monitoring and Blocking

Security Policies

Allow security teams to manage and enforce security policies for GitLab projects and for Kubernetes clusters.

Learn more about security policy management

License Compliance

Check that licenses of your dependencies are compatible with your application, and approve or deny them. Results are then shown in the Merge Request and in the Pipeline view.

Learn more about License Compliance

Configuration Modeling

CM modeling is the concept to consolidate the interactions between IT service assets, configuration items and infrastructure. Shows the interaction and relationship of services, infrastructure, and assets with each other, it will ease to find the root cause of an incident and problem.

Configuration Automation

Configure Management automation is used to make the server reach a desirable state, previously defined by provisioning scripts using a tool’s specific language and features ensuring that every system you’re responsible for is configured accurately and consistently.

Configure Monitoring

CM monitoring includes the process of recording and reporting configuration item descriptions (e.g., hardware, software, firmware, etc.) and all departures from the baseline during design and production. In the event of discovered problems, the verification of baseline configuration and approved modifications can be quickly determined.

Configure Governance

CM governance is a review that assesses compliance with established performance requirements, commercial and appropriate government standards, and functional, allocated, and product baselines. Configuration governance confirm that the system and subsystem configuration documentation complies with the functional and physical performance characteristics before acceptance into an architectural baseline.