How nyxory works

A deploy touches four places. Your coding agent starts it, a nyxory agent carries it off your machine, the nyxory cloud runs it, and operations keeps it healthy long after the first push. You only ever touch the first one — the rest is where nyxory does its work.

In your coding agent

You prompt — “deploy this repo.” Your agent reasons about the stack and calls nyxory over MCP. The reasoning stays with your agent; nyxory never overrides it, and you never leave your chat. Which coding agent is your choice — Claude Code, Cursor, Codex, or any MCP client work the same way. Connect your agent →

In the nyxory agent

Off your machine, a nyxory agent picks up the work: it reads the recipe for your stack, clones the repo into an isolated workspace, sets your secrets, builds a container image, and applies the deploy. This is the execution surface — the DevOps hours, done by an agent instead of your team, and never against your production by hand. The tool-by-tool detail lives in MCP tools and Builds & the execution surface.

In the nyxory cloud

Your app runs on European infrastructure, isolated per project — ingress, TLS, a public URL, configurable backups, all provisioned for you. You allocate the resources; nyxory runs what you allocate. How the account pool and project quotas relate is in Projects & accounts.

In operations

This is the part most platforms stop before. After it’s live, the nyxory agent keeps it running — monitoring, patching and CVE response, change management, backups and restores, incident response — with every action on the record. Most of the real cost of software isn’t the deploy; it’s the months of operating it afterward, and that’s the part nyxory owns continuously. Day-2 operations →

---

Who drives which part — your own coding agent over MCP, or nyxory’s operations agents — is your call, and you can mix them. See Self-managed and operated.