Distributed multimodal database
Four data models.
One database.
Bring structured queries, semantic search and connected data into one database. Give your application more ways to find the right information, with fewer separate systems for your team to manage.
Query capabilities
Choose the query
for the task.
Start with one model. Add another as your application needs more ways to find and understand its data.
Filter and aggregate.
Look up records, apply conditions and calculate totals across your tables.
02 / VectorSearch by meaning.
Find semantically similar content using embeddings, even when the wording differs.
03 / GraphFollow connections.
Traverse relationships between records to explore their context and dependencies.
04 / Full-textFind the right words.
Search indexed text for matching terms and retrieve the passages they appear in.
In practiceSee how the four models can work together
For a charger lookup, graph finds compatible devices, SQL checks stock, vector finds the relevant setup guide and full-text locates a specific instruction. Your app connects the results using record IDs.
Explore the catalog code exampleWhat you can build
Put your data
to work.
Bring search, similarity and relationships into the features people use every day.
Explore all solutionsKnowledge search
Find relevant passages by their wording or meaning, then retrieve the source records for your application or AI workflow.
Recommendations
Discover similar items, follow their relationships and check record attributes before making a suggestion.
Fraud investigation
Explore connections between accounts, devices and transactions to help investigators spot shared patterns.
Behind the queries
Keep every result
linked to its source.
Record IDs let your application connect a search match to the original data and its relationships.
Explore the architecture- Give your records a shared identity
Reference the same record ID in your tables, relationships and search indexes so results can be traced back to their source.
- Prepare the indexes you need
Your ingestion code writes searchable text to the full-text index and stores embeddings in the vector index.
- Bring results together in your app
Use returned IDs to fetch source records and combine the context your application needs.
Connect your application
Connect the way you build.
HTTP API
Send requests for SQL, vector, graph and full-text queries. Work directly with the responses in your application.
Explore the APISQL clients
Use the current read-only PostgreSQL login to browse records and run supported queries. Use HTTPS for writes.
Connect a SQL clientSDK guides
Find installation and query examples for your language, with guidance on preview versions and API coverage.
Choose your SDKNeed to write data? Use the HTTPS API for writes and schema changes
Deployment & operations
A clear path
to production.
Choose where your database runs, who can access it and how you recover.
Deployment
Start on shared infrastructure, then choose dedicated resources in your region. Add an optional warm standby as your workload grows.
Explore deploymentAccess controls
Use database roles, row policies and column masks to control which records and fields a database user can read.
Review access controlsBackup & recovery
Plan how you will recover your data. Review backup retention, restore procedures and recovery options for your configuration.
Read the recovery guideChoose the capabilities you need. Features and capacity depend on your configuration and selected add-ons.
Compare plans