> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/licensing/network-license.md).

# Network License

The Getint Network License is built for organizations that synchronize four or more applications or instances. It fits businesses that deliver services across multiple platforms and work with a broad range of third-party companies.

### Who It Is For

The Network License is a good fit for:

* Software development firms
* Marketing agencies
* UX/UI design studios
* Support service providers
* Any organization that serves multiple third-party companies

### What It Covers

A standard license connects a single pair of tools. The Network License goes beyond one-to-one integrations and lets you connect multiple tools or instances in one setup. For example, you can link several Jira instances to several Azure DevOps instances.

{% hint style="info" %}
The Network License is not unlimited. It is scoped to your organization's integration needs, giving you room to create and manage multiple integrations across your tools.
{% endhint %}

### How to Get It

If your organization needs to connect four or more tools or tool instances, contact us at <support@getint.io>. We will review your integration requirements and define a license scope that matches them.

<figure><img src="https://4106311246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MR6Z9V8zLATPQPOGSDf%2Fuploads%2F9OSEDBl869gRue9mQAwv%2FGetint%20Yellow%20Banner.png?alt=media&amp;token=9cc42142-6e48-4931-8fd5-cbf7dcf4cdc1" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team
">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>


---

# 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.getint.io/licensing/network-license.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.
