Sovereign access—Join the waitlist →
WIPVerified 2026-10-20

Authentication

How external integrations will authenticate with OVAITY.

Status: WIP

Public partner authentication for API, SDK, and MCP access is being finalized.

Product users (today)

Researchers and collaborators sign in through the OVAITY web application with email and password. New accounts join by invitation. Public self-serve signup is closed. Role-based permissions control what they can see and do inside organizations, labs, and projects.

Partner integrations (coming)

We are designing dedicated credentials for external systems so partners do not reuse end-user browser sessions. Expected patterns:

IntegrationPlanned auth model
Public APIPartner credentials / API keys or OAuth (final model TBD)
SDKSame credentials as the public API
MCPNot available. Remote MCP is not a partner integration.

There is no self-serve API-key program. Partners cannot create API keys themselves. Exact onboarding steps will be published here only if a public API ships.

Need access now?

During private beta, integration access is provisioned case by case. Contact us or apply for the OVAITY Beta.