Configuration management

Servers configured the same way, every time, from code

Servers that are configured by hand slowly drift apart until no two behave the same. DoneDeploy describes your server configuration in Ansible or Puppet, with AI helping turn existing setups into code and review each change. You get servers that can be rebuilt, patched and audited from one place.

Talk to an engineer »How it works
  • Fixed price
  • Free first call
  • In your own cloud
How we work

From design to implementation, and everything after

Designthe service, its architecture and costs
Buildinfrastructure and code, reviewed
Rundeployed, secured and watched
Automatepipelines, runbooks and AI
Improvecost, 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

AnsiblePuppetLinuxVaultPackerNGINX
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.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.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.
Related services

Often done together

Infrastructure as codeEvery server, network and permission defined in code you ownLearn more »CI/CD and GitOpsReleases that are routine, reviewed and easy to roll backLearn more »After launchInfrastructure that keeps getting cheaper, faster and safer after launchLearn more »
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 »