From c598bf38fbef8b868881ff6fa8587f839cad56a4 Mon Sep 17 00:00:00 2001 From: "Alex Ellis (OpenFaaS Ltd)" Date: Thu, 3 Oct 2024 10:38:02 +0100 Subject: [PATCH] Mention SaaS ToS issues in FAQ Signed-off-by: Alex Ellis (OpenFaaS Ltd) --- docs/reference/faq.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/reference/faq.md b/docs/reference/faq.md index df0876b..bb95e6e 100644 --- a/docs/reference/faq.md +++ b/docs/reference/faq.md @@ -19,11 +19,12 @@ Are you curious about the advantages of using inlets vs. alternatives? We must f SaaS tunnels provide a convenient way to expose services for the purposes of development, however they are often: +* subject to overreaching terms of service, including licensing your content, censoring, and monitoring your traffic for violations * blocked by corporate IT * running on shared infrastructure (servers) with other customers * subject to stringent rate-limits that affect productivity * priced per subdomain -* unable to obtain high value TCP ports like 22, 80, 443 and so on +* unable to offer standard TCP ports like 22, 80, 443, etc You run inlets on your own servers, so you do not run into those restrictions. Your data remains your own and is kept private.