Reyka
GitHub
Open source soon

Your VPN service,
under control.

The self-hosted operations panel for VPN providers. Users, nodes, protocols and subscriptions — one clear interface, on your infrastructure.

Follow on GitHub Explore the panel
SELF-HOSTED DOCKER COMPOSE LIGHT + DARK
ILLUSTRATIVE INTERFACE · SYNTHETIC DATA

01 / OPERATIONS

The whole service.
No terminal required.

From a routine plan change to a node incident on your phone, Reyka keeps the next action close and the impact visible.

01

Know what needs attention

Node health, online users, traffic and recent activity surface on one overview. A user's card answers which host they use and when they were last seen.

02

Change access with confidence

Manage users, squads, limits and subscriptions without hand-editing JSON. Profile saves show a dry-run before credentials or tunnels change.

03

Roll out, not restart

The panel sends desired state to each node agent. The agent applies the diff across connected engines — no panel-driven engine restart.

02 / PROTOCOLS

One model.
More than one engine.

Xray share links and AmneziaWG configs can live side by side in the same user's subscription. Non-standard protocols are ordinary properties, not a separate workflow.

ENGINEPROTOCOLSDELIVERY
XrayVLESS · REALITY · XHTTP · Trojan · Shadowsocks 2022 · Hysteria2SHARE LINKS + JSON
AmneziaWGAmneziaWG obfuscation · Plain WireGuard.CONF + QR
sing-boxTUIC · AnyTLS · ShadowTLS · NaiveProxySUBSCRIPTION
OpenVPNOpenVPN · Optional Cloak.OVPN
IKEv2strongSwanNATIVE PROFILES
MieruMieruSUBSCRIPTION

CLIENT FORMATSShare links, Xray JSON, Clash, Mihomo, Stash, sing-box, AmneziaWG, OpenVPN and native IKEv2 profiles.

03 / SUBSCRIPTIONS

One link for the operator. The right format for every client.

Reyka renders the subscription for the app asking for it. Users get the tunnels their squads allow; operators see exactly what was delivered.

  • Per-user credentials, hosts and access
  • Client-aware formats from one neutral model
  • Revocation, traffic limits and expiration built in

04 / HOW IT WORKS

Your hardware.
Your control plane.

Run the panel as a Docker Compose stack, connect Docker-based node agents, then manage the service from the panel.

  1. 01

    Start the panel

    Bring up Reyka and PostgreSQL. Add Caddy for automatic HTTPS when the panel is public.

  2. 02

    Connect your nodes

    Build the node image, create a node in the panel and run its one-time install snippet on the host.

  3. 03

    Publish access

    Assign profiles through squads and hosts. Each user's subscription follows those choices.

SELF-HOST WITH DOCKER

From checkout to running stack.

The setup script generates local secrets. The first start builds the panel and applies database migrations.

Deployment guide
TERMINAL 
# Clone the repository
git clone https://github.com/Rejke/reyka.git
cd reyka

# Generate secrets and start the stack
./scripts/init-env.sh
docker compose up -d --wait

05 / OPEN SOURCE

Infrastructure you can inspect. A service you own.

Reyka is being prepared for its public source release. Follow the repository for the code, license and release notes.

PUBLIC REPOSITORYLICENSE AT RELEASESELF-HOSTED BY DESIGN
Follow Reyka on GitHub