Documentation

Yado Ecosystem Architecture

Yado is an interconnected ecosystem of self-hosted microservices deployed under the *.yado.my.id domain on private homelab infrastructure with centralized identity and access control.

1. Service Registry & Status

Service	Role	Status	Repository
SSO	Centralized OAuth2 identity and session provider	Live	srytmj/sso
Malas	Digital catalog and library reader	Live	srytmj/malas
libs	Agent/relay tunnel connection platform & content aggregator	Draft / RFC	srytmj/libs
Pore.js	Browser digital reader engine (manga, novels, EPUB, and PDF)	Development	srytmj/pore.js

2. Digital Reader Architecture (Reader Effort)

The reader effort is engineered with a multi-tenant model, enabling users to link their personal Komga or Kavita instances. The architecture is decoupled across two independent repositories communicating through standardized API contracts:

Backend: libs (Go)

SSO authentication integration
Outbound agent and tunnel relay (yamux)
Catalog synchronization and metadata indexing
Media proxying, format transcoding, and caching
Normalized Read API endpoints (/api/v1)

Frontend: Pore.js (TypeScript)

Image rendering engine for comics and manga
Text pagination engine for EPUB and PDF
Source-agnostic adapters (Yado, LocalFile, and Demo)
Operates standalone in browser without strict backend dependency

3. Single Sign-On (SSO) Authentication Flow

All Yado web services implement standard OAuth2 authentication flows. Each client application registers its client_id and redirect_uri with the centralized SSO provider.

GET https://sso.yado.my.id/oauth/authorize?client_id=yado-landing&response_type=code

Upon successful verification on the SSO portal, session credentials grant immediate access across target microservices without repeated logins.