Inletsctl – the fastest way to create self-hosted tunnels
12 hours ago
- #devops
- #cloud-computing
- #networking
- inletsctl automates the creation of exit-servers (tunnel servers) on public cloud infrastructure.
- The 'create' command provisions a cloud VM with a public IP and pre-installs inlets.
- Provides a connection string for use with the inlets client.
- Supports L4 TCP and HTTPS tunnels for local services using inlets-pro.
- Facilitates Kubernetes cluster tunnels and port-forwarding with 'inletsctl kfwd'.
- Demo includes creating a DigitalOcean host, running a local Python server, and accessing it via public IP.
- Quickly provision hosts with 'inletsctl create' and delete them with 'inletsctl delete'.
- Cloud host costs vary; estimated around $5/month on providers like DigitalOcean or Scaleway.
- inletsctl does not auto-delete exit nodes; manual deletion is required.
- Install via arkade or directly from releases; supports updates.
- Supports multiple cloud providers: DigitalOcean, Google Cloud, AWS, Azure, etc.
- Uses a provision package for cloud host setup with defaults for OS images and plans.
- Separate binary to avoid bloat; core tunnel binary remains lightweight.
- Open-source Go package 'provision' allows extending support for new providers.
- Licensed under MIT; inlets-pro requires a subscription under EULA.