AgenticOps multi-site translation hub

Professional converters run this server; your browser is the client. Create a project, attach many legacy sites over SSH, pick one web output language, then Run all sites with parallel jobs and per-site progress bars in the project Console.

Documentation — Migration OS, CLI, hub install, GCE verify, and full operator library.

Organizations

Team projects share an org; members see org-scoped projects only.

Your projects

Hub stores workspaces under ~/.chrysalis-hub/ on this server.

Language completion tracker

Scope

Grade filter

Prioritized by popularity; shows what remains per language.

Origin	Output	Grade	Path	Next action
—

Extended matrix oracle census

601/601 oracle-product (G9160 maintenance). Trace replay in CI — not production cutover parity.

Translation path explorer

Browse the 575-pair hub matrix: per-pair ingest/emit/verify lanes, similarities, differences, and consolidated cross-language synthesis.

Synthesis overview

Loading synthesis…

Gold pairs

—

Pair detail

Origin

Output

Migration plan

Combine language compare, pair risk, and detected datastores into operator steps.

Detected databases (comma-separated ids)

Similarities

Differences

Best practices

—

New translation project

1 Project & sites → 2 Auto setup (SSH) → 3 Console: translate all sites

Project name Description Organization (optional)

Origin sites (SSH) — add as many as you need

Fill one site below and click Add to project. Repeat for each legacy server. All sites share the same output language.

Host

Port

User

SSH key path on hub (optional)

Remote project path Autodetect languages over SSH (install chrysalis-origin-scan on origin — connectivity guide)

Prepare origin on add (install scan agent + capture kit docs via SSH) Pull code to hub on create

0 sites queued

No server to point at? Upload your files

Skip SSH — upload your site's PHP files (or a .zip of the whole tree) straight from your browser. You'll also need a small chrysalis.routes.json in the upload declaring your routes explicitly (no auto-detection — Chrysalis never guesses routes from code).

Show an example chrysalis.routes.json

{
  "app": "my-site",
  "routes": [
    { "method": "GET", "path": "/posts", "file": "pages/posts_list.php", "pathParams": [] },
    { "method": "GET", "path": "/posts/:id", "file": "pages/posts_view.php",
      "pathParams": [{ "name": "id", "type": "int", "phpVar": "post_id" }] }
  ]
}

Select files or a folder ...or a single .zip instead

Output language (all sites)

Origin language

Set manually if autodetect is off or wrong.

Output language

SSH: add sites above, or use Local workspace only for code already on this hub. No CLI required.

Console

Client/server hub — add many SSH origin sites, run in parallel with per-site progress.

Project settings

Name

Output language

Translation route plan

Loading plan…

Migration plan (project)

Load a project to see migration steps.

Evidence dashboard

Verify correctness, holes, and blockers for the first site.

Origin sites

Batch: idle

Parallel jobs

Prep origins before translate

Add site (SSH)

Site name

Origin override

Host

Port

User

SSH key on hub

Remote path Prepare origin (SSH agent + capture docs) Pull code to hub when adding site

idle

Use Run full pipeline for prep + pull + translate in one click.

Overall batch progress

0 / 0 routes (aggregate)

IS routing: idle

Hole closure: verify-gated repair bridge when holeId present

Oracle verify (staging traces)

Copy traces into each site’s .chrysalis/traces/ on this hub, start the emitted app, then verify.

Emitted app base URL

Pass threshold

Traces dir override (optional) Upload traces (.ndjson / .json, or .zip) Upload origin source files (PHP tree, files/folder, or .zip — no SSH needed)

Observe on staging

Select a site and load capture instructions (PHP oracle on staging, not on prod).

—

Job log

Chrysalis status (selected site workspace)

—

Create your demo account