About WingGate
WingGate is a self-hosted remote asset management platform for individuals and small teams: wing-connector dials out from inside your network, and a single console covers terminal, SSH, file and MCP access with project-scoped grants and audit — no inbound ports exposed on your assets.
What it is
Everything is modeled around four entities: Organization bounds your resources and members, Project is a work context and authorization view, Asset is a physical access object in the pool, and Session is the lifecycle and audit boundary of every access. The management plane uses a fixed Owner/Admin/Member role matrix, and the data plane uses verifiable grants — no configurable authorization rule engine.
Why it is built this way
Credentials are isolated by class and every session and grant-relevant action lands in audit by default. Features ship only when they can be honestly described: pages and documentation describe the current implementation and are updated after delivery.
Contact and feedback
WingGate is maintained by its author — no sales team, no support desk, no community forum and no paid support tier, but there is always a real person to reach when something goes wrong.
For usage questions, start with the support page; for anything it does not cover, contact the operator of the deployment you use, with what you tried, the exact symptom and the troubleshooting steps you already checked.
- Support and troubleshooting — Usage questions, connection issues and troubleshooting steps
- Contact and support channels — Full channel list: security disclosure, business and deployment notes
Project status
The project is at version 0.1.0, an early release under active development. Version changes, compatibility requirements and security-relevant fixes are summarized on the change log page.