About resource pools
A resource pool is the capacity boundary for one or more applications. It combines CPU, memory, storage, and region into a single resource that applications can share.
Bring your own server first
Connect a dedicated Linux VPS to create a resource pool from the server you already own. Infralane management is free, with no trial expiry. Applications share that server’s available capacity. Your hosting provider bills its own fees directly.
Optional Infralane-hosted pools are still available as a paid alternative. Current hosted quotes appear in the dashboard before purchase.
Included bandwidth
Every hosted resource pool includes 5 TB of bandwidth per month, shared by the applications in that pool. This allowance is monthly data transfer, not a connection speed or a separate 5 TB allocation for every application. Customer-owned servers follow their own hosting provider’s bandwidth terms. Contact support before exceeding the allowance; additional service or charges must be agreed in advance.
Why pools matter
Applications need somewhere to run. Connect a server once and place compatible applications inside its pool. This makes shared capacity and cost easier to understand.
The pool list shows each pool’s name, region, capacity, status, and creation details. Open a pool for its overview, usage or metrics view, and settings that are currently available.
Pool status
| Status shown | Meaning | Recommended action |
|---|---|---|
| Pending / Provisioning | Creation is still in progress | Wait and refresh; do not create a duplicate immediately |
| Active | The pool is ready for applications | Select it during application deployment |
| Inactive | The pool is not currently available for normal workloads | Check the pool details and contact support if unexpected |
| Error / Failed | Creation or a later operation did not complete | Read the message, retry only when offered, or contact support |
Shared capacity
Each application receives a CPU and memory allocation from its selected pool. The sum of planned workloads should fit within pool limits, including room for traffic peaks and safe deployments.
Persistent volumes belong to application runtime configuration, while the pool supplies the overall storage capacity. Avoid allocating every last unit of capacity to normal traffic; leave headroom for growth and operational recovery.
Connecting your own server does not charge the Infralane wallet. Purchasing or resizing an optional hosted pool affects billing; review its complete configuration and charge in the dashboard first.
Naming pools
Choose names that help teammates identify intent, such as production-east, staging, or shared-services. Do not include account numbers, credentials, customer records, or other sensitive data.