certified.app

What It Is

Certified is a passwordless identity platform operated by Hypercerts Foundation and built on AT Protocol. Its goal is to let users access multiple partner applications with a single account, while allowing profiles, records, and activity to move with the identity. The experience is similar to “Sign in with Google,” but with an emphasis on open protocols, no vendor lock-in, and data portability.

Core Capabilities and Security

In terms of protection, Certified primarily provides an identity authentication layer: users enter their email address and receive a one-time verification code, with no password or crypto wallet required. The passwordless model can reduce risks associated with weak passwords, password reuse, and credential-stuffing after leaks. However, the source text does not specify verification-code validity periods, device binding, risk detection, anti-phishing mechanisms, or multi-factor authentication policies.

For deployment, Certified is an online identity platform that partner applications integrate via “Sign in with Certified.” It currently supports Ma Earth, GainForest, Simocracy, and Hyperboards, and says more applications will be added in the future. A key integration advantage is that it is based on AT Protocol: users can use AT Protocol or Bluesky accounts, and on some platforms they can connect existing accounts. The platform states that all components are open source and can be verified and built by anyone, which is positive for security auditing and ecosystem expansion.

Pricing, Compliance, and Management

The collected source text does not disclose its pricing model, enterprise plans, payment methods, SLA, or technical support channels. It also does not show compliance certifications such as SOC 2, ISO 27001, or GDPR. Information on management and alerting is also insufficient: there is no mention of an admin console, audit logs, login alerts, permission models, or enterprise directory integration. As a result, it currently appears better suited to open-ecosystem identity and lightweight login scenarios than to organizations that require full enterprise IAM, compliance auditing, and centralized control.

Pros, Cons, and Who It’s For

Its strengths are ease of use, no need for passwords or wallets, an emphasis on data exportability, the ability to leave the service, open protocols, and open-source transparency. Its drawbacks are a limited number of partner applications and insufficient disclosure around security policies, compliance, support, and commercialization. It is suitable for applications in the AT Protocol/Bluesky ecosystem, community platforms that value data portability, and partner apps that want to reduce registration and login friction.

Access from China

The source text does not provide information about mainland China network access, payment, or localization support, so this remains unknown. For use in China-based operations, it would be necessary to additionally verify email verification-code deliverability, access stability, privacy compliance, and fallback options. Comparable alternatives include Auth0, Okta, Microsoft Entra ID, Clerk, Magic.link, or domestic identity authentication services.