A modern, open replacement for Pterodactyl — built in the open

Building in public, coordinating in private

As an open-source Pterodactyl alternative, struxa’s users and contributors expect to see where the project is headed. But planning happened in scattered GitHub issues and Discord messages — nothing gave outsiders, or new contributors, a real view of what was coming next.

Two products, one team

The panel, the Wings agent and the storefront all move at once — plus a managed Struxa Cloud in the works. Without a shared task view, it was easy to lose track of which piece a given fix or feature actually belonged to.

Feature requests with nowhere to land

Operators asked for things — a Pterodactyl migration path, new plan and checkout options, node-agent improvements — and those requests either turned into GitHub issues that stalled or got lost in Discord entirely.

A public roadmap, not just a changelog

struxa’s board in Elean doubles as their public roadmap — anyone can see what is planned, in progress or shipped, without asking in Discord.

One backlog across panel, agent and storefront

Every task — a Wings agent fix, a new storefront plan, a panel UI change — lives in the same place, tagged by which part of the stack it touches.

Requests become tracked work

Migration-from-Pterodactyl asks, plan and checkout requests, node monitoring improvements — instead of getting buried, they become cards with real status.

Contributors know what’s next

Anyone looking to contribute can see open, prioritized work instead of guessing what is welcome.

Fewer "is this still happening?" questions

The roadmap answers it before it is asked — for Struxa Cloud’s waitlist, for the migration guide, for everything in between.

Trust that comes from visibility

For an open-source project asking people to self-host their infrastructure on it, showing the work builds more confidence than a polished landing page alone.