Монгол العربية 中文 English Français Русский Español

Gerege Nexus

Integrated Digital Operations Platform

Gerege Nexus is an open-source modular platform that connects services, operations, systems, and data across public and private organizations. It is Mongolian-first and integrates directly with Mongolia's national digital infrastructure (DAN, E-ID, XYP / ХУР).

Nexus is the connection point: where organizations, services, workflows, systems, users and data meet. The platform itself is not tied to one sector — the modules running on it are what make a deployment specific.

Modules compile into a single Go binary, while a PostgreSQL-backed app store decides which apps are active per tenant — module separation without the network hops or operational cost of microservices.

Language policy: Mongolian plus the six official languages of the United Nations — Arabic, Chinese, English, French, Russian, Spanish. Seven in total. Mongolian is the source. The documentation exists in all seven; the application ships offering Mongolian and English and the rest are switched on per device from Settings → Appearance. See the translation guide.

Монгол  ·  العربية  ·  中文  ·  English  ·  Français  ·  Русский  ·  Español

Contents

• Authors
• Core capabilities
• Business applications
• Repository layout
• Getting started
• Configuration
• API overview
• Testing and quality gates
• Security
• Documentation index

Authors

Core capabilities

1. High-performance modular monolith

• Compile-time Go app modules — contacts, products, inventory, billing, documents and sso_clients compile into one binary and are invoked in-process.
• Per-tenant app store — application entitlements, menus and RBAC are driven from PostgreSQL (app_installations).
• Dependency resolver — recursive resolution over a directed acyclic graph with cycle detection and semver constraint checking.
• Catalog sync — catalog/apps.json is the single source of truth; the apps table is reconciled from it on every boot.

2. Cloud-native resilience engine

3. National digital infrastructure

• XYP — State Information Exchange (platform/gerege/xyp.go): citizen civil registration (WS100101) and legal entity verification (WS100201).
• National E-ID and DAN (developer.gerege.mn, eidmongolia.mn) — PKI digital signature, mobile OTP, bank SSO and biometric face verification.
• Built-in OAuth2 / OIDC provider (/.well-known/openid-configuration) issuing client-credentials tokens to third-party systems.
• Email verification (platform/emailverify) — one shared flow for proving an address, called in process by every app module. The mail is sent by the hosted service (enigma.mn), so the platform holds no mailbox credential and owns no sender address; the verification is recorded when the person comes back, and that return works exactly once. Visible under Settings → Email verification.

Note. Mock mode for E-ID, DAN and XYP is a development convenience only. With ENVIRONMENT=production it is disabled automatically, so a fabricated registration number can never authenticate.

4. AI copilot and analytics

• AI assistant (platform/ai/copilot.go) — intent-classified conversation wired to live tenant data.
• Inventory demand forecaster (platform/ai/inventory_forecaster.go) — safety-stock and reorder-point recommendations from historical movement.

Business applications

Routes only open once the app is installed and enabled for the tenant; otherwise the gate returns 403 Forbidden.

Repository layout

backend/
  cmd/api/            HTTP API server (+ demo seeder)
  cmd/migrate/        Goose migration runner
  db/migrations/      SQL migrations
  internal/
    module.go         The Go Module contract
    apps/             Business modules
    platform/         Platform core services
frontend/             Next.js 16 (App Router) web client
catalog/              App store catalog and manifests
deploy/               Production Dockerfile, Nginx config
docs/                 Documentation and translations

Getting started

Prerequisites

• Go 1.26+
• Node.js 20+
• PostgreSQL 16+ (or Docker Compose)

1. Docker Compose

docker compose up -d

Migrations run as a dedicated one-shot migrate service before the API starts.

2. Manual

Backend:

cd backend
go mod download
DATABASE_URL="postgres://postgres:postgrespassword@localhost:5432/platform_db?sslmode=disable" \
  go run ./cmd/migrate up
go run ./cmd/api

Frontend:

cd frontend
npm ci
npm run dev

Open http://localhost:3000.

Demo credentials

The demo account is only seeded outside production. In production it is created only when SEED_DEMO_DATA=true is set explicitly.

Automated deployment

Every push to main runs deploy.yml:

1. Build and push the backend and frontend images to GHCR (:latest and :<sha>).
2. Copy docker-compose.prod.yml to the server.
3. Write the server .env from GitHub secrets and pull the images.
4. Run migrations to completion, then swap the API and frontend over.
5. Probe /health and /ready, printing container logs and failing the run if the rollout is unhealthy.

Deploy manually from Actions → Deploy to Production → Run workflow, optionally pinning an image tag.

Required repository secrets:

The production domain is nexus.gerege.mn, which replaced openerp.gerege.mn in the Gerege Nexus rename. PUBLIC_ORIGIN defines CORS, the OIDC issuer and the eID callback in one place, so moving it carries DNS, the TLS certificate and every client that pinned the issuer along with it.

The server needs Docker only — no source tree and no Go/Node toolchain. See deploy/.env.prod.example for the values.

Configuration

See .env.example for the complete list.

API overview

Session tokens travel either in the HttpOnly cookie or as Authorization: Bearer <token>.

Testing and quality gates

# Backend unit tests with the race detector
cd backend && go test -race ./...

# Static analysis
cd backend && go vet ./... && golangci-lint run

# Vulnerability scan
cd backend && govulncheck ./...

# Frontend build
cd frontend && npm run build

CI runs lint, tests, the frontend build, the Docker image build, govulncheck and gosec on every push and pull request.

Security

• Session tokens are 256-bit random values; only their SHA-256 digest is stored.
• Passwords are hashed with bcrypt and login attempts are rate limited per IP.
• Installing, enabling or disabling apps and registering integrations require tenant administrator rights.
• OAuth2 client authentication uses constant-time comparison.

Report vulnerabilities as described in SECURITY.md.

Documentation index

Credits and inspiration

1. snykk/go-rest-boilerplate by @snykk — Go REST API foundations.
2. Odoo — modular app store and dependency model.
3. go-zero — cloud-native resilience engine.

License

Copyright (c) 2026 Gerege Systems Development Team, Gemini AI & Claude AI. Distributed under the Apache 2.0 License — see LICENSE.

Flag icons by Flaticon (attribution).