Support

Support is by email, from the same team that builds the platform.

Where to go

You want to	Go to
Check whether the platform is healthy	status.kupe.cloud
Read about planned maintenance and past incidents	status.kupe.cloud
Report a bug, ask for help, or send feedback	support@kupe.cloud
Report a security issue	security@kupe.cloud, or the contacts in security.txt
Raise a `kupe` CLI bug or feature request	kupecloud/kupe-cli issues
Raise a Terraform provider bug or feature request	kupecloud/terraform-provider-kupe issues
Ask a general or commercial question	hello@kupe.cloud, or the contact form

Check the status page before you send a bug report. If an incident is already open for what you are seeing, updates land there first.

Send these in the first email. Each one saves a round trip:

Tenant name and cluster name. Both, even when only one seems relevant.
What you did. The exact kupe or kubectl command, or the console page and the control you used.
The exact error text. Copy it rather than describing it. If you were calling the API directly, include the X-Request-Id response header, which the API sets on every response and which lets us find the request in our logs.
When it happened, with a timezone. To the minute is enough.
What you expected instead.

For CLI problems, add the output of kupe version, and rerun the failing command with --verbose (-v), which turns on debug logging to stderr.

Do not open a public GitHub issue for a security problem. Email security@kupe.cloud or use the contacts published at kupe.cloud/.well-known/security.txt.

These are platform boundaries:

Restore data from inside your cluster. Kupe does not back up persistent volumes or in-cluster Kubernetes state. See Deleting clusters, tenants, and accounts.
Undo a deletion. Cluster, tenant, and account deletion are permanent and there is no grace period to reverse them from.
Debug your application. We will help with the platform underneath it, and with anything that looks like a platform fault.