CONFIDENTIAL June 2026

UniCon Server Architecture

Dual-Server Global Infrastructure — Role & Flow

MITOMO Inc. — UniCon Team

Press → or Space to navigate

Why Dual-Server?

🚫 The Problem

China's Great Firewall blocks Google Cloud, making UniCon apps inaccessible for China-based employees.

✅ The Solution

Run a fully mirrored UniCon instance on a local China server, with bi-directional sync via encrypted VPN.

🔒 Connectivity

Tailscale mesh VPN (WireGuard) bypasses GFW, enabling secure server-to-server communication.

🎯 Management

All management centralized at Google Cloud (Japan). No on-site personnel required in China.

Architecture Overview

🇯🇵 GOOGLE CLOUD (Global Master) 🇨🇳 HUAWEI SERVER (China Local) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │ UniCon Apps (IERP/IRS/MAS/ASIS)│ │ UniCon Apps (IERP/IRS/MAS/ASIS)│ │ MySQL Master (Global Data) │ │ MySQL Master (China Data) │ │ Qdrant VectorDB │ ◄════► │ Qdrant VectorDB (Mirror) │ │ Hermes Agent (ASIS Global) │ Tailscale│ Hermes Agent (ASIS China) │ │ Google Drive │ VPN │ Local Storage (40TB HDD) │ │ GCE: 136.110.87.61 │ │ HUAWEI RH2288 v3 │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ▲ ▲ │ │ Japan + Global Users China Domestic Users

Server Specifications

🇯🇵 Google Cloud

PlatformGoogle Compute Engine
Regionasia-northeast1 (Tokyo)
IP136.110.87.61
ServicesMySQL, Qdrant, Hermes, Apps

🇨🇳 China HUAWEI

CPUXeon E5-2696v4 ×2 (44 cores)
RAMDDR4 256GB
Storage256GB SSD + 40TB HDD
ChassisFusionServer RH2288 v3

Data Authority — Conflict Prevention

Each server owns write authority for its regional data. Both have read access to all data.

Data TypeWrite AuthorityRead Access
Japan / Global Orders🇯🇵 GoogleBoth
China Domestic Orders🇨🇳 ChinaBoth
Product Master Data🇯🇵 GoogleBoth
China Customer Data🇨🇳 ChinaBoth
KBMS Documents🇯🇵 GoogleBoth
China Local Documents🇨🇳 ChinaBoth

Synchronization Strategy

MySQL

GTID-based replication
↔ Bi-directional
⏱ Real-time

Qdrant VectorDB

Snapshot transfer
🇯🇵 → 🇨🇳 One-way
⏱ Daily scheduled

File Storage

rclone over VPN
↔ Bi-directional
⏱ Every 5 minutes

Agent Tasks

Hermes API
↔ Bi-directional
⏱ Real-time

Management — Control Tower

All management centralized at Google Cloud. China managed remotely via Tailscale VPN.

TaskMethodFrom
Code DeploymentGit push + Docker rebuild🇯🇵 Google
Server MonitoringSSH + Hermes health checks🇯🇵 Google
DB SyncReplication monitoring🇯🇵 Google
App UpdatesDocker Compose restart🇯🇵 Google
Agent TasksMain → China delegation🇯🇵 Google
Incident ResponseSSH via Tailscale🇯🇵 Google

User Access Map

User GroupAccess PointServerChannel
🇯🇵 Japan Staffunicon.mitomo.co.jpGoogleWeb / DingTalk
🌏 Internationalunicon.mitomo.co.jpGoogleWeb
🇨🇳 China StaffInternal IP / CN domainChinaWeb / DingTalk
👤 Owner (Admin)Both serversBothAntigravity + Hermes

Disaster Recovery

If either server goes down, the other continues independently. Sync resumes on reconnection.

Implementation Roadmap

PhaseTaskDuration
1Tailscale VPN setup (both servers)1 day
2China server infrastructure (Docker, MySQL, Qdrant)2 days
3UniCon app deployment on China server2 days
4Data synchronization pipeline2 days
5Hermes Agent setup (China)1 day
6Testing & validation1 day
Total~9 days

UniCon

Unified Convergence — Dual Server Architecture

MITOMO Inc. — Confidential

1 / 10