Skip to main content
TopK regions determine where your data is physically stored and processed. Choosing the right region is important for latency, compliance, and data residency requirements.

​
What is a region?

A region in TopK maps to a specific cloud provider location where your collections and documents are stored. When you create a TopK client, you specify a region, and all operations are performed against that region.
TopK clients are region-specific.A client configured for aws-us-east-1-elastica cannot access collections in aws-eu-central-1-monstera and vice versa. You must create separate clients for each region.

​
Available regions

TopK is currently available in the following regions:
Region NameCloud ProviderCloud RegionLocation
aws-us-east-1-elasticaAWSus-east-1N. Virginia, USA
aws-eu-central-1-monsteraAWSeu-central-1Frankfurt, Germany

​
Choosing a region

Consider these factors when selecting a region:

​
Latency and performance

Choose a region geographically close to your users or application servers to minimize network latency:
  • North America users → aws-us-east-1-elastica
  • European users → aws-eu-central-1-monstera
Lower latency improves user experience, especially for interactive search applications where speed matters.

​
Data residency and compliance

Some applications have legal or regulatory requirements for where data can be stored:
  • GDPR compliance - If you need to keep EU citizen data in Europe, use aws-eu-central-1-monstera
  • US-based applications - For data that must remain in the United States, use aws-us-east-1-elastica

​
Cost considerations

Data transfer costs can vary by region. If you’re processing large volumes of data:
  • Store data in the same region as your application to minimize egress costs
  • Consider where your data originates and where it’s consumed

​
Specifying a region

You specify the region when initializing your TopK client: 
from topk_sdk import Client

# US East region
us_client = Client(
    api_key="YOUR_API_KEY",
    region="aws-us-east-1-elastica"
)

# EU Central region
eu_client = Client(
    api_key="YOUR_API_KEY",
    region="aws-eu-central-1-monstera"
)

​
Multi-region architecture

If you need to support users in multiple geographic locations, you can create clients for multiple regions: 
from topk_sdk import Client

# Initialize clients for multiple regions
clients = {
    "us": Client(
        api_key="YOUR_API_KEY",
        region="aws-us-east-1-elastica"
    ),
    "eu": Client(
        api_key="YOUR_API_KEY",
        region="aws-eu-central-1-monstera"
    ),
}

# Route queries based on user location
def get_client_for_user(user_region: str) -> Client:
    if user_region in ["EU", "UK", "DE", "FR"]:
        return clients["eu"]
    return clients["us"]

# Use the appropriate client
user_region = "EU"
client = get_client_for_user(user_region)
results = client.collection("products").query(...)
Each region requires separate collections. You’ll need to manage data synchronization between regions if you want to replicate data.

​
Region mismatch errors

If you try to access a collection that doesn’t exist in the specified region, you’ll receive a region mismatch error: 
Error: collection not found
To resolve this:
  1. Verify you’re using the correct region for your client
  2. Ensure the collection was created in the same region
  3. Check that you’re not mixing collections across different regions

​
Custom deployments

Need TopK in a specific region or in your own VPC?
For custom region deployments or private cloud installations, please contact our team at [email protected].
Custom deployment options include:
  • Additional AWS regions
  • GCP or Azure deployments
  • Private VPC deployments
  • On-premises installations

​
Next steps

Installation

Set up your client with the appropriate region

Quickstart

Build your first application

Create collections

Learn how to create region-specific collections

Architecture

Understand TopK’s organizational structure

Build docs developers (and LLMs) love

Get started for freeTalk to us