App Deployment — Git repo to a public URL

Deploy a web app straight from a Git repository and get a public preview URL — https://<slug>.apps.openfactory.tech — that you can open in a browser, share, or point an automated UI test at. OpenFactory clones the repo, installs dependencies, starts the app, and health-checks it. There’s nothing to wire up: no port forwarding, no tunnels, no DNS.

Just want to test an app you already host? You don’t need to deploy. Point a scenario straight at any reachable URL — a Vercel / AWS / Netlify deployment or a local dev server. See App UI Testing.

How it works

1. Register the app (recommended) — create_app records the repo, a display name, and a URL-safe slug. The slug becomes the subdomain: slug my-shop → https://my-shop.apps.openfactory.tech.
2. Deploy — deploy_app clones the repo into your tester VM, installs and starts it, health-checks it, and returns the public preview URL (plus an in-VM URL for local checks).
3. Open or test it — open the URL in a browser, or run a saved GUI scenario against it with run_app_scenario.

MCP tools

Example

deploy_app(vm_name="<your tester VM>", git_url="https://github.com/you/my-shop")
  → { "public_url": "https://my-shop.apps.openfactory.tech", "status": "live", … }

Then test it:

create_app_scenario(app_name="my-shop", app_url="https://my-shop.apps.openfactory.tech", …)
run_app_scenario(…)

Notes

• Web apps get a public URL. Long-running web services are reachable at https://<slug>.apps.openfactory.tech.
• Stable URL. The same slug always maps to the same URL, across restarts and redeploys.
• Slugs are DNS-safe — lowercase letters, digits, and hyphens (3–40 chars); a few names like api, www, and console are reserved.
• Keep the app’s VM running — the preview URL serves the app from its VM.

Related

• App UI Testing — test any app URL (deployed here or hosted anywhere) with reusable, self-hardening GUI scenarios.
• MCP Integration — set up the OpenFactory MCP server.