OpenConnector
An authorization gateway for AI agents, maintained by the OOMOL team, that connects business apps and checks access for tool calls.
Cloud encryption, controlled app access, and open-source components help protect the work you entrust to OOMOL.
Personal data protection is part of how we build and operate OOMOL.
OOMOL has passed TAC Security’s CASA/ESOF security assessment.
OOMOL follows the personal data protection requirements of the General Data Protection Regulation (GDPR). Our privacy policy explains data processing, your rights, and how to submit a privacy request.
Read the Privacy PolicyOOMOL uses envelope encryption to protect sensitive data in the cloud, with separate layers for encrypting data and protecting encryption keys.
A data encryption key encrypts the data into ciphertext.
A separate key encrypts the data encryption key, forming the two layers of envelope encryption.
Administrators connect business accounts and define available operations. OOMOL calls apps within the authorized scope, so members do not need to handle account passwords or raw tokens.
We maintain OpenConnector and make OO-CLI and Connector SDK source code available for developers to inspect, review, and improve.
OpenConnector uses the Apache 2.0 license. The current public OO-CLI and Connector SDK repositories use the MIT license.
An authorization gateway for AI agents, maintained by the OOMOL team, that connects business apps and checks access for tool calls.
Our open-source client-side CLI lets developers inspect the code that runs on their devices.
Our open-source connector development SDK lets developers review connector implementations and contribute improvements.
Contact us about security requirements, compliance materials, or a potential vulnerability. Avoid including passwords, tokens, or personal data in your first message.
Contact the TeamManage which optional storage OOMOL can use. You can change these choices from the footer at any time.