Skip to content

Become a Partner ​

Build and deliver IAM solutions on an open-source foundation designed for long-term maintainability and interoperability.

The Wren Security partner ecosystem is open to system integrators, IAM consultants, and solution providers delivering Wren Security-based solutions for their clients.

Benefits of Partnership ​

Wren Security provides a modular, standards-based IAM platform without commercial licensing barriers or vendor lock-in.

For implementation partners, this creates a foundation for building repeatable architectures while maintaining flexibility over solution design, integration, and long-term client relationships.

Open-Source Foundation

Wren Security components are freely available and built on established identity standards, including OAuth 2.0, OpenID Connect, SAML, and LDAPv3.

Flexible Delivery Model

Solutions can be designed around specific client requirements without dependency on commercial licensing models.

Technical Collaboration

Architecture discussions, implementation guidance, and technical support are available when deeper platform expertise is useful.

Roadmap Visibility

Partners can stay closer to the development of Wren Security and provide technical feedback based on real implementation experience.

How Partnership Works ​

Wren Security partnerships are built around practical collaboration and the needs of individual partners and projects.

Partners can work with the team behind Wren Security on architecture, implementation questions, migrations, and other technical topics where deeper platform expertise is useful.

The scope of collaboration develops according to each partner's experience, client projects, and involvement with Wren Security.

Partner Profile ​

Partnership is intended for organizations with experience in identity and access management, system integration, security architecture, or related enterprise technologies.

Relevant experience with Wren Security is valuable, while broader IAM expertise and the ability to design, deliver, and maintain production environments are equally important.

How Collaboration Starts ​

  1. 01

    Start the Conversation

    A first discussion covers IAM experience, typical client projects, and the intended use of Wren Security.

  2. 02

    Explore the Technical Fit

    Relevant Wren Security components, architecture considerations, and areas where technical guidance may be useful are discussed.

  3. 03

    Work on Real Projects

    Collaboration can continue around evaluations, architecture design, implementation, migration, or production deployment as needed.

  4. 04

    Stay Connected

    Partners can share implementation feedback, discuss technical developments, and stay connected to the evolution of Wren Security.

Partnership inquiries are handled by Orchitech, the core maintainer of Wren Security. Wren Security remains open source; source code, documentation, and community resources remain publicly available.

Though Wren Security suite originated with open-source code that ForgeRock™ had previously released, we are not affiliated with ForgeRock™ in any way. Our projects are based on the very latest code from what was available under a CDDL license (OpenAM 13.5+, OpenDJ 3.5+, OpenIDM 4.5+, and OpenIG 4.0+).