Skip to main content

Weaviate console

LICENSEΒ Weaviate on Stackoverflow badgeΒ Weaviate issues on Github badgeΒ Weaviate version badgeΒ Weaviate total Docker pulls badgeΒ Go Report Card


Learn how to use the Weaviate console

The Weaviate Console allows you to connect to Weaviate instances that are running on the Weaviate Cloud Service (our SaaS solution), on your own cluster, on your local machine, or all the public demo datasets. Note that the console never collects any data from your Weaviate instance; you can safely connect every instance, also over VPN.


The console is available on:

Login page​

When opening theΒ Weaviate Console, you'll see two options:

  1. "Sign in with the Weaviate Cloud Service"
  2. "Self-hosted Weaviate"

The Weaviate Cloud Service​

The Weaviate Cloud Service allows you to create Weaviate instances as SaaS instances on our infrastructure. There is no difference between locally run Weaviate instances or Weaviate SaaS instances other than that the latter ones are managed by us.


Sandboxes are free Weaviate instances! You can create them for small test use cases if you don't want to run Weaviate locally.

Connect to a self-hosted Weaviate​

You can connect to any Weaviate instance as long as your computer has access to it (yes, this also includes over a VPN). The GraphiQL editor runs locally, and we don't forward any result or query to our servers.

When you're connected, you can use the GraphiQL interface to interact with your Weaviate instance.


GraphiQL is a graphical interface that allows you to manually write GraphQL queries. Within Weaviate we use it a lot, the auto-fill functionality allows you to easily navigate through your own dataset. Curious? Try out the console right now with the Wikipedia dataset.

Try out the console​

  1. Go to:
  2. Start querying :)

Try out the console with your own instance​

  1. Go to:
  2. In the Self-hosted Weaviate section, provide the endpoint of you instance. If you run Weaviate locally this will be http://localhost:8080.
  3. Click "connect"

The console might ask to downgrade to HTTP. This is done to avoid CORS errors.


  • You can use the Weaviate Console to connect to any Weaviate instance.
  • You can use the Weaviate Console to connect to the Weaviate Cloud Service to create managed Weaviate instances.
  • Because Weaviate uses GraphQL, you can easily query it with the console's GraphiQL integration.

What would you like to learn next?​


More Resources​

If you can't find the answer to your question here, please look at the:

  1. Frequently Asked Questions. Or,
  2. Knowledge base of old issues. Or,
  3. For questions: Stackoverflow. Or,
  4. For issues: Github. Or,
  5. Ask your question in the Slack channel: Slack.