Server Configuration,
GitOps-Driven

Pull Base brings GitOps to your server configuration management. Keep your infrastructure consistent, track changes, and roll back instantly—all powered by Git.

GitOps-Driven

How Pull Base Works

Pull Base follows the GitOps pattern: define your desired state in Git, and let Pull Base handle the rest.

GitOps Workflow

How Pull Base delivers continuous configuration management

Define & Commit

Write server configurations as code and commit to Git

Controller Observes

Pull Base monitors changes and determines the target state

Agents Apply

Server agents pull and reconcile to match desired state

Continuous GitOps Cycle

How the GitOps Workflow Works

Define in Git: Define your server configurations in Git. Use YAML files to specify packages, services, and files.
Controller Monitors: Pull Base Controller monitors your Git repositories and updates the target state for each server.
Agents Pull & Apply: Agents pull the latest configuration and apply it to your servers, ensuring they match the desired state.

Simple Configuration

Define Your Infrastructure as Code

A simple YAML file is all you need to define your server configuration. Here's what a typical Pull Base configuration looks like:

server-config.yaml

# Pull Base Server Configuration
serverMetadata:
  name: web-server-01
  environment: production

packages:
  - name: nginx
    state: present
  - name: nodejs
    state: latest
  - name: apache2
    state: absent

services:
  - name: nginx
    enabled: true
    state: running
    managed: true
  - name: ufw
    enabled: true
    state: running
    managed: true

files:
  - path: /etc/nginx/sites-available/myapp.conf
    content: |
      server {
          listen 80;
          server_name myapp.example.com;
          
          location / {
              proxy_pass http://localhost:3000;
              proxy_set_header Host $host;
              proxy_set_header X-Real-IP $remote_addr;
          }
      }
    reloadService: nginx

system:
  serviceManager: systemd
  containerized: false

YAML

Line 42, Col 3

Learn more about Pull Base features

Why Pull Base?

Everything you need to manage server configurations

Pull Base brings the power of GitOps to your server configuration management, making it easy to track changes, maintain consistency, and roll back when needed.

Git-Driven Configuration: Define your server configurations in Git. Use YAML files to specify packages, services, and files.
Real-time Drift Detection: Pull Base continuously monitors your servers for configuration drift and automatically reconciles them.
Auto Reconciliation: Automatically detect and fix configuration drift, ensuring your servers always match their desired state.
Instant Rollback: Need to undo a change? Roll back to any previous commit with a single click.
Multi-Platform Support: Support for multiple package managers (apk, apt, yum) and service managers (systemd, supervisor, openrc).
Status History: Track configuration changes and server status over time with detailed history and audit trails.

And More: Discover more powerful features as Pull Base continues to evolve with additional capabilities coming soon.

How We Compare

Pull Base vs. Other Solutions

See how Pull Base stacks up against traditional configuration management tools

Pull Base

Architecture

GitOps / Pull-based
Configuration Source

Git (Any Provider)
Learning Curve

Low (Simple YAML)
Versioning/History

Built-in (Git-based)
Rollback Capability

One-click to any version
Drift Detection

Continuous & Automatic

Ansible

Architecture

Push-based
Configuration Source

YAML on Control Node
Learning Curve

High
Versioning/History

Manual
Rollback Capability

Manual
Drift Detection

Manual Check

Puppet/Chef

Architecture

Pull-based
Configuration Source

DSL on Master/Server
Learning Curve

High
Versioning/History

Limited
Rollback Capability

Complex
Drift Detection

Periodic

Feature

Architecture
Configuration Source
Learning Curve
Versioning/History
Rollback Capability
Drift Detection