Deploy a Next.js app
End-to-end walk-through: take a Next.js repo and ship it on Nyxory through your connected agent. Five to eight minutes for a standard repo.
-
Open the repo in your agent.
Open the Next.js project in your MCP-connected client (Claude Code in the repo dir, Cursor with the workspace, Windsurf with the project loaded).
-
Prompt.
deploy this Next.js app to NyxoryOr, if you want to name a target project explicitly:
deploy this Next.js app to my "widget" project on Nyxory -
What the agent does (visible as tool calls).
nyx_deploy_start(repo)— returns the Next.js recipe + your project’s state + URL pattern- Scans
package.json, detects framework version + runtime needs - Detects env vars in
.env*, asks you which are secrets (vs build-time embeds) nyx_app_create(...)— creates the app stub in your projectnyx_secret_set(...)— uploads the secrets you confirmed- Triggers the build via the standard primitives — your agent watches the rollout
- Returns the ingress URL when the deploy reaches Available
Any of these can pause for input — your agent will ask if it’s unsure (a non-standard build script, an ambiguous secret, an unfamiliar dependency).
-
Watch the deploy.
Two options:
Terminal window nyx app list # quick overviewnyx app get widget my-nextjs # detail on one appnyx app deployments widget my-nextjs # rollout historyOr open the console at Projects → widget → Apps.
-
Verify it’s live.
Terminal window curl -I https://my-nextjs.nyxory.appExpect
200 OK. The ingress host appears innyx app get widget my-nextjs --json | jq '.data.domains[].host'.
Common Next.js gotchas
Section titled “Common Next.js gotchas”Next steps
Section titled “Next steps”- Add a custom domain → — bind your own hostname
- Projects & accounts → — resize quotas, manage the pool