Market Atlas started because I was tired of opening several websites to understand one company. One page had a good price chart, another had the basic company numbers, and somewhere else I would look for financial statements or the latest reported quarter. None of that was impossible to find. It just never felt connected.
I wanted to type a ticker once and keep following my curiosity. What happened to the price? How large is the company? Is revenue growing? What did the last few years look like? The first version was only a chart, but every useful answer created the next obvious feature.
The fun part was not only the interface
I enjoyed building the page, but the project also pulled me further into company data. A number is not very useful until you know its period, source, units, and whether it is actually available. Earnings and annual statements do not arrive on the same schedule as a price update. Missing information should stay missing instead of quietly turning into zero.
Those details changed how I read the companies themselves. Building the software forced me to look more carefully at what each figure means and how one period compares with another.
A project earns its place when you keep using it
Market Atlas now runs from my own server and I still open it in everyday research. That matters to me more than adding features for the sake of a longer list. When something feels slow, unclear, or missing, I notice it as a user first and can improve it as the developer afterward.
It is limited mostly to the U.S. companies I follow, and that is fine for now. I would rather have a smaller tool I trust and enjoy using than a huge catalogue with shallow or confusing data. The project can grow from real needs as I find them.