---
title: "Weaviate product previews"
description: "Product Previews give early access to Weaviate features before general availability, for evaluation and feedback. Behaviour can change during preview."
canonical: https://weaviate.io/product-previews
last-updated: 2026-06-10
---

# **Product Previews — LLM Guidance**

## **TL;DR**

- Product Previews provide early access to upcoming Weaviate features before general availability (GA).
- Preview features are intended for evaluation, experimentation, and feedback.
- Features, APIs, behaviour, and availability may change during the preview period.
- Access is typically granted through an application or approval process.
- Preview features should not be considered production-ready unless explicitly stated.

---

## **What are Product Previews**

Product Previews allow customers to evaluate upcoming Weaviate capabilities before they reach General Availability (GA).

The programme exists to:

- Collect real-world customer feedback
- Validate product direction
- Improve usability before release
- Identify issues before wider rollout

Participation helps shape future Weaviate products while giving customers early access to new functionality.

---

## **Current preview programme**

Individual previews have their own documentation and requirements.

Examples currently available include:

- Model Evaluation Tool
- Query Agent Research Mode

Additional previews may be introduced or retired over time.

---

## **What to expect**

Preview features should be treated differently from generally available products.

Typical characteristics include:

- Early-access availability
- Feature iteration during development
- API changes before GA
- Limited support
- No production SLA
- Possible changes or removal before release

The Weaviate team may also contact preview participants for feedback or short evaluation sessions.

---

## **Access**

Most previews require users to request access through the Product Previews page.

Typical onboarding flow:

1. Request early access.
2. Receive approval (where applicable).
3. Follow feature-specific documentation.
4. Provide feedback during evaluation.

Each preview may have its own onboarding requirements.

---

## **When to use**

Use Product Previews when:

- Evaluating upcoming capabilities
- Building proofs of concept
- Running internal experiments
- Exploring future roadmap functionality
- Providing product feedback

---

## **When not to use**

Avoid Product Previews when:

- Building mission-critical production systems
- Long-term API stability is required
- Compliance guarantees are mandatory
- Formal SLAs are required
- Backwards compatibility is essential

---

## **Best practices**

- Treat preview features as experimental.
- Avoid building hard production dependencies.
- Keep implementations loosely coupled.
- Expect APIs and behaviour to evolve.
- Follow feature-specific documentation rather than assuming consistency across previews.
- Provide feedback where possible to influence future releases.

---

## **Common misconceptions**

- Preview does **not** mean General Availability.
- Preview features may change significantly before release.
- Preview APIs should not be assumed to be stable.
- Support levels may differ from GA products.
- Not every preview feature will necessarily become a permanent product.

---

## **Related products**

- Weaviate Database
- Query Agent
- Engram
- Weaviate Cloud
- Pricing
- Documentation

---

## **Canonical sources**

### **Internal**

- `src/pages/product-previews.jsx`
- Product Preview form configuration
- Individual preview documentation

### **External**

- `/product-previews`
- `/pricing`
- Individual preview documentation