Skip to content

Gerege Ecosystem Docs

eID based · AI enabled — the single technical documentation gateway for the platforms of the Gerege ecosystem.

This site is not a list of unrelated projects. What Gerege Systems LLC is building is one ecosystem of digital services: grounded in a national eID/PKI core, wired together by an SSO layer, and branched out of a single shared platform template. Every layer, every platform and the shared standards that connect them are collected here.

  • What the ecosystem is

    In one sentence, then layer by layer. What sits on what, and which piece depends on which.

    Introduction

  • Layered architecture

    The full picture, from Layer 0 (data exchange) up to Layer 4 (vertical products).

    Architecture

  • Platforms

    Gerege Nexus · eID Mongolia · Gerege SSO · Template · Gerege Platform · Developer Portal · Wallet · Verify · X-Road.

    All platforms

  • Shared standards

    The de-facto rules repeated across every repo: role hierarchy, identity casing, callback rules, the security baseline.

    Standards

In one sentence

One identity core (eID), two SSO providers, one platform foundation, many vertical products — all on the same Clean Architecture Go backend + Next.js BFF stack, built along two mirrored lines in parallel: government (*.dgov.mn) and private sector (*.gerege.mn).

Layer 4  VERTICAL PRODUCTS   Ring · Khurdan · Wallet · Developer Portal
Layer 3  PLATFORM FOUNDATION Gerege Nexus (modular monolith + app store)  ← new
                             Template Platform (Go + Next.js BFF + AI)
Layer 2  IDENTITY / SSO      sso.gerege.mn · sso.dgov.mn (OIDC providers)
Layer 1  IDENTITY / PKI      eID Mongolia — threshold ECDSA · CA · OCSP · TSA
Layer 0  DATA EXCHANGE       X-Road (instance MN)

2026-08: the ecosystem model is shifting

Gerege Nexus has arrived at layer 3 — a new foundation built as a modular monolith with an app store, carrying all its modules inside one binary. The previous model was "one template → a fork per product"; the new one is "one upstream (Nexus) → a fork per brand, refreshed by merging from upstream". The first two forks — Gerege SSO and Eduge.mn — already exist. The transition is in progress, so the existing platforms remain in production; each page states which state is in force.

See Layered architecture for the detail.

Where to start

Depending on your role

Scope

This site is ecosystem-level documentation: it explains what each platform is for, where its boundaries lie, how the pieces connect, and which conventions they share. The deep API reference, endpoint-level detail and SDK documentation for each platform lives in that platform's own repository — this site points you there.

In scope here Not in scope here
Ecosystem architecture and layers Per-endpoint request/response schemas
Each platform's role and boundaries Method-level SDK reference
Shared standards and conventions Per-repo local development guides
Domain ↔ platform mapping Internal operational secrets

Languages

The site is published in Монгол (the source language) plus the six official languages of the United Nations — العربية · 中文 · English · Français · Русский · Español — seven in total. Switch with the language selector in the header; see Internationalisation for the policy behind it.