> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/technical-architecture/no-integration.md).
# No integration
The ins-pi products are native solutions designed and built entirely on the ServiceNow platform. This means that unlike other solutions, complex integrations or extensive interface administration are not required.
## Navigating the Costs of Integration
In an era where digital transformation reigns supreme, the selection of your solutions holds the power to either propel or hinder your transformative journey. While the allure of integrating with ServiceNow is undeniable, it conceals a labyrinth of uncertainties and risks.
Integrating external tools with ServiceNow demands a repetitive cycle of adjustments and configurations, culminating in amplified complexity, escalated administrative burdens, heightened expenses, and a significant peril to data consistency. Additionally, staying current with updates and other alterations mandates frequent reconfiguration, compounding the challenge.
The diagram illustrates how YouDesign is natively built on ServiceNow as the "single source of truth." Through the Integration Hub, other tools can be connected via an API. However, to successfully integrate these tools, configurations must be done three times: within ServiceNow, for integrations, and within the external tool themselves.
***
## Effort Comparison
This chart illustrates the contrast in effort between integrated tools and ins-pi solutions, which are exclusively built on the ServiceNow platform.
***
## 100% Built on ServiceNow
Natively built on the ServiceNow platform, YouDesign transcends these integration woes. Say goodbye to complexity, resource drain, and maintenance nightmares. Enjoy data security, compatibility assurance, and a superior user experience, all without the shackles of vendor lock-in.
---
# 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.ins-pi.com/technical-architecture/no-integration.md?ask=&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.
