I built it to get my time back.

I have done infrastructure work since I was a teenager. Servers, networks, clusters, and all the small work that keeps them healthy.

Over those years, my knowledge grew. I learned more tools, more best practices, and more about security and safety. My time went the other way. My responsibilities grew, and they became more diverse. Then came a family, with priorities that matter more than any infrastructure.

The drive never went away. I still want infrastructure that is current, documented, reliable and secure. I still want to keep the technical promises I make. But the hours to do that work were gone. So the infrastructure slowly fell behind. Upgrades waited. Setups that only I understood stayed undocumented. The rot set in.

The assistant does the boring part

I used the time I have to build GitOps Assistant to do that work. It does the boring part that takes most of my time: it finds the problem, reads the changelogs, gathers the metrics, writes the change and tests it. I do the part that needs me: I review, I decide, I merge.

It works. The infrastructure I was managing was years out of date, full of complex setups that nobody had written down. With the assistant, I brought it to a state I am proud of.

Time is what it gives back

There must be thousands of engineers like me. They know exactly what their infrastructure needs, and they do not have the time to do it. There are also many companies that do not know what their infrastructure needs, because nobody has the time to look.

Time is the most valuable thing we have. That is what GitOps Assistant gives back: to engineers, to the teams they work in, and to the people who wait for them at home.

Ruben de SmetFounder, GitOps Assistant