Skip to Content
We are conducting a survey to learn how startups, SMEs, developers, and technical teams currently host, deploy, and operate software. Take the survey
Infralane
Infralane
Resource poolsCreate a resource pool

Create a resource pool

Create a pool before deploying your first application. You must have an active project and permission to create billable resources.

Open the creation page

Select Resource Pools in the dashboard, then select Create resource pool.

Name the pool

Enter a clear name that describes its purpose or environment. The name should help teammates make the right selection during deployment.

Choose CPU

Select the CPU option that can handle the combined work expected from applications in this pool. The dashboard shows the monthly price of each option.

Choose memory

Select memory based on the applications’ normal working set plus headroom. Memory is presented in customer-friendly units in the selector and summary.

Choose storage

Select enough storage for application needs, persistent data, and expected growth. Do not use persistent application storage as your only backup of important data.

Choose a region

Choose from the regions currently presented by the dashboard. Consider where your users are, where dependent services are, and any organizational requirements that apply to your data.

Review the estimate

Verify the pool name, CPU, memory, storage, region, and estimated monthly total. The dashboard’s current estimate is authoritative.

Create the pool

Select Create resource pool once. The dashboard returns to the pool list while provisioning continues. Watch the status until it becomes active.

If the page appears slow after submission, do not immediately submit again. Check the resource pool list first. Provisioning can continue after you leave the creation page.

Creation problems

  • Project context is missing: select an active project and reopen the form.
  • A specification is unavailable: choose from the options currently shown; availability can vary.
  • Creation fails: keep the exact customer-facing error message and pool name, then contact support. Do not send passwords, tokens, or secret application values.
Last updated on