Frequently Asked Questions
Here are some of the most asked questions that were asked in our Q&A stage on 4/12/2024, and our answers.
Last Updated: 2024-08-30
The Beta is now available! Head over to the Install docs and try out Pelican yourself.
- Panel
- Wings
- Licensing
- Project
What makes Pelican different to Pterodactyl?
We have a dedicated Comparison page where you can see differences and planned features.
Will my Eggs still be compatible?
Yes! We have a newer version of them planned, but the original ones will always work.
How can I migrate to Pelican?
You'll receive an easy guide to migrate from Pterodactyl to Pelican. It will be at least as easy as upgrading was originally.
Are automatic updates planned?
Yes. And easier manual updates too.
Can I use the original API?
Yes, it'll be backwards compatible. Any new changes for the API will be put in a new and separated version.
Where can I submit bugs and pull requests?
They can be posted on our Github!
Will Blueprint extensions work on Pelican?
No, Blueprint extensions will not work with Pelican.
Will the client area match the new admin area?
Yes, we are currently working on that.
Will WHMCS and other billing solutions still work?
To our knowledge, almost all of these solutions use the Panel's API to function. We will be supporting the same API, so everything should work the same.
Are automatic updates planned?
Yes!
Where can I submit bugs and pull requests?
They can be posted on our Github!
Will Wings support plugins?
Currently it's not planned. But new features are being built into Wings and are on the way!
Will the original Wings still be compatible with Pelican?
Yes, the original latest version of Wings will remain compatible with Pelican. We are working on adding new features and improvements to Wings that will greatly improve your experience.
Will Podman / Kubernetes be supported?
Yes, we plan on supporting them in the future.
The Pelican Panel has been relicensed to AGPLv3. Wings still uses MIT.
This license change does only affect you if you meet all of the following requirements:
- You modified the Pelican panel source files.
- These modifications are not open source.
- Your modified panel is publicly available. (Note: People who are family, friends, and acquaintances are not the public)
If you meet all of the above requirements you need a commercial license. Please note that the usage or development of plugins/ themes does not require a commercial license.
You can find more detailed information about the new license in this blog post.
Where can I submit feature requests and discuss new ideas?
They can be posted on our Github Discussions
Are there any hostilities with the previous project?
Not at all. We also gave the previous team 2 months of advance notice.
Why move away to make your own project?
Difference of visions, directions, and opinions.
Couldn't these changes be part of Pterodactyl?
If they could, they would. But they can't, so they shan't.
What will happen with Pterodactyl? Is it EOL now?
We can't say that. That's up to the Maintainer of Pterodactyl. Pelican and Pterodactyl are separate projects.