Network as a Service
Adjust connectivity as projects change.
Network as a Service (NaaS) manages eligible services through a portal or Application Programming Interface (API). It suits recurring changes; check ports, capacity and cost.
On-demand availability depends on compatible buildings, ports, products and ecosystems.
Let’s talk
How it works
Adapt connectivity to business needs while retaining control of each change.
Portal / APIManagement: configures the serviceCreate and verify
Available ports
Configured serviceThe portal configures the connection; user traffic flows through the service.
From a port to a working connection
Select eligible locations and ports, then define Ethernet, Internet or cloud service. The request configures a logical connection on available infrastructure.
A site without prepared access still needs provisioning. After a change verify state, capacity and real traffic: submitting an order does not prove the service works.
Portal / APIManagement: configures the serviceAdjust capacity
Available ports
Configured serviceThe portal configures the connection; user traffic flows through the service.
Capacity under control
For a migration or peak, check whether the connection supports a capacity change and for how long. Physical port and contracted profile set the limits.
Agree permissions, approval and cost monitoring. Before-and-after measurements avoid paying for an upgrade when the bottleneck lies elsewhere.
Portal / APIManagement: configures the serviceReconcile state
Available ports
Configured serviceThe portal configures the connection; user traffic flows through the service.
An uncertain request is not blindly repeated
If the portal or API does not confirm the result, check order and service state before retrying. A management failure does not mean traffic has stopped.
Define escalation, rollback and change evidence. Traffic resilience is designed through access and paths, not automation alone.
Illustrative case: from situation to decision
- Situation
- A migration needs extra capacity during a defined window.
- Option
- Prepare ports and permissions, increase an eligible connection and plan the return.
- Check
- Measure traffic before and after, confirm the order and review the cost for that period.
Portal agility does not remove physical installation, eligibility, port limits or commercial conditions.
Decisions for your project
- Eligibility and limits
- Available locations, ports, connection type and capacity.
- Change governance
- Approval, execution, duration and cost control.
- Verification and recovery
- Order state, traffic tests and rollback plan.
From design to operation
Prepare ports, permissions and a verifiable pilot change before automating recurring operations.
Complements, alternatives and variants
Product sources
What challenge would you like to solve?
Tell us what is happening and what needs to change. You do not need to know the catalogue.
What happens next?
- Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
- Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
- Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.
ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.
Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.