We’re selecting 1–3 organizations to help define the future of identity operations.

An early enterprise customer that works directly with GSC Identity to apply Mission Control Identity OS™ to a real, measurable identity problem. Together we define the use case, establish a baseline, run a focused proof of concept, measure the outcome, and decide on the path to production.

A beta program typically gives many users early access in exchange for general feedback. This program is selective, paid, and structured: each engagement has a defined scope, timeline, baseline, success criteria, deliverables, and decision point, and GSC Identity works directly with each partner. Mission Control is published on Microsoft Marketplace; the program is about proving measurable value on a specific use case, not testing an unfinished product.

Yes. The Founding Design Partner engagement is a paid, outcome-driven proof of concept. Pricing and scope are determined after the qualification and discovery process, and founding partners receive preferential commercial terms, subject to the final agreement.

One to three. We are deliberately limiting the program so that GSC Identity can work directly and closely with each organization.

Healthcare organizations, government agencies, higher-education institutions, regulated enterprises, managed service providers, and identity or cybersecurity consulting firms — particularly those where identity complexity is already creating measurable cost, risk, delay, administrative burden, or limited visibility.

No. Applications are reviewed for organizational fit, the nature of the identity challenge, sponsorship, readiness, and the potential for measurable outcomes. Only qualified applicants will be contacted for the next stage, and only one to three organizations will be selected.

A meaningful identity problem; an executive sponsor or empowered champion; the relevant stakeholders and workflow knowledge; approved access, sample data, integrations, or technical support for the agreed scope; regular working sessions and candid feedback; budget for a paid proof of concept; and the ability to complete legal, security, privacy, and procurement reviews.

Discovery and use-case definition, baseline analysis, implementation guidance, direct engagement with GSC Identity leadership and product experts, measurement against the agreed success criteria, an agreed avenue for roadmap feedback, and a documented production recommendation at the end of the engagement.

Yes, within defined limits. Partners provide structured input on the capabilities relevant to their use case and receive priority consideration for selected roadmap requirements. Roadmap decisions remain with GSC Identity.

No. Roadmap influence does not mean roadmap control, guaranteed feature development, or exclusivity. Any commitment to specific functionality would need to be agreed explicitly in writing as part of the engagement scope.

Through the formal agreement. Before any proof of concept begins, security, privacy, confidentiality, data-handling, and intellectual-property terms are agreed in writing, and the approved scope defines which systems and data are involved and how access is granted. Participation does not mean surrendering ownership of your organization’s confidential information. The initial application should contain no confidential information at all.

No. Mission Control is published on Microsoft Marketplace, which some organizations prefer for procurement, but the program is open to organizations running any combination of identity platforms — including SailPoint, Okta, CyberArk, ServiceNow, and custom workflows.

We review the evidence together against the agreed baseline and success criteria. The outcome is a decision: stop, refine the use case, extend the engagement, or proceed toward a production deployment under a separate agreement.

Possibly, but only if you want to. Any case study, reference, logo use, or co-marketing requires your separate written approval and is never a condition of participation.

Credentials, API keys, tenant or directory IDs, hostnames or IP addresses, architecture diagrams, security findings, personal data about employees or customers, and any confidential, regulated, privileged, or export-controlled information. Describe the challenge at a business level; specifics come later, under a formal agreement.