# Pelican Wings

Pelican Wings is a self-hosted control plane for the Pelican game-server panel. It is open source and self-hosted, installable on Proxmox.

Canonical page: https://ourlocalhost.com/app/7077/pelican-wings

## Description

Pelican Wings is a self-hosted control plane for the Pelican game-server panel. It manages running game-server instances over a secure web API, retrieves logs, generates backups, and provides an SSH file transfer (SFTP) endpoint, giving panel operators lightweight control over server lifecycle and file access.

## Platform availability

Available on 1 of 9 platforms: Proxmox.

## Links

- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=pelican-wings
- GitHub: https://github.com/pelican-dev/wings
- Documentation: https://pelican.dev/docs/wings/install

## Common questions

### Does Wings run each game server in its own Docker container?

Yes. Pelican's Wings server control daemon runs each game server in its own Docker container.

### Does Wings include an SFTP server, and what credentials does it accept?

Wings ships with a built-in SFTP server so the system can avoid Pelican-specific dependencies. Users authenticate with the same credentials they would normally use to access the Panel.

### Can Wings be controlled over HTTP for logs, backups, and lifecycle management?

Yes. Wings provides an HTTP API for interfacing directly with running server instances, fetching server logs, generating backups, and controlling all aspects of the server lifecycle.

### What kinds of Pelican Panel and Wings deployment issues are covered by the troubleshooting documentation?

It covers Panel application errors, Wings connectivity failures, schedule execution problems, and file upload issues.

### Where should Wings-specific issues or feature requests be reported?

Wings-specific issues and feature requests can be reported in GitHub Issues.

---
Source: Our Local Host (https://ourlocalhost.com/app/7077/pelican-wings), the self-hosted and open-source app directory.