Overview 💥
This article explains how Liongard integrations are structured and clarifies whether multiple integrations of the same type can be created within a single Liongard instance.
Liongard supports multiple integrations overall, but only one integration per integration type (platform) is allowed within a single Liongard instance.
How Liongard Integrations Work 🤔
Each Liongard instance can connect to multiple external platforms; however, there is a one-to-one relationship per integration type.
Supported Model
Liongard Instance | Integration Type | Status |
Liongard → IT Glue | One IT Glue instance | ✅ Supported |
Liongard → ConnectWise PSA | One ConnectWise instance | ✅ Supported |
Liongard → Autotask | One Autotask instance | ✅ Supported |
Liongard → Multiple different platforms | One per type | ✅ Supported |
Not Supported
Scenario | Status |
One Liongard instance → two ConnectWise PSA instances | ❌ Not Supported |
One Liongard instance → two IT Glue instances | ❌ Not Supported |
One Liongard instance → multiple instances of the same platform | ❌ Not Supported |
Why This Limitation Exists? 🧐
Liongard enforces this limitation by design for several important reasons:
Reason | Explanation |
Data integrity | Prevents conflicts and duplication between identical platform types |
Mapping consistency | Ensures predictable configuration, environment, and asset mappings |
Inspector reliability | Inspectors rely on a single authoritative source per platform |
Alert accuracy | Reduces false positives caused by overlapping data sources |
Platform stability | Simplifies integration lifecycle management |
This architecture ensures consistent, reliable, and supportable integrations across environments.
Common Use Case Scenarios 🧑🏫
Scenario 1: Multiple Different Platforms (Supported)
Example:
One ConnectWise PSA
One IT Glue
One Autotask
✅ This is fully supported within a single Liongard instance.
Scenario 2: Multiple Instances of the Same Platform (Not Supported)
Example:
Two separate ConnectWise PSA instances
Two separate IT Glue instances
❌ This is not supported within a single Liongard instance.
How to Handle Multiple Instances of the Same Platform 👨💻
If your organization needs to connect to multiple instances of the same integration type, the recommended approach is:
Use Multiple Liongard Instances:
Requirement | Recommended Solution |
Multiple ConnectWise PSA instances | Separate Liongard instance per PSA |
Multiple IT Glue instances | Separate Liongard instance per IT Glue |
MSP with segmented tenants | Multi-instance Liongard architecture |
Recommended Next Steps for Multi-Instance Needs 🚀
If you believe your environment requires multiple instances of the same integration type:
Contact your Liongard Account Manager.
They can help assess your architecture
Provide guidance on best practices for multi-instance deployments
Review licensing and data segmentation needs.
Plan Inspector and alert distribution accordingly.
This ensures scalability without compromising data accuracy or platform stability.
When to Contact Support 🦁
Contact Liongard Support if:
You are unsure whether your use case requires multiple Liongard instances.
You are planning a migration or consolidation.
You need help understanding integration limitations.
You encounter errors while attempting to add an integration.
Best Practices 🌟
Best Practice | Benefit |
One integration per platform type | Maintains clean data relationships |
Use dedicated API accounts | Prevents authentication conflicts |
Engage Account Management early | Avoids rework and architectural changes later |
Keep integrations minimal and intentional | Improves Inspector performance and alert quality |