Talk to a specialist

VLSM.io SCALABILITY

Connectivity thatgrows with youroperation.

From 1 Mbps to multiple 100 Gbps links. Size your infrastructure to match your project requirements.

Globe with data flows and connected servers

PLANNED GROWTH

More capacity, at the pace of your business.

Align network capacity, addressing, and delivery with your application.

Capacity planning

Define bandwidth, connection volume, and addressing requirements.

Expansion

Plan resource increases as your operation grows.

Continuity

Consider redundancy and monitoring in your infrastructure design.

One egress family per service.

Delivery tailored to your infrastructure.

Choose a delivery method based on your project’s technical requirements.

Server racks with cyan and green lighting in a datacenter

Inside or outside our datacenters, depending on the contracted delivery method.

Let’s plan your next step.

  1. 01Understand demandDestinations, volume, and concurrency.
  2. 02Define the architectureIP family, delivery, and capacity.
  3. 03Plan expansionTrack metrics and adjust resources.
Explore the technical planning criteria

Understand demand before increasing capacity

Scaling an operation starts with understanding the work it needs to perform. List the systems it accesses, its busiest periods, the volume of data it moves, and the time available to complete each workflow. An application that looks up small records throughout the day has a different profile from one that transfers large files within a short window. The number of tasks alone does not describe the network requirement. Also consider response size, connection duration, and concurrency across processes. This assessment lets your team discuss capacity using the application's actual behavior as a reference. Record a baseline before expanding: traffic utilization, response times, errors, and completed tasks. Compare similar periods, including normal peaks in activity. These observations help explain what needs to improve and assess whether a proposed change addresses the problem you have identified. VLSM.io uses the requirements you provide to help size connectivity for the project, with the scope and delivery conditions defined during planning.

Network capacity and application performance

The scalability offering ranges from 1 Mbps to multiple 100 Gbps links, according to the project's design and conditions. This describes network capacity; it does not promise a specific number of lookups per second. Results also depend on the client, processing, storage, and destination behavior. Size the network and application together while keeping those measurements distinct. A task queue may grow even when bandwidth remains available if another component is limiting processing. Likewise, increasing concurrency may raise resource consumption without improving workflow completion. Before requesting additional resources, identify where time is being spent and which limits are being reached. Define the initial capacity, the headroom you want to maintain, and the signals that should trigger a review. The proposal should document the expected delivery and the requirements for using it. A commercial capacity range should not be interpreted as guaranteed application performance under every workload, at every destination, or across every component in your environment.

Choose the egress family and integration method

Each VLSM.io connectivity solution uses one Internet egress family. An IPv4 service provides IPv4-only egress, while an IPv6 service provides IPv6-only egress. There is no dual-stack delivery. If your application must reach destinations in both families, plan separate services and define which service handles each workflow. Expanding capacity does not change this characteristic of the service agreement. With IPv6 Proxy, the application connects to an IPv4:Port ingress endpoint, while the proxy communicates with the Internet exclusively through IPv6. That ingress address must not be confused with an alternative IPv4 egress path. Validate compatibility across every destination involved in the workflow, including authentication, lookups, and downloads. Record the decision in application configuration and support procedures. This prevents a compatibility failure from being mistaken for insufficient bandwidth and keeps the team clear about which service supports each integration. Choose the family according to the actual requirements of the systems being accessed, rather than assuming that one service includes both.

Match delivery to your company's environment

The delivery method must make sense for the team operating the integration. IP Proxy HTTP, SOCKS5, SOCKS5H, and SOCKS5 UDP address the needs of compatible clients; VXLAN, GRE, cross-connect, VM, and bare metal form part of infrastructure designs defined for the project. These options are not interchangeable, and their inclusion does not imply that every method is available at every location. Explain where your application is hosted, which systems or equipment you manage, and which protocols you need. For external environments, assess how the connection reaches VLSM.io infrastructure. For environments hosted in the datacenters, clarify the resources involved and who is responsible for each component. Document the contracted method, integration points, and change procedures. A clearly defined delivery simplifies implementation and helps distinguish application issues from access or infrastructure issues. Before expanding, confirm whether the complete path can support the planned capacity and identify which changes your team needs to prepare in advance.

Size addressing, sessions, and concurrency

Available bandwidth, address quantity, and simultaneous connections are separate planning considerations. Assess each one according to your application's workflow. One project may need a stable origin to maintain sessions, while another needs requests distributed across egress addresses. With static proxies, the outbound address remains fixed. With rotating proxies, changes follow the configured interval in minutes. With random proxies, the egress address changes for each new request. The application keeps the same ingress endpoint according to the service configuration. The egress family remains exclusively IPv4 or exclusively IPv6, depending on the contracted solution. Also define concurrency limits, queue management, and failure handling. Adding addresses does not automatically increase the workload that a destination system permits. Planning should support predictable operation, with control over the work being sent and the results being received. Test how your client's sessions and connections behave before expanding a workflow across the environment, and keep those integration requirements documented for future changes.

Plan continuity alongside growth

Organized growth also requires assessing the impact of interruptions and changes. Identify the essential workflows, how long they can wait, and which dependencies must be available for them to finish. Consider redundancy and monitoring in the infrastructure design according to the contracted scope. Additional capacity alone does not remove single points of failure or replace recovery procedures. Document who monitors the operation, which information should be collected during an incident, and how the team resumes interrupted tasks. When changing capacity or delivery, agree on an implementation window and validation criteria. Keep a reference of the previous configuration and define how to stop the change if it does not achieve the expected result. The goal is to make expansion an understandable process for every team involved. Availability commitments, responsibilities, and support conditions should be clear in the proposal rather than inferred from an illustrative design on the website or from the size of the capacity being discussed.

Track metrics and expand in stages

A useful expansion should produce an outcome the team can observe. Compare the new configuration with the initial baseline using similar periods and workloads. Track network utilization, workflow completion times, queue growth, and error frequency. If a change does not improve the selected indicator, investigate other dependencies before continuing to add resources. Whenever possible, start with a representative part of the operation and expand after validating its behavior. This approach makes the effect of each adjustment easier to identify and improves communication between development and infrastructure teams. Review requirements periodically, especially when adding destinations, customers, or new workflows. Record decisions and the reasons behind each capacity increase. That history helps anticipate future needs without treating every temporary variation as a permanent requirement. Scalability should follow the business through deliberate planning while preserving the egress family and delivery conditions defined for each service. Use the review to decide what to maintain, what to adjust, and what needs further investigation.

Prepare the information needed to size your project

To start a conversation with a specialist, describe the application's purpose, the environment where it runs, and the destinations it needs to reach. Include the required egress family, current volume, peak periods, and expected growth. For proxy integrations, identify the client being used and the session behavior you need. If the project involves tunnels or dedicated infrastructure, explain which components your team manages and which resources you intend to contract. You do not need every answer in advance: a consistent initial assessment is enough to organize the next checks. Use that information to assess capacity, delivery method, and implementation stages. Record the agreed conditions and confirm requirements before activating changes. VLSM.io provides connectivity to support the operation's development through project-oriented planning. The agreement should make clear what will be delivered, how the application will use the service, who will validate the integration, and when the team should reassess capacity as the operation evolves.