# Configuration Management

URL: https://donedeploy.com/devops-services/configuration-management/

ansible · fleet

✓

**Inventory**128 hosts in 6 groups

done

✓

**Playbook dry run**4 changes expected

checked

**Applying baseline**patches, users, sshd

running

**Hosts out of policy**2, fixed on this run

2

Hosts compliant**98.4%**

*✓*

**Same every time**from code

*⟳*

**Nightly check**drift reported

How we work

## From design to implementation, and everything after

**Design**the service, its architecture and costs

**Build**infrastructure and code, reviewed

**Run**deployed, secured and watched

**Automate**pipelines, runbooks and AI

**Improve**cost, speed and reliability, every month

The problem

## What goes wrong without it

1

### Snowflake servers

Each server was set up slightly differently, so fixes on one do not work on another.

2

### Patching put off

Updating operating systems and packages is manual and risky, so it is delayed.

3

### No audit trail

When a setting changes, nobody can tell when, why or by whom.

### What we do

- Write Ansible playbooks and roles, or Puppet modules where you already use Puppet
- Use AI to read existing servers and scripts and draft the matching configuration code
- Have AI review changes for unsafe settings before an engineer approves the rollout
- Automate operating system patching and hardening on Linux
- Manage secrets with Vault rather than files on servers
- Run configuration from a pipeline so changes are logged and repeatable

### What you get

- Playbooks, roles or modules in your Git repositories
- An inventory of servers and their roles
- A patching and hardening process
- Runbooks for rebuilding a server from code

How it works

## From first call to continuous improvement

### Free first consultation

We learn how many servers you run, what is on them and how they are maintained.

### Inventory

With AI reading the servers and scripts, we list what is configured where and what differs.

### Fixed-price proposal

We agree which servers and settings come under code first, at a fixed price.

### Codify and roll out

Engineers write and test the configuration and roll it out in stages.

### Improve after launch

We keep patching, hardening and the code itself up to date.

Technologies

## What we use

[!Ansible](https://donedeploy.com/technologies/ansible/)[!Puppet](https://donedeploy.com/technologies/puppet/)[!Linux](https://donedeploy.com/technologies/linux/)[!Vault](https://donedeploy.com/technologies/vault/)[!Packer](https://donedeploy.com/technologies/packer/)[!NGINX](https://donedeploy.com/technologies/nginx/)

From the blog

## Related articles

[!AI · November 11, 2026From Idea to AI Feature in Six WeeksHow an AI project runs end to end in six weeks: discovery, design, prototype, infrastructure, rollout, then measuring and improving.](https://donedeploy.com/ai-feature-in-six-weeks/)[!AI · October 15, 2026Automating Business Workflows with AI, SafelyWhere AI fits in business process automation, and how human review, guardrails and audit trails keep automated workflows safe.](https://donedeploy.com/ai-workflow-automation/)[!AI · September 16, 2026RAG in Production: The Boring Parts That MatterIngestion, chunking, refresh, evaluation and access control: the unglamorous work that decides whether a RAG system can be trusted.](https://donedeploy.com/rag-in-production/)

Related services

## Often done together

[**Infrastructure as code**Every server, network and permission defined in code you own*Learn more »*](https://donedeploy.com/devops-services/infrastructure-provisioning/)[**CI/CD and GitOps**Releases that are routine, reviewed and easy to roll back*Learn more »*](https://donedeploy.com/devops-services/ci-cd/)[**After launch**Infrastructure that keeps getting cheaper, faster and safer after launch*Learn more »*](https://donedeploy.com/devops-services/continuous-improvement/)

Questions

## Frequently asked

Ansible or Puppet?

For most new setups we use Ansible because it needs no agent on the servers. If you already run Puppet, we work with it.

Do we still need this with containers?

Often yes: the hosts, build agents and any servers outside a cluster still need consistent configuration.

Will changes interrupt our servers?

Changes are tested first and rolled out in stages, and anything that needs a restart is scheduled with you.

Tell us what you run and what you want to change. We reply personally, and the first consultation is free.

[Let's talk »](https://donedeploy.com/lets-talk/)