Hyperspace is a cloud search database that leverages cloud hardware to enhance search speed and relevancy. Hyperspace uses a Search Processing Unit (SPU) virtual chip—a domain-specific architecture optimized for search tasks, to provide unmatched performance for real-time applications at scale, maintaining cost efficiency without compromising over logic complexity.
Hyperspace is a managed SaaS solution, combining hardware-level speed with software-level flexibility and designed to support a wide range of AI applications such as real-time recommendations, fraud prevention, Ad-tech, RAG, and threat detection.
Fast queries at scale
Hyperspace excels in delivering query results with minimal latency, even when dealing with billions of documents. Using designated processing units in the cloud, Hyperspace provides latencies that are 10 to 100 times faster than industry benchmarks, all while reducing costs. Furthermore, Hyperspace's search functionality is designed to operate at an extremely large scale without compromising on performance or stability.
Relevant search results
Hyperspace's hybrid search combines keyword search, term and value matching, with vector-based search, allowing a versatile and efficient approach to information retrieval. While vector search tends to excel at capturing semantic relationships, it behaves unexpectedly in many cases. A keyword search can pinpoint explicit matches and retrieve documents based on specific terms, improving relevancy when vector search falls short. Hyperspace hybrid search allows to create complicated functions, combining these two methods, and allowing comprehensive results with high relevancy.
Hyperspace documents store vectors and metadata
Hyperspace documents include fields with a variety of types, including keywords, numerical values, lists and vectors. The list of supported types is available under
Creating collections and ingesting documents
Hyperspace stores data under collections, each with its own index. Hyperspace allows to easily create and manage data collections, upload and modify data:
We call the search_dsl API to submit the query. In this call we specify the name of the query, the number of documents to return, and the collection name. The result of this call goes to the 'result' dictionary, containing the top document ids along with their scores.
JsonObject params = new JsonObject();
params.add("name", new JsonPrimitive("Bob"));
JsonObject query = new JsonObject();
query.add("query", params);
Object results = hyperspaceClient.searchDsl(collectionName, 10, query, "my_score_function");
JsonObject queryResults = new Gson().toJsonTree(response).getAsJsonObject();
let results = hyperspaceClient.searchDsl(search_query,
size=10,
collection_name=collection_name)
That's our first query!
In the following chapters, we'll discuss these features in greater detail.
Creating hybrid queries
Hyperspace score function allows you to specify the keyword search and vector search behavior in python syntax. Score functions allow filtering and scoring (including TF/IDF). Below is an example of a simple hybrid score function that filters the results based on two fields and applies score manipulation.
Basic score function
def score_function ( params, V ) :
score = 0.0
if match ( 'metadata 1' ):
score = 1.0
if match ( 'metadata 2' ) :
score = 2.0
else:
score = score + 1.0
return score + 2.0 * distance("vector_field")
Here is a simple keyword search followed by a vector search on the resulting documents. We specify how both scores will be merged via the boost parameter, in this example, the keyword search is given twice the weight of the vector search. Document 2 is used for the query documents.
In python client, you can provide either the function directly or the name of the file that contains the function. In Java client, you can only provide the name of the file.
Submitting a python query
Lastly, we call the search API to submit the query. In this call we specify the name of the hybrid query, the number of documents to return, the score function name, and the collection name. The result of this call goes to the 'result' dictionary, containing the top document ids along with their scores.