Identify each user

Advanced biometrics to recognise specific users, not just devices.

Authenticate

Ensure only account holders and family members access content on any device in any location.

Protect

Significantly reduce revenue risks from widespread account sharing.

Tackle account sharing head on

Streaming is existentially exposed to revenue leakage from account sharing and piracy. Sports rights holders are already losing $30Bn annually to piracy.

Self is robust and agile

Simple integration via APIs and SDKs

For embedding into existing mobile apps and rapid integration into enterprise systems.

Scalable protection

Built to secure globally-cleared, exclusive content packages.

Customisable design

Fully adaptable for tailoring to customer UX/UI requirements.

Ending account sharing and piracy

Next-generation security technology

Patented biometric technology delivers industry-leading safeguards against account sharing and piracy.

Replace illegal sharing with permitted sharing

Use customer engagement to drive signups and directly leverage viral interest in popular content.

Revenue opportunity

Reduce costs by reducing customer touchpoints and exploit new revenue stream opportunities created by enabling users to interact.

While enhancing the experience for users

Simplified login

No more usernames, passwords or account details, just biometric access.

Seamelss transactions

Enable easy sign-ups, purchases, gifting and sharing

Stronger, easier parental controls

Simple and secure authorisation powering family friendly viewing.

Get started with Self

Try now for free

Built for developers

SDK Examples

Mobile SDKs allowing you to build secure and user-friendly applications for Android and iOS and server-side SDKs designed for robust backend integrations.

Documentation

Clear, well-documented APIs and SDKs for popular languages/frameworks, and plenty of examples, to significantly reduce development time and effort.

Our Sandbox mimics production, including APIs and authentication flows to ensure your testing reflects a real world use case. Develop integrations without concerns about production stability or conflicts, innovate and release on shorter cycles.

"The great promise of the early internet has been replaced with real risks. These risks are fundamentally a consequence of leaving a gap between humans and the technology they rely upon. As the web, and the platforms that have come to dominate the online landscape, have grown, so tiny gaps have become the attack vectors fraudsters exploit."

Dan Sutherland

Founder, Self Group

Blog

The Future of Trust

In his paper, Kim Cameron called for an identity layer for the internet. Self has spent six years researching and developing a solution to that challenge. Here, we look at what that is.

Two Decades of Neglecting the Digital Identity Crisis

Kim Cameron's work was foundational, but a lot has happened in the intervening 20 years. Now not only do we need to implement his rules, we have to solve the problems caused by doing nothing for 2 decades.

The Internet isn't a Vault

Why is it seemingly so easy to industrialise fraud and identity crime? The problem is incredibly complex and has its roots back as far as the 18th Century. Decisions taken over decades in good faith have layered one upon the other to create the mother of all unintended consequences.

FAQ

What is an identity and authentication network, and why do I need it?

It's a system that helps verify who your users are (identity) and control what they can access (authentication and authorisation). It saves development time, improves security, and can help you meet compliance requirements.

How do I integrate Self into my application?

Follow the links to try now, or head to our documentation to be taken through the process of integration. It's simple and quick with plenty of examples and code snippets to help guide you.

How does Self handle security?

- End-to-end encrypted communication between devices uses Message Layer Security (MLS) end-to-end encrypted communication between devices.
- W3C Verifiable Credentials (VCs) allow users to securely assert and demonstrate claims about themselves and others.
- Self is underpinned by a robust, tamper-evident and W3C Distributed Identifiers (DIDs) compliant Public Key Infrastructure (PKI) allowing for realtime management of keys and their revocations.
- Self Leverages a number of insudtry standard and accredited ciphers, signature schemes and cryptographic functions, such as Ed25519 (FIPS 186-5), SHA3 (FIPS 202), AES 256 (FIPS 197) and Curve25519.
- All actions are authenticated via signature, with real time key revocation to ensure you are always making up to date decisions.
- Keys are held securely in an on-device encrypted wallet. Usage of keys are gated via biometric checks.

Can I manage and customise user data?

Yes. You can store user profiles, roles, and custom fields with the user's permission. But Self is designed to protect you and users by replacing Personally Identifiable Information (PII) like names and emails with a non-correlatable SelfID, with the PII distributed to the user to store in their phone. It means your dataset is safer and outside of regulation.

How does multi-factor authentication (MFA) work?

Self is already a biometric MFA solution, so you don't need to integrate or pay for external methods like TOTP, SMS or push.

What languages and frameworks are supported?

Self supports:
‍Backend: Golang, Java,
‍Mobile: iOS, Android

Quickstarts, examples including app examples for mobile and SDKs are provided for each.

Can I customise the login and sign-up experience?

Yes. We allow you to use your own UI and UX in all but a couple of screens. You can also use and customise UI elements we release as Open Source components.

What happens if the network goes down?

Self is highly available and deployed to global infrastructure, it has been designed to be resilient and reliable. You can also implement fallback strategies based on your needs.

Prevent users sharing accounts in streaming