> 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/getting-started-with-the-platform/deployment-options/getint-saas.md).
# Getint SaaS
## Getint SaaS: Deployment & Access Guide
Getint SaaS is the standalone Getint platform hosted and maintained by Getint at [app.live.getint.io](https://app.live.getint.io/). You access it directly from your browser with a Getint account, without installing anything on your own servers or inside Jira.
The SaaS platform runs the same integration engine as the other deployment options. It is the standard choice for:
* **Data Migrations**: Migrations are not supported by the Jira Cloud (Forge) app, which is built for continuous sync only. To migrate data, create an account on [app.live.getint.io](http://app.live.getint.io/). Migrations are billed separately based on the number of items migrated.
* **Jira and Non-Jira Integrations**: Integrations created through the Getint Jira apps run on the SaaS platform, as do integrations between other supported tools.
* **Teams Without Infrastructure to Manage**: Hosting, updates, and backups are handled by Getint.
### Technical Architecture
Getint SaaS runs entirely on Getint's infrastructure and connects to your tools over their public APIs.
* **Web Interface**: You log in at [app.live.getint.io](http://app.live.getint.io/) to create connections, configure integrations, map fields, and review runs and logs.
* **Sync Engine**: Synchronization runs on Getint's servers, not inside any of the connected tools.
* **API Requests**: Getint sends authenticated HTTP requests to each connected tool to read items, write updates, upload attachments, and post comments.
* **Connections**: Each connection uses the authentication method the tool supports, such as API tokens, OAuth, or username and password.
* **Storage**: Configuration data (connections, mappings, settings) and synchronization logs are stored on Getint's infrastructure.
### Accessing the Platform
1. Navigate to [app.live.getint.io](https://app.live.getint.io/) in your browser.
2. Create a Getint account, or log in with your existing credentials.
3. At first login, set up two-factor authentication for your account (see **Account Security** below).
4. Once logged in, select **Integration** or **Migration** to get started.
### Account Security
#### Two-Factor Authentication (2FA)
Getint SaaS supports two-factor authentication using time-based one-time codes. With 2FA turned on, logging in requires your password plus a 6-digit code from an authenticator app. You are prompted for 2FA at first login and whenever you log in from an unknown browser.
Supported authenticator apps include Google Authenticator, Authy, and 1Password.
**To set up 2FA:**
1. At first login, the **Set up 2-factor authentication** screen opens.
2. In your authenticator app, add a new account and scan the QR code shown on the screen.
* If you can't scan the QR code, click **Show setup key** and enter the key manually in your authenticator app.
3. Enter the 6-digit code generated by your authenticator app in the **6-digit code** field.
4. Confirm to complete the setup. 2FA is active only after the code is verified.
{% hint style="info" %}
*Note: Codes refresh every 30 seconds. If a code is rejected, wait for the next one and check that the time on your device is set automatically.*
{% endhint %}
#### Single Sign-On (SSO)
SSO is not available on Getint SaaS. Two-factor authentication is not the same as SSO. With 2FA, you log in with credentials managed by Getint plus a code from your authenticator app. With SSO, you would log in through your organization's identity provider (such as Okta or Microsoft Entra ID).
*Customers who require SSO can contact* [*support@getint.io*](mailto:support@getint.io) *to discuss their options.*
### Security & Data Residency
* **Infrastructure**: The Getint platform is hosted on AWS (Amazon Web Services).
* **Data Isolation**: Each customer's data is stored in a separate database schema.
* **Data Handled**: Only the data needed for the integrations you configure: item data, comments, user identifiers, encrypted connection details, and instance URLs.
* **Backups**: Daily backups, retained for 30 days.
* **Updates**: Applied by Getint using a blue/green deployment technique, with no action needed on your side.
For more details, see the [Security FAQ](https://docs.getint.io/support-legal-and-others/faq/security-faq) and [Data Residency with Getint](https://docs.getint.io/support-legal-and-others/privacy-and-security/data-residency-with-getint).
### Comparison: SaaS vs. On-Premise vs. Data Center
| **Deployment** | **Getint SaaS** | **On-Premise** | **Jira Data Center (Native)** |
| -------------- | ------------------------------------------------ | ------------------------- | ----------------------------- |
| Hosting | Hosted by Getint (AWS) | Hosted on Customer Server | Hosted on Customer Server |
| Access | [app.live.getint.io](http://app.live.getint.io/) | Customer URL | Inside Jira |
| Maintenance | Managed by Getint | Managed by Customer | Managed by Customer |
| Updates | Automatic | Manual Update Required | Manual Update Required |
| Data Location | Getint infrastructure | Customer servers | Jira database and `JIRA_HOME` |
### Deployment Best Practices
* **Turn On 2FA**: Set up two-factor authentication for every account that can access your integrations.
* **Dedicated Service Accounts**: Use service accounts in the connected tools for your connections. This keeps sync activity separate from individual employees and provides a clear audit trail.
* **Filter Early**: Use filters to sync only the items you need. This reduces unwanted syncs and keeps runs fast.
* **Log Retention**: Set your log retention to match your organization's internal data privacy policies.
{% hint style="info" %}
*For organizations with restricted cloud access, Getint also offers an* [*On-Premise*](https://docs.getint.io/getting-started-with-the-platform/deployment-options/on-premise-deployment) *deployment option that can be installed on private servers behind your firewall.*
{% endhint %}
---
# 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/getting-started-with-the-platform/deployment-options/getint-saas.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.
