ArchSync
PricingDocsAboutContact
Sign inOpen the canvas
← all guides

Map a Go API built with gin or echo to the apps that call it

Go services tend to be split into many small repos, each with its own router. ArchSync reads every router — including inline handlers — and links them to the clients that depend on them.

1. Put the repos side by side

Clone them into one folder. Nothing is linked or uploaded; ArchSync only reads the files.

my-product/
├─ orders-service/   # Go (gin or echo)
├─ users-service/    # Go
└─ web/              # React / Next.js, or a Flutter app

2. Scan them together

cd my-product
npx archsync scan --workspace

What ArchSync reads:

  • Services: gin and echo routes on any router variable (including inline func(c) handlers), handlers and services.
  • Clients: Web calls with axios or fetch, and Flutter calls with http or Dio.

3. Read the broken calls

Every call that no route answers any more is listed with its repo, method and path. Example output:

$ npx archsync scan --workspace
  Cross-system:    37

─── Broken cross-system calls (1) ───
  ✖ web: DELETE /v1/orders/${id}

Change something — rename a route, change a method, drop a field — and scan again to see exactly which callers it breaks. Open the result on a canvas with npx archsync serve.

4. Run it on every pull request

# CI (free): check out the related repos side by side, then scan them together
git clone --depth 1 $ORDERS_SERVICE_REPO orders-service
git clone --depth 1 $USERS_SERVICE_REPO users-service
git clone --depth 1 $WEB_REPO web
npx archsync scan --workspace     # prints "Broken cross-system calls" in the job log

With ArchSync Team, each repo pushes its map to your own Supabase, and any repo can check itself against all the others:

# CI (Team): compare this repo with what every other repo pushed
npx archsync scan
npx archsync diff --merged --json > merged.json
test "$(jq .breakingCount merged.json)" = 0   # fail the job on a breaking change

Good to know

Routes assembled from variables computed at runtime are shown as gaps.

Quickstart
archsync
ArchSync

Reads every repo your product is made of and shows where they call each other — so a change on one side doesn’t surprise the other.

Product

Open the canvasPricingDocsCLI on npm

Developers

QuickstartGuides by stackCLI referenceDatabase setupReport an issue

Company

AboutContactTermsPrivacyRefundsShipping & delivery
© 2026 ArchSync · operated by Vivek Parida, Bhubaneswar, Odisha, IndiaYour code stays on your machine. Your schema lives in your database.