Skip to content

doc(sls): fees precision #5789

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 13, 2025
Merged

doc(sls): fees precision #5789

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pages/serverless-containers/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource
* **Memory consumption:** The memory consumption is obtained by multiplying the memory tier chosen by the container run duration.
* **vCPU consumption:** The vCPU consumption is obtained by multiplying the vCPU tier chosen by the container run duration.
* **Ephemeral storage:** Is free of charge, the maximum value of ephemeral storage depends on the memory value.
* **Ingress/Egress:** Is free of charge.

<Lightbox image={Image1} size={"medium"} alt={"Serverless Containers Billing"} />
<Lightbox image={Image2} size={"medium"} alt={"Serverless Containers Billing"} />
Expand Down
4 changes: 3 additions & 1 deletion pages/serverless-functions/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,8 @@ Serverless Functions is billed on a pay-as-you-go basis. Three components are ta

* **Resources provision:** in order to mitigate cold start, users can choose to keep some function instances warm (by filing the minimum scale value). We then charge for the provisioned resources similarly to the Resources consumption component.

* **Ingress/Egress:** Is free of charge.

The scheme below illustrates our billing model:

<Lightbox image={Image1} size={"medium"} alt={"Functions Billing"} />
Expand Down Expand Up @@ -293,4 +295,4 @@ In the `Serverless Functions Logs` dashboard, you will then be able to read info

### Why does my function have an instance running after deployment, even with min-scale 0?

Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum scale is set to `0`. This behavior is not configurable at this time.
Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum scale is set to `0`. This behavior is not configurable at this time.
2 changes: 1 addition & 1 deletion pages/serverless-jobs/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,4 +192,4 @@ Ongoing job runs will keep using the resources defined when they started.

Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development.

To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.
To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.