CloudChef

1.7 public betaEffective

Support

One public GitHub form handles product, CloudChef sign-in, privacy, and abuse requests. Everyone can read it, so post nothing you would not publish.

On this page

Open a support request

Create a GitHub support request

Before posting, remove:

  • personal data and identity documents
  • prompts and source code
  • tokens and credentials
  • Cloudflare account identifiers
Acknowledgement
Within two weekdays

Public-beta targets, not guarantees or contractual service levels. Channels are not monitored continuously, and CloudChef does not provide 24/7 or real-time emergency response. Acknowledgement is not resolution.

Account and privacy requests

Post only the request type and your GitHub handle. There is no verified confidential support or privacy inbox yet; if a private method can be arranged, a maintainer will name it there. Statutory deadlines govern privacy-rights requests whatever the target above says.

Report abuse

Abuse reports use the same form — there is no separate abuse address. Choose the abuse category, describe the prohibited use under the Terms, and identify the affected CloudChef-generated site by its public URL only. Attach no evidence containing another person’s private content; a maintainer will ask for what is needed.

CloudChef can act only on the service it operates. A deployed application’s content and behaviour live in the Cloudflare account that owns it, so serious cases may also need Cloudflare support or law enforcement.

Not an emergency channel

Immediate danger
Local emergency services
Compromised Cloudflare account
Cloudflare support, which also handles an active Cloudflare platform incident
A vulnerability in CloudChef
Security, so exploit details stay out of a public issue