Document account spend limits and worker limits (#449)

Author: muhsinking

get-started/manage-accounts.mdx

@@ -94,6 +94,10 @@ The admin role provides complete control over all account features and settings.
 
 Administrators have unrestricted access to manage team members, configure account settings, handle billing, and control all team computing resources. This role should be reserved for team leaders and trusted members who need full account access.
 
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
 ## Monitor account activity
 
 Runpod provides comprehensive audit logs to track all actions performed within your account. This feature helps maintain security and accountability across team operations.

pods/pricing.mdx

@@ -152,6 +152,10 @@ Runpod is not designed as a long-term cloud storage system. Storage is provided
 
 When you [stop a Pod](/pods/manage-pods#stop-a-pod), you will no longer be charged for the Pod's hourly GPU cost, but will continue to be charged for the Pod's volume disk at a rate of \$0.20 per GB per month.
 
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
 ## Tracking costs and savings plans
 
 You can monitor your active savings plans, including their associated Pods, commitment periods, and expiration dates, by visiting the dedicated [Savings plans](https://www.console.runpod.io/savings-plans) section in your Runpod console. General Pod usage and billing can be tracked through the [Billing section](https://www.console.runpod.io/user/billing).

serverless/pricing.mdx

@@ -75,6 +75,10 @@ Set reasonable [execution timeout limits](/serverless/endpoints/endpoint-configu
 
 After completing a request, workers remain active for a specified period before scaling down. This reduces response times for subsequent requests but incurs additional charges. The default idle timeout is 5 seconds, but you can configure this in your [endpoint settings](/serverless/endpoints/endpoint-configurations#idle-timeout).
 
+## Account spend limits
+
+By default, Runpod accounts have a spend limit of \$80 per hour across all resources. This limit protects your account from unexpected charges. If your workload requires higher spending capacity, you can [contact support](https://www.runpod.io/contact) to increase it.
+
 ## Billing support
 
 If you think you've been billed incorrectly, please [contact support](https://www.runpod.io/contact), and include this information in your request:

serverless/workers/overview.mdx

@@ -54,6 +54,19 @@ You can view the state of your workers using the **Workers** tab of a Serverless
 
 To debug issues in production, you can access [worker logs](/serverless/development/logs) and [SSH directly into running workers](/serverless/workers/ssh-into-workers) to inspect file systems and environment variables in real-time.
 
+## Max worker limit
+
+By default, each Runpod account can allocate a maximum of 5 workers (flex + active combined) across all endpoints. If your account balance exceeds a certain threshold, you can increase this limit:
+
+- \$100 balance: 10 max workers
+- \$200 balance: 20 max workers
+- \$300 balance: 30 max workers
+- \$500 balance: 40 max workers
+- \$700 balance: 50 max workers
+- \$900 balance: 60 max workers
+
+If your workload requires additional capacity beyond 60 workers, [contact our support team](https://www.runpod.io/contact).
+
 ## Next steps
 
 * [Build your first worker.](/serverless/workers/custom-worker)