One home for internal tools
As a business grows, its tools tend to pile up one at a time, each with its own login. A private hub gives staff one place to start, one sign-in for the tools that share it, and one list of who can use what. It suits any business whose staff move between several separate systems.
Tools Python · Flask · PostgreSQL · AWS · Claude
Built for AngelFire Ammunition
A Kansas ammunition manufacturer in Saint Marys.
The problem
The company's internal tools had grown up one at a time, each with its own sign-in: five separate logins before this work. Staff had to know which tool lived where, and some work, such as dealer applications and issue reports, had no screen at all.
What I did
I built one private hub that links the company's internal apps, with a single login shared across several of them. I added screens for the work that had none, and one list of people for the tools on the shared login, so access to those is given or removed in one place.
The result
There is one place to start, and less time goes into hunting for the right tool. New staff are set up faster, work that used to live in email is now tracked, and every change to who can use the shared login is recorded.
Try it Demo data
The hub's own launcher, rendered from its templates with invented data. Each tile opens that tool's entry on this site.
Interactive samples use invented data, including invented names and prices. Pictures of the samples show the same invented data. Prices in screenshots of shipped marketing are already public.