One account boundary for client access across Gopsco services and future Vyoma tenants, with or without a managed domain.
Gopsco Identity is the shared access surface for sign-in, signup, verification, recovery, and role-aware session handling. It is live on the current Gopsco runtime now, with broader tenant and federation layers staged as later expansion instead of being falsely advertised today.
Interactive access
Live account entry paths exist for sign-in, account creation, verification follow-through, and password recovery without forcing every access event into a manual support request.
- Portal login
- Portal signup
- Access recovery
- Accounts can start for apps, MSP services, integrations, support, or domains depending on scope.
Approved machine access
Identity metadata and machine-usable account-flow APIs are available only to authenticated approved accounts. Public marketing stays public, but sandbox and production API access require review.
- Sandbox access is issued only after authenticated account review.
- Production access requires stronger policy, security, and network approval.
- Developer, vendor, partner, MSP, affiliate, influencer, and customer-contact accounts are handled as separate approval lanes.
Current scope
The live tranche covers customer-facing auth, account invites, refresh tokens, cookie-backed sessions, verification, recovery, and role-aware checks. Federation and broader tenant exchange stay planned until those lanes are actually deployed.
Direct account-flow APIs
The identity runtime supports first-party invite, verification, and recovery endpoints directly, but those machine endpoints are no longer positioned as anonymous public APIs.
- Interactive portal access remains available for sign-in, signup, verification, and recovery.
- Machine-readable identity endpoints now sit behind authenticated approved-role access.
- Sandbox is the default environment for approved integrations; production is separately reviewed.
What this unlocks
For Gopsco products
- Shared sign-in for applications, domains when needed, billing, support, delivery, and future product surfaces.
- One place to enforce account status, access recovery, and role checks.
- A stable approved metadata path for future client and partner integrations without exposing production APIs anonymously.
For Vyoma.cloud
- Shared identity primitives can be reused when the public Vyoma experience is rebuilt.
- Operator and customer surfaces can stay brand-distinct while sharing verified access foundations.
- Future federation can attach to a real live identity plane instead of a placeholder panel shell.