I recently went through a large Infrastructure as Code migration. If you have ever done one, you know you spend a massive amount of time just trying to understand what already exists. I needed to navigate existing resources, find abandoned orphans, compare tags, and check how different resources related to each other.
Doing this in the Azure Portal was just too slow and inefficient. I tried exporting everything to CSV and Excel, but that felt too complex and the visual design was terrible. The Azure CLI is really nice, but it requires you to write and remember complex queries just to find simple answers.
I needed something better. I really like tools that stay out of your way and just work fast, drawing inspiration from tools like Radar and k9s. So, I decided to build something specifically for my own personal use. I used Claude Code and started putting together a solution to solve my exact problems.
That is how azure-lupa was born. It helped me so much during the migration that I decided to make it public and open source.
It is definitely not a replacement for the Azure Portal. It is simply a fast, local, and lightweight tool to help you see what you have in Azure.
How it works
The secret to its speed is how it handles data. It pulls your selected scope just once using Azure Resource Graph. Then, it loads that data straight into a DuckDB database running right inside your browser. Because the data sits locally, filtering and sorting are instant.
There is absolutely zero setup. You do not need to create app registrations. It simply uses your existing Azure CLI login and runs securely on your local machine. It never writes back to Azure.
A few things you can do
Spot orphaned resources: The tool automatically flags abandoned items like unattached disks or empty App Service plans to help you clean up.
Combine your views: You can hold down the Control or Command key and click multiple subscriptions to see all of their resources in one single screen.
See the full picture: Click on any resource to see its raw JSON, tags, and related parent or child resources.
If you manage a lot of Azure subscriptions, I think you might find it useful too.
You can check out the source code and try it yourself right here:
Let me know what you think in the comments.
Top comments (0)