# Weaviate Support

Weaviate offers several ways to get help, depending on what you're using and the kind of answer you need. This page explains the available channels, who they're for, and how to reach the right place quickly.

## Find the right channel

::::card-grid
:::card{title="Community Forum" href="https://forum.weaviate.io/" icon="messages-square"}
The home for the Weaviate community. Ask technical questions, get help with your cluster, share ideas, and connect with other developers and the Weaviate team. Open to everyone and a great place to start.
:::

:::card{title="Weaviate Cloud Support" href="https://support.weaviate.io" icon="headset"}
Direct help from the Weaviate support team for Weaviate Cloud users and customers. Open and track tickets in the Support Portal, or email support@weaviate.io, and we'll work with you to resolve issues quickly, in line with your support plan.
:::

:::card{title="Support plans" href="https://weaviate.io/support-plans" icon="life-buoy"}
Need guaranteed response times and dedicated assistance? Explore the available support plans and tiers.
:::

:::card{title="Documentation feedback" href="https://github.com/weaviate/docs/issues" icon="github"}
Found something missing, unclear, or incorrect in these docs? Open a GitHub issue so we can fix it.
:::
::::

Not sure where to go? Use this quick guide:

| If you...                                                                                                            | Go to                                                         |
| -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Use **Weaviate Cloud** (Database cluster or Weaviate product in the cloud) or have a **self-hosted support package** | [Weaviate Cloud Support](#weaviate-cloud-support)             |
| Run Weaviate **on your own without a support package** (open-source / self-hosted), including for cluster issues     | [Community Forum](https://forum.weaviate.io/)                 |
| Want guaranteed response times and a dedicated contact                                                               | [Support plans](https://weaviate.io/support-plans)            |
| Found a bug in Weaviate itself                                                                                       | [GitHub issues](https://github.com/weaviate/weaviate/issues)  |
| Found a problem in the documentation                                                                                 | [Docs GitHub issues](https://github.com/weaviate/docs/issues) |
| Want to report a security vulnerability                                                                              | [Report a vulnerability](https://weaviate.io/security)        |

## Weaviate Cloud Support

Support tickets are the right channel if you use Weaviate Cloud or have a support package. This includes:

- **Weaviate Cloud** users: anyone running a cluster or using a Weaviate product in the cloud.
- **Self-hosted customers** with a support package.
- Anyone on an [enterprise or paid support plan](https://weaviate.io/support-plans).

Open and track your tickets in the [Support Portal](https://support.weaviate.io), or email support@weaviate.io. Include your organization name, cluster details, and a clear description of the issue so we can prioritize and resolve it faster. Tickets are answered by the support team in line with your support plan's SLA.

Common support requests include:

- Reporting a bug, outage, or unexpected behavior with your cluster, including production-impacting or high-severity issues that need urgent attention.
- Something not working as expected (errors, performance problems, failed operations, connectivity issues).
- Restoring a backup.
- Increasing cluster limits. By default each organization can have up to six (6) Shared Cloud clusters, and each user can have one (1) free cluster.
- Custom provisioning or increased resources for a cluster.
- Billing and account questions (see also the [billing guide](../cloud-account-management/billing.md)).

:::callout{intent="info" title="Free clusters"}
Free clusters are intended for evaluation and learning. For production workloads, use a paid Weaviate Cloud plan so that support and SLAs apply.
:::

## Community support

The [Weaviate community forum](https://forum.weaviate.io/) is the home for the Weaviate community and is open to everyone. It's a great place for technical questions, help with your cluster, and discussion. The forum is monitored by the Weaviate team and community members, and answers there help other users too.

You can:

- Browse and search [existing forum topics](https://forum.weaviate.io/) before posting, since your question may already be answered.
- Ask a question in the [support category](https://forum.weaviate.io/c/support).
- Report technical issues or bugs with your cluster, or open an issue in the [Weaviate GitHub repository](https://github.com/weaviate/weaviate/issues).

The forum is open to everyone. If you're a Weaviate Cloud user or customer, you can also use [Weaviate Cloud Support](#weaviate-cloud-support) for account-specific or time-sensitive issues.

## Support plans

For teams that need guaranteed response times, dedicated assistance, and higher support tiers, Weaviate offers [several support plans](https://weaviate.io/support-plans). Support plans determine your response-time SLAs and the level of assistance available.

To add or upgrade a support plan, contact [Weaviate sales](https://weaviate.io/pricing#contact-sales). For more on how plans affect billing, see the [billing documentation](../cloud-account-management/billing.md).

## Documentation feedback

These docs are open source. If something is missing, unclear, or incorrect:

- [Open an issue](https://github.com/weaviate/docs/issues) in the documentation repository.
- Use the feedback widget on any docs page to let us know what worked and what didn't.

## Report a security issue

To responsibly disclose a security vulnerability, follow the process on the [Weaviate security page](https://weaviate.io/security). Please do not report security issues through the public forum or GitHub issues.

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
