Pterodactyl is back and keeps its MIT open source license
Pterodactyl is moving again in a big way: there’s new leadership, the project is alive, and most importantly… it’s not going closed and it’s not changing its open source nature.
If you run game servers, sell hosting, or maintain infrastructure with Wings, this is good news because the core message is simple: long-term stability and consistent maintenance.
What happened with Pterodactyl
In the official organization discussion, the team announced a leadership change: Infraly is now managing the project, with a focus on getting Pterodactyl “back in shape” through maintenance and continuity.
The thread even got temporarily locked due to spam, which tells you how much attention this announcement pulled in a short time.
Who Infraly is and why WISP is part of the conversation
In the same announcement, Infraly introduced itself as a company based in Allentown, Pennsylvania, operating since January 2020, and mentioned it currently maintains WISP, a well-known fork of Pterodactyl.
That naturally raised a common concern (and a fair one): “company involvement = monetization = bad changes?”. The official response was straightforward.
License and open source with zero drama
The most important promise is clear:
Pterodactyl will remain free and open source.
The MIT license is not changing.
Infraly also clarified that WISP is their paid alternative, and that direct funding around Pterodactyl would come from sponsorships to support contributors.
Dane (the original creator and long-time maintainer) reinforced the message from his side: he said he wouldn’t be coming back if he didn’t trust Infraly, and that projects at this scale are more sustainable with an organization behind them instead of a single person burning out.
What to expect in the short term
Spoiler: it’s not “Pterodactyl 2 with ray tracing tomorrow”. It’s the kind of work that’s not flashy… but actually fixes things:
Dane said they’re still working on a roadmap because there’s a lot of catching up to do, and plenty of maintenance tasks need to land before pushing hard on new features.
From the leadership side, the same idea repeats: cleanup, maintenance, and accepting contributions as the foundation stabilizes.
Human translation: changes are coming, yes — but first they’ll patch holes, untangle dependencies, improve testing, and make maintaining the project less of an extreme sport.
Why this matters even if you just want your panel not to blow up
Because with Pterodactyl (like any internet-facing panel), security and updates matter.
Real example: the repo has recent advisories, including one published on December 27, 2025 (XSS) and another critical one (RCE) published in 2025.
This isn’t fear-mongering — it’s just a reminder that “I installed it in 2022 and never touched it again” is basically a speedrun into trouble.
How to prepare for what’s coming
A practical checklist (no poetry):
Set up a staging environment (even a cloned VM) to test updates before touching production.
Monitor releases and advisories (GitHub + the official Discord).
Keep real backups: database +
/var/www/pterodactyl+ your webserver configuration.Keep Panel and Wings aligned by major/minor versions when it matters (it reduces weird edge-case issues).
Conclusion
Pterodactyl didn’t die, it didn’t go closed-source, and the MIT license stays. Infraly steps in to provide continuity, and Dane returns with the goal of making the project sustainable beyond the “single hero maintainer” model.
If you run production panels, the move is simple: expect more consistent updates, and keep your stack (Panel + Wings) up to date.
