Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.genloop.ai/llms.txt

Use this file to discover all available pages before exploring further.

Genloop supports three deployment modes to meet different infrastructure and compliance requirements. You can start with the cloud deployment and migrate to a private deployment as your needs evolve. SSO and SAML authentication are available on the Enterprise plan for all deployment modes.

​
Deployment modes

The default deployment. Genloop is hosted and managed by the Genloop team. You connect your data sources, and Genloop handles infrastructure, updates, and scaling.Best for: Teams that want to get started immediately without infrastructure overhead.Data handling: Genloop queries your data sources directly. No enterprise data is copied or stored in Genloop’s cloud. Connections use TLS-encrypted credentials stored in Genloop’s secrets manager.No setup is required. Create your account at app.genloop.ai and connect your first data source.

​
Model agnosticism

Genloop is not tied to a single AI provider. Depending on your deployment mode, you can configure which underlying language model powers Genloop’s analysis:
  • Cloud (SaaS): Genloop uses its default hosted model. Contact the team to discuss model options.
  • VPC: You can configure outbound LLM API calls to any supported provider (e.g., OpenAI, Anthropic, Azure OpenAI).
  • Air-gapped: You bring your own model. Genloop supports open-weight models served via standard inference APIs. Your Solutions Architect will confirm which runtimes and models are supported.
Model selection does not affect Genloop’s context graph, data access controls, or RBAC configuration. These are Genloop-layer features that work the same regardless of the underlying model.

​
SSO and SAML

SSO and SAML are available on the Enterprise plan for all deployment modes.
Genloop supports SAML 2.0-based single sign-on, which lets your team log in with your existing identity provider instead of managing separate Genloop credentials. Supported identity providers include:
  • Okta
  • Microsoft Entra ID (formerly Azure AD)
  • Google Workspace
  • OneLogin
  • Any SAML 2.0-compliant provider

​
Configure SSO

1

Contact Genloop to enable SSO

SSO configuration is handled by the Genloop team during Enterprise onboarding. Contact your Solutions Architect or reach out at https://cal.com/ayush-genloop to request activation.
2

Provide your IdP metadata

Share your identity provider’s SAML metadata URL or XML file with the Genloop team. This includes your issuer URI, SSO URL, and public certificate.
3

Configure your IdP

In your identity provider, create a new SAML application for Genloop. The Genloop team will provide the required Entity ID, ACS URL (Assertion Consumer Service), and attribute mapping requirements.
4

Test the integration

Once configuration is complete, test the login flow with a non-admin account before rolling out to your full team.
5

Enforce SSO for your workspace

After a successful test, you can enforce SSO for all workspace members — disabling password-based login entirely.

​
Role auto-sync with SSO

Role auto-sync is available on Enterprise only.
On Enterprise, Genloop can sync roles from your identity provider automatically. When a member’s group membership changes in your IdP (for example, they’re added to a data-team group), their Genloop role updates automatically at next login. This eliminates manual role management and ensures access controls stay in sync with your directory. Configure the group-to-role mapping in Settings > Security > SSO after your SSO integration is live.

​
Requesting a private deployment

To discuss VPC or air-gapped deployment:
  • Book a call with the team: https://cal.com/ayush-genloop
  • Or contact your dedicated Solutions Architect if you’re an existing Enterprise customer