Self-driving vs Concierge

Nyxory ships in two tiers. They share one cookbook and one set of primitives. What differs is who runs the agent.

Self-driving

Your coding agent — Claude Code, Cursor, Windsurf, or custom — connects to Nyxory over MCP. It reads our recipes, calls our tools, and ships your software.

• You pay tokens to your model vendor.
• We provide the platform compute.
• Best when you already live in your coding agent day-to-day and want it to handle deploys too.

Concierge

Our agent runs in a pod on our infra, reads the same cookbook autonomously, and reports back. You don’t run anything locally — you just describe what you want and get notified when it’s live.

• You pay a flat monthly subscription.
• We pay the tokens.
• Best when you don’t have an agent setup, or when the task is better off in our hands (overnight migrations, scheduled rollouts, agent-to-agent ops).

Same cookbook, same outcomes

Both tiers retrieve recipes from the same source, call the same primitives, and produce the same deploys. The cookbook is the moat — not which agent runs it.

How to choose

Three questions:

1. Do you already use Claude Code, Cursor, or Windsurf? → Self-driving keeps you in the tool you already know.
2. Do you want continuous background ops without an agent on your side? → Concierge runs without your involvement.
3. Do you need unattended deploys 24/7? → Concierge today. (Self-driving on a remote workstation is on the roadmap.)

Next: How Nyxory works →