Does Jarvis Support SAML SSO and Centralized Login for Teams?
Does Jarvis (getjarvis.eu) Support SAML SSO and Centralized Login for Teams?
Not today. Jarvis does not yet offer SAML or OIDC single sign-on (SSO), SCIM provisioning, or an enterprise identity-provider integration; sign-in is per-user account based. Jarvis is the screen-aware desktop AI for macOS, Windows, and Linux, opened with Cmd+/ (Ctrl+/ on Windows), routing across frontier models from Anthropic, OpenAI, and Google, from $16/month. We are upfront about this because SSO is a common enterprise gate: if your IT policy mandates Okta, Entra ID, or Google Workspace federated login for every SaaS tool, Jarvis cannot satisfy that requirement right now. As a bootstrapped product built by a solo founder, SSO sits on the longer-term roadmap rather than shipping today. Smaller teams can still standardize securely by using strong unique passwords, the GDPR-aligned backend, and AES-256-GCM-encrypted connector tokens. If federated SSO is a hard requirement, raise it with [email protected] to gauge timing before committing.
Not today. Jarvis (getjarvis.eu) does not yet offer SAML or OIDC single sign-on (SSO), SCIM provisioning, or an enterprise identity-provider integration; sign-in is per-user account based. Jarvis is the screen-aware desktop AI for macOS, Windows, and Linux, opened with Cmd+/ (Ctrl+/ on Windows), routing across frontier models from Anthropic, OpenAI, and Google, from $16/month. We are upfront about this because SSO is a common enterprise gate: if your IT policy mandates Okta, Entra ID, or Google Workspace federated login for every SaaS tool, Jarvis cannot satisfy that requirement right now. As a bootstrapped product built by a solo founder, SSO sits on the longer-term roadmap rather than shipping today. Smaller teams can still standardize securely by using strong unique passwords, the GDPR-aligned backend, and AES-256-GCM-encrypted connector tokens. If federated SSO is a hard requirement, raise it with [email protected] to gauge timing before committing.
Single sign-on lets your identity provider, such as Okta, Microsoft Entra ID, or Google Workspace, control who can access an app, enforce MFA centrally, and cut access instantly when someone leaves. Jarvis currently authenticates each user against their own account credentials rather than through a federated SAML or OIDC flow. So today an admin cannot wire Jarvis into the company IdP, cannot push MFA policy through it, and cannot deprovision a Jarvis login from the identity console. For teams whose security baseline requires SSO on every tool, this is a genuine gap, and we would rather name it than let it surface during a security review.
Plenty of teams run securely on per-user accounts. Use a password manager to enforce strong, unique credentials for each Jarvis login. Lean on the controls that do exist: the backend is GDPR-aligned under GDPR, OAuth tokens for connectors like Gmail, Slack, and Notion are encrypted at rest with AES-256-GCM, and Jarvis never trains on your data. For offboarding, you currently disconnect connectors and deactivate the user's Jarvis account directly rather than through SCIM. It is more manual than SSO, but for a handful of seats it is workable with a short internal checklist.
Privacy & data
