docs(srv): add faas

Author: SamyOubouaziz

pages/serverless-functions/how-to/use-private-networks.mdx

@@ -91,4 +91,4 @@ This must be carried out from the VPC section of the console. Follow the procedu
 
 ## Private Networks and functions limitations
 
-For more information on limitations when using Private Networks with Serverless Functions, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-limitations/#private-networks-and-virtual-private-cloud-vpc).
+For more information on limitations when using Private Networks with Serverless Functions, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/).

pages/serverless-functions/reference-content/functions-limitations.mdx

@@ -66,21 +66,7 @@ Due to potential abuse (spam), no outbound traffic is allowed through following
 
 ## Private Networks and Virtual Private Cloud (VPC)
 
-### Usage
-
-- Functions in the same namespace can be attached to different Private Networks.
-
-- Attaching Serverless Functions to Private Networks does not entail additional cost.
-
-### Compatibility
-
-Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information.
-
-### Limitations
-
-- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-functions-namespace/#creating-a-serverless-functions-namespace), and cannot be updated afterward.
-
-- Only one Private Network can be attached to a function.
+Refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/) on VPC and Serverless Functions integration for more information.
 
 ## Versioning and rollback
 

pages/serverless-functions/reference-content/functions-private-networks.mdx

@@ -0,0 +1,34 @@
+---
+title: Serverless Functions and Private Networks integration
+description: This page contains details on how Serverless Functions interacts with Virtual Private Cloud and Private Networks
+dates:
+  - posted: 2025-08-04
+  - validation: 2025-08-04
+---
+
+## Compatibility
+
+Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information.
+
+## Features
+
+- Functions in the same namespace can be attached to different Private Networks.
+- Both [sandbox](/serverless-functions/concepts/#sandbox) environments (`V1` and `V2`) are compatible with Private Networks.
+- Attaching Serverless Functions to Private Networks **does not entail additional cost**.
+- **Egress** (outbound private traffic from a function to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be through the public endpoint of the function.
+- All DNS resolution is done through the Private Network (using the VPC DNS server `169.254.169.254`), which allows to resolve `*.internal` records.
+
+## Quotas
+
+Refer to the [dedicated documentation](/organizations-and-projects/additional-content/organization-quotas/) for more information on Private Networks quotas for Serverless Functions.
+
+## Limitations
+
+- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-functions-namespace/#creating-a-serverless-functions-namespace), and cannot be updated afterward.
+- Only one Private Network can be attached to a Serverless Container.
+- **VPC routing** (custom routes and cross-PN automatic routing) is not supported yet.
+- **Ingress** (inbound private traffic from resources to a function within the same Private Network) is not supported yet.
+- Each [function instance](/serverless-functions/concepts/#instance) has a unique IP automatically assigned by Scaleway in the Private Network. This implies the following:
+    - Users **cannot preemptively book an IP** with [IPAM](/ipam/), and reference it in the attachment.
+    - A single Serverless Container can have a **large number of IPs** being used within the Private Network, depending on the number of concurrent instances.
+    - **Cold-starts are slightly longer** due to the additional steps required to attach the node to the Private Network and book an IP.