INTEGRATIONS
Connect Collablynx to the systems that already run your enterprise.
The public catalog describes integration purpose, product applicability, authentication pattern, data direction, and availability. Exact permissions, secrets, agents, and setup commands remain protected.
INTEGRATION CATALOG
Clear categories and explicit availability labels.
A catalog entry does not imply that every connector is generally available. Confirm status, edition, region, and technical prerequisites during evaluation.
Cloud platforms
AWS
Platform scopeGoogle Cloud
Platform scopeOperating platforms
Kubernetes
Platform scopeOn-Premise
Platform scopePrivate Cloud
Platform scopeMainframe
Platform scopeIdentity and access
Microsoft Entra External ID
Identity standardOIDC
Supported standardSAML
Enterprise federation patternTelemetry and operations
OpenTelemetry
Integration patternPrometheus
Integration patternCloud-native monitoring
Environment-specific patternDocuForge AI routes
Azure OpenAI
Configuration dependentOpenAI
Configuration dependentGoogle Gemini
Configuration dependentAnthropic Claude
Configuration dependentPrivate or customer-managed models
Edition dependentCATALOG STANDARD
Every integration should answer the same nine questions.
Which Collablynx products use it?
What outcome does the integration support?
What data enters or leaves Collablynx?
Which authentication or machine identity is used?
Where is the connector deployed?
Which versions and regions are supported?
What customer permissions are required?
What is the availability status?
Where are protected setup instructions located?
Availability discipline
Integration entries use explicit availability labels so buyers can distinguish generally available capabilities from preview, planned, configuration-dependent, and customer-provided patterns.
ACCESS MODEL
The right information at the right level.
Prospects receive enough detail to evaluate the platform. Sensitive implementation and assurance material stays protected.
Buyer and evaluator resources
- Integration categories and business purpose
- Supported environment and identity standards
- General authentication and data-direction patterns
- Availability and edition labels
- Compatibility and prerequisite summaries
Implementation and assurance resources
- IAM roles, service principals, service accounts, and API scopes
- Configuration files, commands, certificates, keys, and secrets
- Agent and gateway downloads
- Webhook configuration and troubleshooting
- Organization connector inventory
NEXT STEP
Validate your integration path before purchase.
Bring your environment list to a tailored demo and confirm product, edition, identity, network, and connector prerequisites.