Skip to main content

We use cookies for analytics. Privacy

Back to Work
Cloud & Infrastructure/ Case study

Kintunnel

Docker-native WireGuard VPN manager

Built with

TypeScript / Docker / Docker Compose / WireGuard / Self-Hosted Infrastructure / Dokploy

Source code

Inside the project

01 / 01

Local capture of the self-hosted WireGuard peer management UI.

Kintunnel1 / 1

Kintunnel admin screen for creating a WireGuard peer

Local capture of the self-hosted WireGuard peer management UI.

The brief

The problem

Small teams and families need secure private access without fragile manual VPN setup. The system has to stay understandable, portable, and deployable on self-hosted infrastructure.

Our approach

Built a management layer around WireGuard using Docker Compose and self-hosted deployment conventions, so peers, configs, and tunnels stay inside clear infrastructure boundaries.

Features

What it does

  1. 01

    WireGuard network management

  2. 02

    Docker-native deployment

  3. 03

    Self-hosted operating model

  4. 04

    Private access architecture

  5. 05

    Portable infrastructure patterns

Results

What happened

  • Public GitHub project

  • WireGuard peers and configs managed through Docker

  • Runs on self-hosted infrastructure

  • Configuration kept portable between hosts

Visibility
Public GitHub
Updated
May 2026
Focus
Private networking
Stack
Docker and WireGuard

Under the hood

Portable VPN management pattern using Docker-hosted WireGuard and a controlled configuration workflow.

frontend
backend
service
external
Manage peersApply configContainerized runtimeEncrypted tunnel
Admin UI
Management surface
Control API
Configuration workflow
WireGuard
VPN tunnel layer
Docker Host
Portable runtime
Client Devices
Private access clients

Portable VPN management pattern using Docker-hosted WireGuard and a controlled configuration workflow.

Working on something similar?

Tell us what you are building or fixing.