This is the full list of repositories in the ARGLabs Bitbucket workspace, organized by project. This post is updated as new repositories are published.
ARGLabs is Being Rewritten Again
After years of iterating on the same foundation, ARGLabs is getting a full rewrite and this time, AI is at the center of it.
With the advancements in AI tooling, I can now move faster, build smarter, and dedicate more focused time to what actually matters: shipping meaningful infrastructure work. The old repositories have been archived under a legacy project, nothing is lost, but everything going forward will be net-new.
The way accounts, teams, and workflows are structured will also evolve to better fit this AI-augmented world. Less friction, more signal. Automation that used to take days of setup will be handled in minutes, freeing up time for higher-level architectural decisions and real problem solving.
This also means the projects themselves will change in nature. Expect more composable modules, cleaner interfaces, and infrastructure that is genuinely designed for teams working alongside AI agents, not just humans.
Stay tuned, new repositories are coming soon.
Cloud as an Operating System
My view of the cloud is fundamentally different from most people around me. They see it as an opportunity to build better infrastructure. I don’t. I see the cloud as the operating system that will run services and applications for me.
ECS or EKS: Native cloud containers or kubernetes ?
There’s a lot of articles comparing the two and telling you about their differences and when you should go with one or another. I’ll make it slightly different.
I’ll tell you what I want to accomplish considering technology, culture, operations, costs, support and compliance and what is my choice to do so.
I want to provide developer teams a platform so they can easily build, deploy and run their apps in compliance with the Cloud Engineering Team’s best practices and Security Team’s policies.
Speedup cloud usage, cloud services details abstraction, best practices and security policies enforced, costs and permissions controlled with no bureaucracy and 100% cloud provider support.
ARGLabs fictitious company
So you are a newcomer on our company. Congratulations !
Our DevOps culture
We like the DevOps “You build it, you run it.” culture.
It means that our Cloud Engineers (call them DevOps, SRE, infrastructure guys or whatever you want), will help you with the basic cloud infrastructure on which your applications will run, but they won’t be called to solve your apps problems and incidents, so please, take the ownership of everything you bring up on the cloud, including costs, incidents etc.
Cloud Engineers can always help you with architecture decisions and deployment pipelines, but once it’s running, it’s up to you to keep things up.
Why a .church domain ?
Because churches are places of faith.
I love IaC. I really do IaC. I think I understood what we can really do with IaC.
But I’ve seen many “good practices” out there that I thought aren’t good enough, many written by famous people and others even by the tool suppliers themselves.
In fact, everyone can write and publish anything and call it a “best practice”, and in fact, it could be for them, for many reasons. Good practice is what works best for your way of working.
ARGLabs is my church because this is where I’m going to show what I believe are best practices for the work I do.
In ARGLabs Church, I am the law (as Rodrigo Goes says 🙂 ).
These are not intended to be best practices for everyone.
What is ARGLabs ?
Take ARGLabs as a fictional company where we’ll be running some applications like a real company
And with “real company” we mean that we’ll bring up everything needed to run our applications.
Every tech company “just” need to “run their applications”. By design, no specific tools are needed as long as the chosen tools meet the applications needs. With that in mind, we’ll choose the simplest tools and only those which allow us to configure them as code.
So what makes ARGLabs worth it, and why you would read more about it ?
Our tech design principle is: “If it can’t be done as code, it cannot be done.”
With that, many other benefits come along:
- Knowledge is written down in code and no more in anyones head.
- Disaster recovery or any number of dev/testing environment is just a matter of cost, but without managing effort.
And countless benefits more. Majority of them already included by the above mentioned (please don’t ask me to tell you every single benefit. If you can’t see them, maybe you should ask you tech staff after reaching us)
We’ll use many tools (where a free account could meet our needs) that a real company would use.
We’ll try to have every tech stuff a modern company usually have:
- Public and private applications
- Deployment pipelines, CI/CD
- Monitoring tools and metrics
- Incident Management
- Communication platform and integrations
ARGLabs 