diff --git a/Makefile b/Makefile
index 6ec70f3..8810e6b 100644
--- a/Makefile
+++ b/Makefile
@@ -5,7 +5,7 @@ all: charts
 charts:
 	cd chart && \
 	helm package inlets-http-server/ && \
-	helm package inlets-pro/ && \
-	helm package inlets-pro-client/
+	helm package inlets-tcp-server/ && \
+	helm package inlets-tcp-client/
 	mv chart/*.tgz docs/charts
 	helm repo index docs/charts --url https://inlets.github.io/inlets-pro/charts --merge ./docs/charts/index.yaml
diff --git a/artifacts/README.md b/artifacts/README.md
index de20c02..114d3bb 100644
--- a/artifacts/README.md
+++ b/artifacts/README.md
@@ -1,3 +1,3 @@
-# Artifacts for inlets PRO
+# Artifacts for inlets Pro
 
 See also: [Options for Kubernetes integration and deployment](chart/)
diff --git a/artifacts/inlets-pro.service b/artifacts/inlets-pro.service
index 427cefb..8f55fb8 100644
--- a/artifacts/inlets-pro.service
+++ b/artifacts/inlets-pro.service
@@ -1,5 +1,5 @@
 [Unit]
-Description=inlets PRO TCP server
+Description=inlets Pro TCP server
 After=network.target
 
 [Service]
diff --git a/chart/README.md b/chart/README.md
index 62f656c..47b71c2 100644
--- a/chart/README.md
+++ b/chart/README.md
@@ -1,6 +1,6 @@
-## Helm charts for inlets Pro
+## Helm charts for inlets
 
-[inlets](https://inlets.dev/) consists of a client and a server portion.
+[inlets](https://inlets.dev) has both a client and a server, which connect to each other to build a tunnel.
 
 When a client wants to expose a service publicly, or privately within a remote network, it connects to a server using its control-plane (a HTTPS websocket).
 
@@ -8,17 +8,19 @@ There is no need for your data plane to be exposed on the Internet, you can bind
 
 Kubernetes v1.19+ is required for the helm charts provided in this repository, due to the various versions of the Ingress API, the minimum supported version will be `networking.k8s.io/v1`.
 
-### Deploy an inlets Pro TCP server
+### Deploy the inlets tunnel client or server as a Kubernetes Deployment
 
-* [Use your Kubernetes cluster for exit-servers](https://github.com/inlets/inlets-pro/tree/master/chart/inlets-pro)
+* [Deploy an inlets HTTP server](https://github.com/inlets/inlets-pro/tree/master/chart/inlets-http-server)
 
-### Deploy an inlets Pro TCP client
+* [Deploy an inlets TCP client](https://github.com/inlets/inlets-pro/tree/master/chart/inlets-pro-client)
 
-* [Run an inlets PRO client in your Kubernetes cluster](https://github.com/inlets/inlets-pro/tree/master/chart/inlets-pro-client)
+* [Deploy an inlets TCP server](https://github.com/inlets/inlets-pro/tree/master/chart/inlets-tcp-server)
 
-### Deploy an inlets Pro HTTP client or server
+## Other Kubernetes use-cases
 
-To deploy a client or server, request access to the helm chart after your purchase.
+### Get Public L4 Load Balancers for your cluster
+
+See also: [inlets-operator](https://github.com/inlets/inlets-operator) which automates both parts of the above for a set number of supported clouds, and integrates through Kubernetes services of type LoadBalancer.
 
 ### Setup your preferred IngressController with TLS certs from Let's Encrypt
 
@@ -26,12 +28,9 @@ To deploy a client or server, request access to the helm chart after your purcha
 
 ### Get kubectl access to your private cluster from anywhere
 
-* [Get kubectl access to your private cluster from anywhere](https://blog.alexellis.io/get-private-kubectl-access-anywhere/)
+* [Tutorial: Expose a local Kubernetes API Server](https://docs.inlets.dev/tutorial/kubernetes-api-server/)
 
 ### Continous Deployment and fleet management with ArgoCD
 
+* [How To Manage Inlets Tunnels Servers With Argo CD and GitOps](https://inlets.dev/blog/2022/08/10/managing-tunnel-servers-with-argocd.html)
 * [Argo CD for your private Raspberry Pi k3s cluster](https://johansiebens.dev/posts/2020/08/argo-cd-for-your-private-raspberry-pi-k3s-cluster/)
-
-### Get Public L4 LoadBalancers for your cluster
-
-See also: [inlets-operator](https://github.com/inlets/inlets-operator) which automates both parts of the above for a set number of supported clouds, and integrates through Kubernetes services of type LoadBalancer.
diff --git a/chart/inlets-http-server/Chart.yaml b/chart/inlets-http-server/Chart.yaml
index d763dbd..d30a60a 100644
--- a/chart/inlets-http-server/Chart.yaml
+++ b/chart/inlets-http-server/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v2
 name: inlets-http-server
-description: Helm chart for an inlets HTTP server
+description: Deploy an inlets HTTP tunnel server to a cluster
 type: application
-version: 0.4.3
+version: 0.5.0
 appVersion: 1.16.0
diff --git a/chart/inlets-http-server/README.md b/chart/inlets-http-server/README.md
index 30f0ece..5f53dbd 100644
--- a/chart/inlets-http-server/README.md
+++ b/chart/inlets-http-server/README.md
@@ -1,8 +1,8 @@
 # inlets-http-server
 
-This is the helm chart for an inlets PRO HTTP server
+This is the helm chart for an inlets Pro HTTP server
 
-Use it to deploy one or more inlets PRO HTTP tunnel servers to your Kubernetes cluster using a wildcard domain.
+Use it to deploy one or more inlets Pro HTTP tunnel servers to your Kubernetes cluster using a wildcard domain.
 
 # Use your Kubernetes cluster for inlets-pro HTTP exit-servers
 
@@ -101,7 +101,7 @@ kubectl create secret generic -n inlets inlets-$NAME-token \
   --from-literal token=$TOKEN
 ```
 
-Create a `values.yaml` and customise the `controlPlaneIngress` with the domain you want the inlets PRO client to connect to.
+Create a `values.yaml` and customise the `controlPlaneIngress` with the domain you want the inlets Pro client to connect to.
 
 Then update `dataPlaneIngresses` with any services that you want to expose to the Internet from the tunnel. If you don't want to expose anything then change it to: `dataPlaneIngresses: {}`.
 
diff --git a/chart/inlets-pro-client/Chart.yaml b/chart/inlets-pro-client/Chart.yaml
deleted file mode 100644
index 84e9313..0000000
--- a/chart/inlets-pro-client/Chart.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-apiVersion: v2
-name: inlets-pro-client
-description: Helm chart for an inlets-pro TCP client
-type: application
-version: 0.4.3
-appVersion: 1.0.0
\ No newline at end of file
diff --git a/chart/inlets-pro/Chart.yaml b/chart/inlets-pro/Chart.yaml
deleted file mode 100644
index 9fc38e8..0000000
--- a/chart/inlets-pro/Chart.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-apiVersion: v2
-name: inlets-pro
-description: Helm chart for an inlets-pro TCP server
-type: application
-version: 0.4.3
-appVersion: 1.16.0
diff --git a/chart/inlets-pro-client/.gitignore b/chart/inlets-tcp-client/.gitignore
similarity index 100%
rename from chart/inlets-pro-client/.gitignore
rename to chart/inlets-tcp-client/.gitignore
diff --git a/chart/inlets-pro-client/.helmignore b/chart/inlets-tcp-client/.helmignore
similarity index 100%
rename from chart/inlets-pro-client/.helmignore
rename to chart/inlets-tcp-client/.helmignore
diff --git a/chart/inlets-tcp-client/Chart.yaml b/chart/inlets-tcp-client/Chart.yaml
new file mode 100644
index 0000000..b780316
--- /dev/null
+++ b/chart/inlets-tcp-client/Chart.yaml
@@ -0,0 +1,6 @@
+apiVersion: v2
+name: inlets-tcp-client
+description: Deploy an inlets TCP tunnel client to a cluster
+type: application
+version: 0.5.0
+appVersion: 1.0.0
\ No newline at end of file
diff --git a/chart/inlets-pro-client/README.md b/chart/inlets-tcp-client/README.md
similarity index 88%
rename from chart/inlets-pro-client/README.md
rename to chart/inlets-tcp-client/README.md
index 74875a3..e0b5b94 100644
--- a/chart/inlets-pro-client/README.md
+++ b/chart/inlets-tcp-client/README.md
@@ -1,12 +1,12 @@
-## Run an inlets PRO client in your Kubernetes cluster
+## Run an inlets Pro client in your Kubernetes cluster
 
-An inlets PRO client can be used to tunnel a service from a local cluster to a remote network or remote Kubernetes cluster.
+An inlets Pro client can be used to tunnel a service from a local cluster to a remote network or remote Kubernetes cluster.
 
 You should decide whether you want to expose the remote service to the world, or to just the local area network of the exit-server.
 
 ### Prerequisites
 
-You will need to set up an inlets PRO TCP server so that the client has an endpoint to connect to. Create a server manually and then configure inlets-pro, or use [inletsctl](https://github.com/inlets/inletsctl) to create a preconfigured cloud VM, or use the helm chart for the inlets-pro server to install the server into a Pod.
+You will need to set up an inlets Pro TCP server so that the client has an endpoint to connect to. Create a server manually and then configure inlets-pro, or use [inletsctl](https://github.com/inlets/inletsctl) to create a pre-configured cloud VM, or use the helm chart for the inlets-pro server to install the server into a Pod.
 
 Install [arkade](https://arkade.dev/), which is used in the tutorial to install Kubernetes software.
 
@@ -58,7 +58,7 @@ kubectl create secret generic -n $NS \
   $TOKEN_NAME --from-literal token=$SERVER_TOKEN
 
 
-helm upgrade --install grafana-tunnel inlets-pro/inlets-pro-client \
+helm upgrade --install grafana-tunnel inlets-pro/inlets-tcp-client \
   --namespace $NS \
   --set tokenSecretName=$TOKEN_NAME \
   --set url=$URL \
@@ -71,11 +71,11 @@ echo Access Grafana via http://$IP:3000
 kubectl logs deploy/grafana-tunnel
 ```
 
-If you wish to disable public access to the forwarded ports, look at the reference documentation for inlets PRO for how to bind the data-plane to a local LAN or loopback adapter.
+If you wish to disable public access to the forwarded ports, look at the reference documentation for inlets Pro for how to bind the data-plane to a local LAN or loopback adapter.
 
 ### Install a client for a server using an IngressController for TLS termination
 
-If you are using an IngressController for TLS termination, then you need to disable the Auto TLS feature of inlets PRO (`--set autoTLS=false`).
+If you are using an IngressController for TLS termination, then you need to disable the Auto TLS feature of inlets Pro (`--set autoTLS=false`).
 
 Install OpenFaaS which bundles Prometheus:
 
@@ -96,7 +96,7 @@ kubectl create secret generic -n default \
 kubectl create secret generic -n default \
   $TOKEN_NAME --from-literal token=$SERVER_TOKEN
 
-helm upgrade --install prometheus-tunnel inlets-pro/inlets-pro-client \
+helm upgrade --install prometheus-tunnel inlets-pro/inlets-tcp-client \
   --namespace openfaas \
   --set tokenSecretName=$TOKEN_NAME \
   --set url=$URL \
@@ -138,7 +138,7 @@ kubectl create secret generic -n default \
   $TOKEN_NAME --from-literal token=$SERVER_TOKEN
 
 helm upgrade --install nginx-tunnel \
-  inlets-pro/inlets-pro-client \
+  inlets-pro/inlets-tcp-client \
   --namespace default \
   --set tokenSecretName=$TOKEN_NAME \
   --set url=$URL \
diff --git a/chart/inlets-pro-client/templates/NOTES.txt b/chart/inlets-tcp-client/templates/NOTES.txt
similarity index 100%
rename from chart/inlets-pro-client/templates/NOTES.txt
rename to chart/inlets-tcp-client/templates/NOTES.txt
diff --git a/chart/inlets-pro-client/templates/_helpers.tpl b/chart/inlets-tcp-client/templates/_helpers.tpl
similarity index 100%
rename from chart/inlets-pro-client/templates/_helpers.tpl
rename to chart/inlets-tcp-client/templates/_helpers.tpl
diff --git a/chart/inlets-pro-client/templates/deployment.yaml b/chart/inlets-tcp-client/templates/deployment.yaml
similarity index 100%
rename from chart/inlets-pro-client/templates/deployment.yaml
rename to chart/inlets-tcp-client/templates/deployment.yaml
diff --git a/chart/inlets-pro-client/templates/serviceaccount.yaml b/chart/inlets-tcp-client/templates/serviceaccount.yaml
similarity index 100%
rename from chart/inlets-pro-client/templates/serviceaccount.yaml
rename to chart/inlets-tcp-client/templates/serviceaccount.yaml
diff --git a/chart/inlets-pro-client/values.yaml b/chart/inlets-tcp-client/values.yaml
similarity index 100%
rename from chart/inlets-pro-client/values.yaml
rename to chart/inlets-tcp-client/values.yaml
diff --git a/chart/inlets-pro/.gitignore b/chart/inlets-tcp-server/.gitignore
similarity index 100%
rename from chart/inlets-pro/.gitignore
rename to chart/inlets-tcp-server/.gitignore
diff --git a/chart/inlets-pro/.helmignore b/chart/inlets-tcp-server/.helmignore
similarity index 100%
rename from chart/inlets-pro/.helmignore
rename to chart/inlets-tcp-server/.helmignore
diff --git a/chart/inlets-tcp-server/Chart.yaml b/chart/inlets-tcp-server/Chart.yaml
new file mode 100644
index 0000000..5fce6ba
--- /dev/null
+++ b/chart/inlets-tcp-server/Chart.yaml
@@ -0,0 +1,6 @@
+apiVersion: v2
+name: inlets-tcp-server
+description: Deploy an inlets TCP tunnel server to a cluster
+type: application
+version: 0.5.0
+appVersion: 1.16.0
diff --git a/chart/inlets-pro/README.md b/chart/inlets-tcp-server/README.md
similarity index 97%
rename from chart/inlets-pro/README.md
rename to chart/inlets-tcp-server/README.md
index f68f0db..9ff16aa 100644
--- a/chart/inlets-pro/README.md
+++ b/chart/inlets-tcp-server/README.md
@@ -1,6 +1,6 @@
 ## Use your Kubernetes cluster for exit-servers
 
-This chart installs the inlets PRO server in TCP mode. It runs the inlets server process as a Pod within your Kubernetes cluster.
+This chart installs the inlets Pro server in TCP mode. It runs the inlets server process as a Pod within your Kubernetes cluster.
 
 You can use this to avoid creating individual exit-server VMs, or to connect a number of services into to a public Kubernetes cluster. It's up to you to decide whether you want to access any tunneled services from the Internet, or from within the cluster.
 
@@ -90,7 +90,7 @@ kubectl create secret generic inlets-pro-secret \
 
 The chart will deploy two Kubernetes services, an Ingress record and a Deployment to run the inlets-pro server process.
 
-* `prometheus-tunnel-control-plane` - a service exposed by Ingress, for the websocket of inlets PRO (usually port 8123)
+* `prometheus-tunnel-control-plane` - a service exposed by Ingress, for the websocket of inlets Pro (usually port 8123)
 * `prometheus-tunnel-data-plane` - a local service to access Prometheus from within the cluster (usually 9090)
 
 Edit `values.yaml`:
@@ -100,7 +100,7 @@ Make any changes you need.
 ```bash
 export DOMAIN="prometheus.example.com"
 
-helm upgrade --install prometheus-tunnel inlets-pro/inlets-pro \
+helm upgrade --install prometheus-tunnel inlets-pro/inlets-tcp-server \
   --set ingress.domain=$DOMAIN
 ```
 
diff --git a/chart/inlets-pro/templates/NOTES.txt b/chart/inlets-tcp-server/templates/NOTES.txt
similarity index 100%
rename from chart/inlets-pro/templates/NOTES.txt
rename to chart/inlets-tcp-server/templates/NOTES.txt
diff --git a/chart/inlets-pro/templates/_helpers.tpl b/chart/inlets-tcp-server/templates/_helpers.tpl
similarity index 100%
rename from chart/inlets-pro/templates/_helpers.tpl
rename to chart/inlets-tcp-server/templates/_helpers.tpl
diff --git a/chart/inlets-pro/templates/control-plane-service.yaml b/chart/inlets-tcp-server/templates/control-plane-service.yaml
similarity index 100%
rename from chart/inlets-pro/templates/control-plane-service.yaml
rename to chart/inlets-tcp-server/templates/control-plane-service.yaml
diff --git a/chart/inlets-pro/templates/data-plane-service.yaml b/chart/inlets-tcp-server/templates/data-plane-service.yaml
similarity index 100%
rename from chart/inlets-pro/templates/data-plane-service.yaml
rename to chart/inlets-tcp-server/templates/data-plane-service.yaml
diff --git a/chart/inlets-pro/templates/deployment.yaml b/chart/inlets-tcp-server/templates/deployment.yaml
similarity index 100%
rename from chart/inlets-pro/templates/deployment.yaml
rename to chart/inlets-tcp-server/templates/deployment.yaml
diff --git a/chart/inlets-pro/templates/ingress.yaml b/chart/inlets-tcp-server/templates/ingress.yaml
similarity index 100%
rename from chart/inlets-pro/templates/ingress.yaml
rename to chart/inlets-tcp-server/templates/ingress.yaml
diff --git a/chart/inlets-pro/templates/serviceaccount.yaml b/chart/inlets-tcp-server/templates/serviceaccount.yaml
similarity index 100%
rename from chart/inlets-pro/templates/serviceaccount.yaml
rename to chart/inlets-tcp-server/templates/serviceaccount.yaml
diff --git a/chart/inlets-pro/values.yaml b/chart/inlets-tcp-server/values.yaml
similarity index 100%
rename from chart/inlets-pro/values.yaml
rename to chart/inlets-tcp-server/values.yaml
diff --git a/docs/README.md b/docs/README.md
index 8f88989..cf69c58 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -12,8 +12,8 @@ $ helm repo update
 
 $ helm search repo inlets-pro
 NAME                            CHART VERSION   APP VERSION     DESCRIPTION                            
-inlets-pro/inlets-pro           0.2.1           1.16.0          Helm chart for an inlets-pro TCP server
-inlets-pro/inlets-pro-client    0.2.1           1.0.0           Helm chart for an inlets-pro TCP client
+inlets-pro/inlets-tcp-server           0.2.1           1.16.0          Helm chart for an inlets-pro TCP server
+inlets-pro/inlets-tcp-client    0.2.1           1.0.0           Helm chart for an inlets-pro TCP client
 inlets-pro/inlets-http-server   0.2.1           1.16.0          Helm chart for an inlets HTTP server  
 ```
 
diff --git a/docs/charts/index.yaml b/docs/charts/index.yaml
index 22f937b..ba5eae6 100644
--- a/docs/charts/index.yaml
+++ b/docs/charts/index.yaml
@@ -3,7 +3,17 @@ entries:
   inlets-http-server:
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.763321+01:00"
+    created: "2022-10-03T09:15:23.245918+01:00"
+    description: Deploy an inlets HTTP tunnel server to a cluster
+    digest: acc57685488c75ccc6791bf2fcdb6697cafcaff6f1cbc5dfdd29cfe3ee0879d1
+    name: inlets-http-server
+    type: application
+    urls:
+    - https://inlets.github.io/inlets-pro/charts/inlets-http-server-0.5.0.tgz
+    version: 0.5.0
+  - apiVersion: v2
+    appVersion: 1.16.0
+    created: "2022-10-03T09:15:23.245626+01:00"
     description: Helm chart for an inlets HTTP server
     digest: 69416d500a12ad1b04a8857f24f748fecea8d67965d5618cc7f259059897af10
     name: inlets-http-server
@@ -13,7 +23,7 @@ entries:
     version: 0.4.3
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.76303+01:00"
+    created: "2022-10-03T09:15:23.245353+01:00"
     description: Helm chart for an inlets HTTP server
     digest: e226d19e14aac943de2e2dfb25535998ae474bb39fe88aaa4f0ce6b7212ee1df
     name: inlets-http-server
@@ -23,7 +33,7 @@ entries:
     version: 0.4.2
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.762733+01:00"
+    created: "2022-10-03T09:15:23.245064+01:00"
     description: Helm chart for an inlets HTTP server
     digest: 83126ada1077e4ab9aeb40babe89cd13539d381c235335f8b637e89b21291dd5
     name: inlets-http-server
@@ -33,7 +43,7 @@ entries:
     version: 0.4.1
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.762404+01:00"
+    created: "2022-10-03T09:15:23.244761+01:00"
     description: Helm chart for an inlets HTTP server
     digest: 2427570cee3593f76b7787a07d81d69a3266f31bec2edcd97b46e8bb6b6e020a
     name: inlets-http-server
@@ -43,7 +53,7 @@ entries:
     version: 0.4.0
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.761986+01:00"
+    created: "2022-10-03T09:15:23.244353+01:00"
     description: Helm chart for an inlets HTTP server
     digest: f6de8d04eef6af9c26a17005849f885aece0a5b04117e10ebcd054f5235f9f60
     name: inlets-http-server
@@ -53,7 +63,7 @@ entries:
     version: 0.3.0
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.759856+01:00"
+    created: "2022-10-03T09:15:23.241713+01:00"
     description: Helm chart for an inlets HTTP server
     digest: 9c946af21b3fba2710002fc24409b72b43f7377d4f9768109e02213fffcff82a
     name: inlets-http-server
@@ -64,7 +74,7 @@ entries:
   inlets-pro:
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.765136+01:00"
+    created: "2022-10-03T09:15:23.247774+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: b849b6e9c6c4a0825fdcfa1a59f6a44c816aff2c8768b66e2710c3721187b901
     name: inlets-pro
@@ -74,7 +84,7 @@ entries:
     version: 0.4.3
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.76481+01:00"
+    created: "2022-10-03T09:15:23.247471+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: 54bfa103641526ce4ab10d5dc2ee3a7420754bfe2f4dce3d569957bf38d78538
     name: inlets-pro
@@ -84,7 +94,7 @@ entries:
     version: 0.4.2
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.764507+01:00"
+    created: "2022-10-03T09:15:23.247156+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: 4b5b7b8032d40e5d3969399cba1943eb752b15efb28b2fbf77b9566522ecc0bc
     name: inlets-pro
@@ -94,7 +104,7 @@ entries:
     version: 0.4.1
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.764218+01:00"
+    created: "2022-10-03T09:15:23.246846+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: 898f6551157fb49c0a617eb30f225b9921a4aba60eba804c6307245b1f8e205a
     name: inlets-pro
@@ -104,7 +114,7 @@ entries:
     version: 0.4.0
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.76394+01:00"
+    created: "2022-10-03T09:15:23.246531+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: 108eaf1e75fa15ba60316867c6bdc645f177dbe305bf320382b49fa0e40222db
     name: inlets-pro
@@ -114,7 +124,7 @@ entries:
     version: 0.3.0
   - apiVersion: v2
     appVersion: 1.16.0
-    created: "2022-09-10T21:43:39.763631+01:00"
+    created: "2022-10-03T09:15:23.246234+01:00"
     description: Helm chart for an inlets-pro TCP server
     digest: 75c0ca85be33d6461410332b2d3f9438e681e53a326f0b12cb80540a5b8db0f2
     name: inlets-pro
@@ -125,7 +135,7 @@ entries:
   inlets-pro-client:
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.766613+01:00"
+    created: "2022-10-03T09:15:23.249243+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: 7db4d044da23c3171b6de57cdb2318f32e10e40445fa0f2009df619852a83a86
     name: inlets-pro-client
@@ -135,7 +145,7 @@ entries:
     version: 0.4.3
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.766362+01:00"
+    created: "2022-10-03T09:15:23.248999+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: 3193fd6292800c0fbc176ba906d4115dd94551e3e1fb21112e0d637d19ecdab4
     name: inlets-pro-client
@@ -145,7 +155,7 @@ entries:
     version: 0.4.2
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.76612+01:00"
+    created: "2022-10-03T09:15:23.248757+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: e52a838e3411b2a2609afcc1ce47471f66497b9c3ffbde631809b7574885a189
     name: inlets-pro-client
@@ -155,7 +165,7 @@ entries:
     version: 0.4.1
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.765872+01:00"
+    created: "2022-10-03T09:15:23.248523+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: b6bfd6f0d4f74ff7bad733ada9c8d2ad426a139925a01346ec15186a2a89f29c
     name: inlets-pro-client
@@ -165,7 +175,7 @@ entries:
     version: 0.4.0
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.765632+01:00"
+    created: "2022-10-03T09:15:23.248261+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: db19167e8659dfca115294b51ca8c8cc3ee53e4b4b692ba6ddf3f61a748cdd00
     name: inlets-pro-client
@@ -175,7 +185,7 @@ entries:
     version: 0.3.0
   - apiVersion: v2
     appVersion: 1.0.0
-    created: "2022-09-10T21:43:39.765386+01:00"
+    created: "2022-10-03T09:15:23.248023+01:00"
     description: Helm chart for an inlets-pro TCP client
     digest: 627dc96ec83d8dd8cff9421d503bd71488a8e276ddbc6c72ec599aa50fd147c0
     name: inlets-pro-client
@@ -183,4 +193,26 @@ entries:
     urls:
     - https://inlets.github.io/inlets-pro/charts/inlets-pro-client-0.2.1.tgz
     version: 0.2.1
-generated: "2022-09-10T21:43:39.759374+01:00"
+  inlets-tcp-client:
+  - apiVersion: v2
+    appVersion: 1.0.0
+    created: "2022-10-03T09:15:23.25092+01:00"
+    description: Deploy an inlets TCP tunnel client to a cluster
+    digest: dd9b48414beba081d5ae4d3f8c1064d0675b37fe4d4a2b639bdfdbbc648ffbc7
+    name: inlets-tcp-client
+    type: application
+    urls:
+    - https://inlets.github.io/inlets-pro/charts/inlets-tcp-client-0.5.0.tgz
+    version: 0.5.0
+  inlets-tcp-server:
+  - apiVersion: v2
+    appVersion: 1.16.0
+    created: "2022-10-03T09:15:23.251268+01:00"
+    description: Deploy an inlets TCP tunnel server to a cluster
+    digest: 01dfdb92723407872e4d8321f21e5f5d0c3db38b0d8b28578e3e0a41c2a71609
+    name: inlets-tcp-server
+    type: application
+    urls:
+    - https://inlets.github.io/inlets-pro/charts/inlets-tcp-server-0.5.0.tgz
+    version: 0.5.0
+generated: "2022-10-03T09:15:23.240371+01:00"
diff --git a/docs/charts/inlets-http-server-0.5.0.tgz b/docs/charts/inlets-http-server-0.5.0.tgz
new file mode 100644
index 0000000..608c08d
Binary files /dev/null and b/docs/charts/inlets-http-server-0.5.0.tgz differ
diff --git a/docs/charts/inlets-tcp-client-0.5.0.tgz b/docs/charts/inlets-tcp-client-0.5.0.tgz
new file mode 100644
index 0000000..8170866
Binary files /dev/null and b/docs/charts/inlets-tcp-client-0.5.0.tgz differ
diff --git a/docs/charts/inlets-tcp-server-0.5.0.tgz b/docs/charts/inlets-tcp-server-0.5.0.tgz
new file mode 100644
index 0000000..fd85177
Binary files /dev/null and b/docs/charts/inlets-tcp-server-0.5.0.tgz differ
diff --git a/docs/cli-reference.md b/docs/cli-reference.md
index 3a4dd65..4fb2790 100644
--- a/docs/cli-reference.md
+++ b/docs/cli-reference.md
@@ -231,7 +231,7 @@ You can use the public IP address of the inlets-server, or a DNS record.
 
 #### Use a pre-supplied, or self-signed certificate
 
-You can use a TLS certificate with the inlets PRO server obtained from a third-party tool such as [certbot](https://certbot.eff.org), or your own Public Key Infrastructure (PKI).
+You can use a TLS certificate with the inlets Pro server obtained from a third-party tool such as [certbot](https://certbot.eff.org), or your own Public Key Infrastructure (PKI).
 
 If you wanted to use an exit-server with a public IP, you can create a DNS A record for it before configuring certbot or another tool to fetch a TLS certificate for you from LetsEncrypt. If you don't want to set up a separate DNS record, then you can get an automated one from [xip.io](http://xip.io) such as `104.16.182.15.xip.io` or `104.16.182.15.xip.io`, where your public IP is `104.16.182.15`.
 
@@ -315,7 +315,7 @@ Now pass the token via `--token $TOKEN`.
 
 ### Configure a http tunnel
 
-The HTTP mode of inlets PRO is suitable for REST / HTTP traffic. Use it when you want to add TLS termination on the exit-server without running a reverse-proxy in the client's network.
+The HTTP mode of inlets Pro is suitable for REST / HTTP traffic. Use it when you want to add TLS termination on the exit-server without running a reverse-proxy in the client's network.
 
 Just like a TCP tunnel, a HTTP tunnel has two TCP ports, one for the control-plane and one for the data-plane.
 
@@ -330,7 +330,7 @@ The control-plane will use Auto-TLS by default, but the data-plane does not.
 
 #### Use Let's Encrypt to obtain a TLS certificate for the data plane
 
-inlets PRO HTTP tunnels are able to obtain TLS certificates from Let's Encrypt for the data-plane. In this mode, you'll find that the server exposes port 80 and 443 in order to process a HTTP01 challenge.
+inlets Pro HTTP tunnels are able to obtain TLS certificates from Let's Encrypt for the data-plane. In this mode, you'll find that the server exposes port 80 and 443 in order to process a HTTP01 challenge.
 
 Three additional fields enable the client to obtain a TLS certificate for the data-plane:
 
diff --git a/docs/reference.md b/docs/reference.md
index 1392a94..4561d08 100644
--- a/docs/reference.md
+++ b/docs/reference.md
@@ -1,4 +1,4 @@
-## Reference architecture for inlets PRO
+## Reference architecture for inlets Pro
 
 ### Single private service with Public VirtualIP