FedID
Protocolo de Identidade
Empresa
Detalhes
Licença Partially open (JLINC Labs has 54 GitHub repositories, organization members not publicly visible; jlinc-node is a listed public repo for the JLINC protocol; FedID server and libraries documented at fedid.me but access unclear)
Status de Dev 🧪 Alpha
Detalhe do Status de Dev Alpha / Active development (FedID protocol documented at fedid.me; JLINC DID method specification published at did-spec.jlinc.org; libraries and server implementation documented but source not publicly visible; JLINC Labs has 54 repositories on GitHub, mostly private)
Proprietário JLINC Labs (co-founded by Jim Fournier, CEO, and Victor Grey, Chief Architect); JLINC Inc was founded as Portable Data Corp in 2015; Oakland, California
Órgão de Governança Company-controlled (JLINC Labs; protocol is patented) | None (FedID Servers are independently operated)
País USA (Oakland, California)
Ano de Início 2023
Stack Node.js (JLINC reference implementation); containerized server deployment; OIDC-compatible server infrastructure; ActivityPub federation layer
Financiamento Unfunded / Self-funded (JLINC Labs listed as unfunded on Tracxn; Jim Fournier funded via LinkedIn IPO founder shares; Noolinc Studio fund planned for 2025)
Última Investigação 15 de jan. de 2026
Protocolo de Identidade Atributos
Origens Decentralized identity / SSO (evolved from JLINC protocol for permissioned data exchange under signed agreements; addresses Fediverse identity portability problem where user identity is tied to a specific server; inspired by solving the OIDC monopoly of Google and Facebook)
Banco de Dados Federated DID document storage (DID documents replicated across federated FedID servers; each server maintains copies of federated user DIDs)
Linguagem de Consulta N/A (DID resolution via JLINC DID method; OIDC discovery endpoints for service integration)
Formatos de Dados JSON-LD (DID documents following W3C DID v1 context + JLINC v2 context); JWS (JSON Web Signatures for proof); OIDC tokens; ActivityPub JSON-LD for federation
Suporte Móvel Yes (FedID App on user's device generates and stores private keys; QR code scanning for authentication challenges; designed for mobile-first key management)
Suporte Web Yes (OIDC-compatible — any website supporting OIDC login can integrate FedID Connect by changing two lines of code; fedid.me documentation site)
Aplicativos Nativos FedID App (described as device-resident app for key generation, storage, and QR code authentication; platforms not specified)
Termos Commercial (JLINC Labs is a for-profit company; JLINC patent issued Jan 2023 'Internet Data Usage Control System'; licensing model for enterprise use; clients include EY, KPMG, Dolby, Nestle, Atlassian for JLINC protocol)
Fundos Unknown (no documented external funding rounds; Jim Fournier's personal investment from LinkedIn IPO proceeds)
Baseado Em OIDC (OpenID Connect — FIDC is drop-in compatible); ActivityPub (federation of DID documents between servers); JLINC protocol (signed auditable data exchange agreements, US patent issued 2023); W3C DID v1 specification
Permissões Proprietary / Open Protocol — JLINC Labs holds a patent on the JLINC protocol (granted January 2023); FedID is a service built on JLINC infrastructure without a published OSI-approved open source license. The FIDC protocol specification and DID method documentation are openly published and freely implementable, but the primary jlinc-node implementation does not carry a standard OSI license.
Autenticação e Identidade DID-based with OIDC compatibility: user creates a FedID (user@domain.ext format) and the FedID App generates private keys on device; FedID Server creates a DID document containing public keys; user signs DID with private key; server federates DID to all federated servers; login via QR code challenge instead of passwords
Modelo de Armazenamento Federated replication: DID documents stored on the user's home FedID Server and replicated to all federated FedID Servers; user's private keys stored only on their device(s) via FedID App; JLINC audit records can be stored on designated archive servers (e.g., archive.jlinc.io)
Interoperabilidade High: OIDC-compatible (any OIDC relying party can integrate FIDC by changing two URL lines); ActivityPub federation (interoperates with Mastodon, Lemmy, Threads, and any ActivityPub-compatible software); JLINC protocol for data provenance auditing across services; potential EU regulatory alternative to Google/Facebook OIDC monopoly
Portabilidade de Dados Core design principle: username persists even if original server disappears, changes domain, blocks user, or shuts down — as long as DID has been federated to at least one other server; user migrates by connecting to any other FedID Server that holds their federated DID; content ownership tracked via JLINC capability delegations
Governança e Tomada de Decisão Corporate (JLINC Labs as for-profit company with patented protocol); FedID Servers are independently operated (similar to Mastodon instance model); no documented community governance structure for the protocol itself
Maturidade / Padronização do Protocolo Community Standard (published did:fedid method specification; JLINC protocol backing; not submitted to formal standards body)
Padrões de Identidade W3C DID v1 (https://www.w3.org/ns/did/v1); JLINC DID v2 (https://didspec.jlinc.io/v2/ctx.jsonld); OpenID Connect (OIDC); ActivityPub; W3C Verifiable Credentials (via capability delegations)
Métodos DID Suportados did:jlinc (format: did:jlinc:fedid.domain.ext:<base64-key>); custom JLINC DID method specification at did-spec.jlinc.org; version 2.0.0 with create, update, revoke record types
Gestão de Chaves Device-resident private keys: FedID App generates key pairs on user's device; public keys published in DID document verificationMethod array; each device gets its own verification method entry (type: 'device') with a controller reference to the user's DID; multiple devices supported via multiple verificationMethod entries; keys are base64-encoded
Tipos de Credenciais DID documents (JSON-LD representation of user identity with verification methods, services, and capability delegations); OIDC tokens (standard OIDC ID tokens and access tokens); JLINC audit records (cryptographically signed data exchange agreements providing provenance)
Método de Verificação JWS/CT (JSON Web Signature / Controller Verification): DID documents include a proof block with JWS signature, created timestamp, proofPurpose of 'controllerVerification', and reference to the signing device's verification method; QR code challenge-response for login authentication
Recursos de Privacidade User-controlled key management (private keys never leave device); JLINC protocol capability delegations enable tracking of data usage and AI training consent; minimal disclosure (OIDC scopes control what information is shared with relying parties); no password storage on servers
Métodos de Autenticação QR code challenge (primary: FedID Server presents QR code, FedID App scans and signs challenge with device private key — replaces passwords entirely); OIDC flows (authorization code flow for relying party integration); device-based key signing
Mecanismo de Revogação DID document deactivation (deactivated field in DID document, default false); DID version tracking (version field increments with each update, enabling audit trail); device revocation via removal of verificationMethod entries; JLINC DID method supports revoke record type
Tipos de Agentes Suportados Humans (primary); services (DID document service array lists connected services with types 'login' and 'service'); JLINC-enabled services can act as agents with capability delegations from user's DID; potential for AI agent delegation via JLINC protocol
Tipos de Carteira/Cliente FedID App (device-resident application for key management and QR code authentication); any OIDC-compatible client (two-line URL change to integrate); Fediverse clients (Mastodon, Lemmy apps can use FedID for login)
Mecanismos de Recuperação Recovery hash (DID document includes recoveryHash field — a hashed recovery secret for account recovery); federation-based resilience (DID replicated across multiple servers means identity survives individual server failure); device addition (new devices can be authorized via existing device)
Conformidade / Regulamentações GDPR (JLINC protocol specifically designed for GDPR compliance — provides auditable signed agreements governing data exchange; working solution for GDPR since 2018; US patent covers data usage control); EU regulatory alternative to Google/Facebook OIDC
Protocolos de Troca de Credenciais OIDC / FIDC (FedID Connect is drop-in compatible with standard OIDC flows); ActivityPub (federation of DID documents between servers); JLINC protocol (signed data exchange agreements with cryptographic audit trail)
Estrutura de Confiança Federated trust: trust anchored in FedID Server operators (similar to email/Mastodon server trust model); JLINC audit records provide cryptographic proof of data exchange agreements; capability delegations enable verifiable chain of data provenance; no blockchain required
Modelo de Custo TBD (JLINC Labs is commercial with enterprise licensing; FedID Server operation costs borne by server operators similar to Mastodon; end-user cost model not documented; JLINC protocol licensing terms not publicly detailed)
Resistência à Censura High (by design): user identity survives original server disappearance, domain changes, user blocking, or server shutdown — as long as DID has been federated to at least one other server; no single point of failure for identity; user can migrate to any federated server