Operate & go live

The other guide paths end at a working deployment. This one starts there, with seven guides.

Going live is a different job from building: you are settling access, domains, rollbacks and escalation rather than writing features, and most of it is done once per project by someone who will not touch the code again. The reference pages below already describe each piece. The guides in this section stitch them into the order you actually need them.

The guides

1. Go live with a project lists what to settle first: keys, domains, caching, deploy safety, logs and support.
2. Size a launch sizes the request budget, batch calls, site timeouts and warmup so a launch does not discover the limits in production.
3. Plan and run a migration from an existing shop sequences a move off another shop platform: what moves and what stays behind (order history does not move), the load order, verification, the DNS cutover and the rollback.
4. Debug a failed request takes a failed call from the response to its cause, and to what support needs.
5. Answer a customer's security questionnaire turns the published facts into answers for the security review that usually comes with a launch, and lists what only revenexx can confirm.
6. Stay current with API, SDK and CLI versions is the routine that keeps you ahead of a change: a Changelog owner, exact pins, a weekly diff of your tenant's API surface and an upgrade order.
7. Script a bulk change safely pages through a list into a plan you can review, applies it row by row with the CLI, and resumes or undoes it.

What the platform already handles

TLS, the web application firewall, DDoS filtering and compression are on without any setup, for the domains you point at the edge. Rate limits apply per tenant on api.revenexx.com only (as of 2026-09), and a 429 is a limit to handle, not a setting to change. The table, with the host each row covers, is in Go live with a project.

Operating what you shipped

• Apps — Operating covers each App Studio screen, what healthy looks like and what to hand over when you escalate; Verifying live and Versioning sit beside it.
• Themes and Sites — Publishing a theme covers going live and rolling back; Deployments, Previews and Logs.
• Anything calling the gateway — Debug a failed request takes a failed call from the response to its cause; Errors, Idempotency and API versioning are the reference behind it.

Where to go next

• Get help — where a question goes, and what to include.
• status.revenexx.com — an incident listed there is already being worked on.