ArchSync
PricingDocsAboutContact
Sign inOpen the canvas
← all guides

Keep an admin panel in sync with Firebase Cloud Functions

With Firebase, an Express app is often exported as an HTTPS function, so every URL starts with the function’s name. That prefix lives in the export, not the route, which is exactly where cross-repo mistakes hide.

1. Put the repos side by side

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

my-product/
├─ functions/    # Firebase Cloud Functions (Express inside onRequest)
├─ admin/        # React admin panel
└─ app/          # Flutter or web app

2. Scan them together

cd my-product
npx archsync scan --workspace

What ArchSync reads:

  • Functions: Express routers mounted inside onRequest(app) exports, with the function name applied as the URL prefix (with or without it in the path), plus Firestore collections the code reads and writes.
  • Clients: Admin-panel and app calls, matched to the function route that answers them.

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:    100

─── Broken cross-system calls (1) ───
  ✖ admin: POST /deletion-requests/approve

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 $FUNCTIONS_REPO functions
git clone --depth 1 $ADMIN_REPO admin
git clone --depth 1 $APP_REPO app
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

A URL built entirely at runtime is shown as a gap rather than guessed.

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.