I have been “building” (read vibe coding, yes) a self hosted replacement for the string of websites and services I use to manage decks, deck building, arena collection management, and get play metrics and metagame information.
It’s not exactly perfect. It runs on glpi, as a plugin, with my thinking being that GLPI is already made to handle IT, assets, workflow, and a complicated relational database, and distill it into a format the user can make use of. It runs a postgres database for glpi and all the assets, a little web server for the user, and some runner services. It scrapes the card database from scryfall with metadata, grabsbinfo from mtgwiki and a few other resources, leaving you with an up to date working system right out of the gate.
The glpi instance then provides a keyed shipper that installs on the same PC where you’re running arena. Its just a timed script that reads arenas debug logs and sends them to the glpi instance. All in all it requires very little resources to run, since the db just needs a few hundred MB for images, and there’s no real processing being done.
The end goal is a local web service you can log into, and click thru a MTG web interface with everything you’d expect out there on the web.
Its proved beneficial for me already in replacing the other online tools I was using, and provides the same data. I get a detailed log of all my games played of arena on desktop, and a central and much easier to use deck building interface, that includes more a more natural workspace.
I’m always worried I’m high on my own supply, however, and I’m reticent to put it out there, because I often think dumb ideas are good. That said, I’d love to offer what I have if anyone wants to check it out, to use, or just to help or critique it. I’m not a developer, just trying to make a cool tool I’d want to use, and I feel like its working.
One thing I wanted and built out for my own deck building, was quickly sending a deck into a play test, which is done by actually running the forge engine in the background (can be disabled), and then interfacing with it inside the instance. The result is that you can quickly start a full mechanics game against a not in one second, that let’s you goldfish thru the deck, etc, but all embedded right in the user interface.
The back and forth between tweaking things, and pushing to a “real” turn 3 or whatever, is a lot faster like this.

