You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/projects-docs/pages/learn/credit-usage/controlling-usage.mdx
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,27 +17,36 @@ Making Devboxes private allows workspace admins to have finer control over total
17
17
18
18
## Templates
19
19
20
-
VM runtime for templates is covered by CodeSandbox. By setting a Devbox as a template, you can share your work without worrying about the costs associated with non-workspace users running your Devbox.
21
-
Once a Devbox is in a template state, it cannot be edited. If you want to continue making changes to the Devbox, you will need to switch it back out of template mode.
20
+
VM runtime for templates is covered by CodeSandbox. By setting a Devbox as a template, you can share your work without worrying about the costs associated with non-workspace users running your Devbox.
21
+
Once a Devbox is in a template state, it cannot be edited. If you want to continue making changes to the Devbox, you will need to switch it back out of template mode.
22
22
23
23
## VM settings
24
24
25
-
Each workspace has a range of VM sizes to choose from. The range of options varies depending on the subscription tier of the workspace.
25
+
Each workspace has a range of VM sizes to choose from. The range of options varies depending on the subscription tier of the workspace.
26
26
By default, all Devboxes and repositories will run on [Micro](/learn/credit-usage/credits). The default VM size can be changed on the VM [settings page](https://codesandbox.io/t/vm_settings) in the workspace portal.
27
27
28
28

29
29
30
-
Individual Devboxes or repositories can be set to run on VMs other than the default.
30
+
Individual Devboxes or repositories can be set to run on VMs other than the default.
31
31
To set the VM of a Devbox or repositority, you can create a rule. This helps ensure that heavy compute projects get the power they need without increasing VM usage across the other projects.
32
32
33
33

34
34
35
+
## VM Hibernation
36
+
37
+
Each individual VM can be manually hibernated at any time from the editor:
38
+
39
+
1. Click the CodeSandbox icon at the top left.
40
+
2. Click "Hibernate VM".
41
+
42
+

35
43
36
44
## Spending limit
37
-
On-demand credits will never exceed the spending limit.
45
+
46
+
On-demand credits will never exceed the spending limit.
38
47
Once subscription credits are used, the VMs will start running on on-demand credits. These credits will be aggregated and added to the end-of-month invoice.
39
48
40
-
Every Pro workspace is required to have a maximum spending limit to ensure that there are no surprise bills at the end of the billing cycle.
41
-
The spending limit is initially set during the Pro subscription check-out flow. Workspace admins can adjust this spending limit in the workspace portal at any time.
49
+
Every Pro workspace is required to have a maximum spending limit to ensure that there are no surprise bills at the end of the billing cycle.
50
+
The spending limit is initially set during the Pro subscription check-out flow. Workspace admins can adjust this spending limit in the workspace portal at any time.
42
51
43
-
Once the on-demand credits hit that limit, all Devboxes and Repositories will enter a [frozen state](/learn/plans/pricing-faq#my-devbox-or-repository-is-frozen-what-does-that-mean) until more credits have been added or the next billing cycle begins.
52
+
Once the on-demand credits hit that limit, all Devboxes and Repositories will enter a [frozen state](/learn/plans/pricing-faq#my-devbox-or-repository-is-frozen-what-does-that-mean) until more credits have been added or the next billing cycle begins.
0 commit comments