Welcome to the documentation for Weaviate Cloud Services (WCS).
Documentation for Weaviate can be found here.
About Weaviate Cloud Services (WCS)
WCS is our SaaS (software-as-a-service) solution, providing managed Weaviate instances on the cloud.
With WCS we aim to provide you with the most convenient Weaviate experience. We do this by reflecting in WCS best practices for running Weaviate on the cloud and managing the underlying infrastructure so you can focus on using Weaviate to add value to your work.
WCS instances of Weaviate come pre-configured as shown below to reduce the work and time required for you to get up and running.
Each WCS instance is:
- Automatically created with the latest available version of Weaviate.
- Upgradeable to later versions of Weaviate as they are released.
- Pre-configured with a set of modules (see the WCS dashboard for the relevant list for your instance).
- Not configured with a default vectorizer. So you must specify a vectorizer in the schema if you want Weaviate to vectorize your data.
- Configured with authentication for security (optional for the sandbox).
- We recommend using a Weaviate client for the most convenient experience with authentication.
- Accessible through the Weaviate Console. :::
Is it possible to modify WCS instances' configurations?
For the moment, all WCS instances are pre-configured and are not able to be changed by the user, although this is planned for the future.
If you require a particular module or configuration that is different to one used by WCS instances, please reach out to us to have a chat about custom deployments.
WCS vs Weaviate open-source
Weaviate offers the same capabilities regardless of whether you run Weaviate as a self-deployed solution, or through WCS.
The difference is in how they are configured, hosted and deployed, and who manages them.
The following pages will help you to get started with WCS:
import WCSDocsMoreResources from '/_includes/wcs-more-resources-docs.md';