# Understanding Getint Licensing and Pricing
Welcome to our comprehensive guide on Getint’s licensing and payment structures. Our model is designed to be **straightforward, flexible**, and tailored to meet your integration and migration needs.
### **Integrations**
#### **Jira-Related Integrations**
We primarily distribute our apps through the Atlassian Marketplace for integrations involving Jira. We also offer a direct purchase option for customers who cannot access the Marketplace.
#### **License Per Integration**
* Each Jira integration requires a single license.
* For example:
* Integrating **1x Jira with 1x ServiceNow** requires **one license**.
* A **Jira-to-Jira integration** needs **two licenses**: one for each Jira instance. Alternatively, you can use a **regular license** for one Jira and a **remote license** for the other. Learn more [here](https://docs.getint.io/getting-started-with-the-platform/integration-synchronization/jira-jira-integration/jira-jira-licensing).
### **Why Choose Getint for Jira Integrations?**
* **Single App, Single Payment:**
Set everything up in one centralized place. Unlike Exalate and Backbone, Getint eliminates the need for additional installations or payments at both ends.
* **No Additional Synchronizers:**
Avoid the hassle of standalone synchronizers like TFS4JIRA.
* **Unlimited Synchronization:**
One license allows you to synchronize an unlimited number of projects, fields, and tasks between two instances.
*(Compare with Unito’s usage-based pricing, where costs scale with the number of integrations.)*
### **Pricing Structure**
* Pricing for Jira integrations is based on:
* **Jira version** (Cloud, Server, or Data Center)
* **User count** on the instance
Pricing adheres to Atlassian Marketplace guidelines. View our apps and pricing [here](https://marketplace.atlassian.com/vendors/1218845).
### **Non-Jira Integrations**
For tools like Asana, Azure DevOps, ServiceNow, Zendesk, Wrike, GitLab, GitHub, and Trello (without Jira involvement), we offer a **simple, fixed-fee structure**:
* **One license covers integration** between 1x Instance A (e.g., Asana) and 1x Instance B (e.g., Azure DevOps).
* No hidden costs—just seamless connectivity. Learn more about pricing [here](https://www.getint.io/pricing).
### **Special Licensing Options**
#### **Network License**
Ideal for organizations managing **multiple integrations**, such as:
* **3x Jira with 2x ServiceNow**
* **4x Asana instances**
Benefit from **special network pricing** for cost-effective scalability. [Learn more about network licenses](https://docs.getint.io/support-legal-and-others/licensing/network-license).
#### **Migrations**
Migrations are often **short-term, high-intensity projects** designed to transfer large volumes of data efficiently.
* **Pricing:** Based on the data volume being migrated, ensure value-based pricing.
* Once migration is complete, you can discontinue using the tool.
Learn more about migration pricing [here](https://www.getint.io/pricing).
### **Getting Started with Getint**
To begin, you only need:
* A license for the dedicated Jira app from the Atlassian Marketplace, or
* A direct license from Getint.
Our simple licensing approach eliminates the need for multiple app purchases or installations across different tools. With just **one platform license**, you’re ready to streamline your integrations and migrations.
Explore Getint’s **flexible, user-friendly licensing options** today and find the perfect fit for your organization. Start your integration journey with confidence!
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.getint.io/licensing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.