wildburrow
Self-hosted HTTPS tunnels on your own domain: expose a local port as myapp.tunnel.example.com, or a whole wildcard
like *.myapp.tunnel.example.com, at any depth, with certificates issued on demand. Linux and macOS.
Server
uv tool install 'wildburrow[server]'
wildburrow service install # asks for the domain, DNS provider and keys, then runs as a systemd or launchd service
Point tunnel.example.com and *.tunnel.example.com at it. Or with Docker: ghcr.io/isik-kaplan/wildburrow.
Client
uv tool install wildburrow
wildburrow login tunnel.example.com
wildburrow 3000 myapp '*.myapp' # https://myapp.tunnel.example.com and https://<anything>.myapp.tunnel.example.com
Documentation
The full index is docs/INDEX.md.
- Client - logging in, the ssh and websocket transports, staying connected, proxies
- Names - wildcards at any depth, binding,
wildburrow names, several local sites behind one router - Tokens - letting people in with tokens you mint and sign yourself
- Server - the service, HTTPS, Docker and Traefik
- Settings - every setting
- Plugins and development
What changed in each release: CHANGELOG.md.
License
MIT
Metadata
Release files for wildburrow 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wildburrow-0.2.0.tar.gz | 133.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wildburrow-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 199.2 kB
Release files / wildburrow-0.2.0.tar.gz
| Download URL | wildburrow-0.2.0.tar.gz |
|---|---|
| Size | 133.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20571d71fa2d9a2ce59b3c9e5a53d8bdd3b1a9598d963315b5b03e5619c1fb71
|
|
BLAKE2b-256 checksum How to use checksums |
eeb80a8f50fe5b1c447c3695a8ad6528ff3a2436213acdf2eec65cad7e1951bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / wildburrow-0.2.0-py3-none-any.whl
| Download URL | wildburrow-0.2.0-py3-none-any.whl |
|---|---|
| Size | 65.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc7586276f94b37539c5d1418517d0e53c5fb40672d4f918264118128985c71d
|
|
BLAKE2b-256 checksum How to use checksums |
0a24580d0c99518b211f7b395a66f003059a8c31d611c964ab58b30adcd7c67d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for wildburrow 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wildburrow-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.