> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/on-demand/on-demand-lso-portal.md).

# ON DEMAND LSO PORTAL

## LIFECYCLE SERVICE ORCHESTRATION PORTAL 

{% hint style="info" %}
This section is specifically for customers who want to benefit from a “quote centric” NaaS model. Customers who want to benefit from a “buy it now” experience, please refer to the main sections of the On Demand Knowledge Centre
{% endhint %}

To address customer’s distinct needs, Colt now offers two complementary digital experiences: the existing **On Demand portal**, designed for instant, on‑demand purchasing, and a newly launched **On Demand Lifecycle Service Orchestration (LSO) portal** that enables customers to create, store, and later convert quotes into orders. 

Colt’s Lifecycle Service Orchestration (LSO) portal enables customers to benefit from a NaaS-based experience via a traditional “quote centric” model. 

The LSO portal is built on the **Mplify Sonata API**, enables API generated quotes to be converted to portal driven orders (and vice versa) and offers a future path to full Mplify API adoption.  

|                       | Default On Demand/NaaS portal                                                                                               | LSO portal                                                                                                                                                    |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Main use case**     | Customers who want a “buy it now” experience & NaaS based flexibility                                                       | Customers who operate traditional “quote based” procurement                                                                                                   |
| **Target customers**  | Enterprises (all sizes)                                                                                                     | Wholesale carriers, larger enterprises                                                                                                                        |
| **Commercial model**  | A choice between shorter contract terms & multi-year contracts                                                              | Fixed multi year contracts                                                                                                                                    |
| **API compatibility** | <p>Colt’s own “SDN” API  </p><p>(for bandwidth flexing, etc.) </p>                                                          | <p>Industry standard Mplify API  </p><p>(with quote/order compatibility) </p>                                                                                 |
| **Product support**   | <p><strong>Today:</strong> </p><p>Ethernet spoke  </p><p>Ethernet Line (P-P) </p><p>Cloud (DCA) </p><p>DIA (IP Access) </p> | <p><strong>Today:</strong> </p><p>Ethernet spoke  </p><p><strong>Tomorrow:</strong> </p><p>Ethernet Line (P-P) </p><p>Cloud (DCA) </p><p>DIA (IP Access) </p> |
| **Product model**     | Separate access ports & circuit connections                                                                                 | Circuit connections                                                                                                                                           |

&#x20;

&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.colt.net/on-demand/on-demand-lso-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.