diff --git a/README.md b/README.md
index dc66234..0b006f6 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@ A thin shell around [`licensing.Issue()`][issue] in the YAMA Go server —
 all validation (tier rules, TTL floor, `sub` required) lives there, so
 this tool stays in sync as the licensing package evolves.
 
-[issue]: https://github.com/yuanyuanxiang/SimpleRemoter/blob/main/server/go/licensing/server.go
+[issue]: https://git.simpleremoter.com/yuanyuanxiang/SimpleRemoter/src/branch/main/server/go/licensing/server.go
 
 ## Status
 
@@ -20,11 +20,11 @@ package from a sibling checkout — `go install` from a fresh clone will fail.
 Build it locally:
 
 ```bash
-git clone https://github.com/yuanyuanxiang/SimpleRemoter.git ../SimpleRemoter
+git clone https://git.simpleremoter.com/yuanyuanxiang/SimpleRemoter.git ../SimpleRemoter
 # yama-issue-token expects YAMA at ../YAMA/server/go (see go.mod replace);
 # if you cloned as SimpleRemoter, either rename or adjust the replace line.
 
-git clone https://github.com/yuanyuanxiang/yama-issue-token.git
+git clone https://git.simpleremoter.com/yuanyuanxiang/yama-issue-token.git
 cd yama-issue-token
 go build -o yama-issue-token .
 ```
@@ -106,7 +106,7 @@ The customer's server never sees the master HMAC key — it HTTPS-POSTs to
 24h (`YAMA_LICENSE_OFFLINE_HRS`).
 
 See the YAMA repo for the License Server side:
-[`server/go/licensing/`](https://github.com/yuanyuanxiang/SimpleRemoter/tree/main/server/go/licensing).
+[`server/go/licensing/`](https://git.simpleremoter.com/yuanyuanxiang/SimpleRemoter/src/branch/main/server/go/licensing).
 
 ## Security