Distributed multimodal database

One database.
Four data models.

Build search, agents, and connected applications with SQL, vector similarity, graph traversal, and full-text search in one managed engine.

Start free See how it works

Start freeScale with dedicated resources

SQLStructured records

VectorSemantic similarity

GraphConnected context

Full-textPrecise retrieval

One engine four data models

Why OriginChainDB

Your application needs
more than one kind of query.

One engine to work with: Keep structured records, vectors, relationships, and search indexes in one database.
Context you can connect: Use record identifiers to connect a search result to its source and related data.
Your application stays in control: Choose the queries, combine the results, and apply the rules that matter to your product.

01 / Four data models

Give each question
the right query.

Start with the model you need. Add other query types as your application grows.

SQL

Query your records.

Filter rows, join tables, and aggregate the data your application runs on.

01 / Explore SQL

Vector

Find similar meaning.

Search your embeddings for similar items, passages, and memories.

02 / Explore Vector

Graph

Follow relationships.

Traverse relationships to reveal the context between your records.

03 / Explore Graph

Full-text

Match the words that matter.

Retrieve relevant documents with ranked full-text and phrase search.

04 / Explore Full-text

Or ask in your own words.

Natural-language queries with /ask.Explore natural-language queries

02 / How it works

See how the pieces connect.

One support manual. Four useful ways to find the answer.

Knowledge searchInteractive illustration

01 Source record

passage:07

AX-7 service manual

Replace the battery when capacity drops. Disconnect power before servicing.

Product: AX-7
Version: 3

02 Choose a query

03 Inspect the evidence

SQL · matching record

Which passages cover AX-7?

passage:07

Battery replacement

Product AX-7 · version 3

Read the source row behind the result.

Prepared with separate writes. Your app writes records and text/vector indexes, supplies embeddings, and combines retrieval results.

03 / Inside the console

All your data.
One place to work.

Inspect rows, explore embeddings, trace connections, and read search results in the same workspace.

SQL Vector Graph Full-text

OriginChainDB console

Write SQL. Inspect results. Understand the plan.

Explore SQL

OriginChainDB SQL workbench with a SELECT query and five sample document rows.

Actual console · Sample data · Swipe to explore View full size ↗

04 / Built for developers

Start with a query.

Go from a table to an application result. Use SQL directly or send it over the HTTP API.

SELECT id, title
FROM public.documents
LIMIT 3;

curl --request POST \
  "$OC_URL/v1/tenants/$OC_TENANT/sql" \
  --header "Authorization: Bearer $OC_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"sql":"SELECT id, title FROM public.documents LIMIT 3;"}'

Example result3 illustrative rows

Illustrative records from a populated public.documents table; no query is executed on this page.
id	title
`doc-001`	Getting started
`doc-002`	Vectors and similarity
`doc-003`	Relationships in your data

Example only. No request is sent.

Get your connection details.
Set OC_URL, OC_TENANT and OC_TOKEN from your instance.
Open the quickstart
Create and populate the table.
This example requires public.documents with id and title columns.
Create your first records
Read your data.
Run the SQL in your workbench or send the HTTP request from your application.
Explore the query API

First-party SDKs

Connect your tools

PostgreSQL wire: limited preview. Elasticsearch: supported API subset.

05 / Deployment & operations

Start with an idea.
Build for production.

A managed database, in your region. Start free, then choose dedicated resources for your workload.

Your region. Your resources.Dedicated configurations run on single-tenant compute.

Connected across nodes.Add a warm standby with asynchronous replication.

Plan access and recovery.Configure access controls and daily snapshots for dedicated instances.

Explore deployment options

YOUR APPLICATION

Your chosen region

OriginChainDBPrimary engine

SQLVectorGraphFull-text

Asynchronous replication

Warm standbyOptional

Illustrative dedicated topology Read the details ↗

06 / Built around your workload

What will you
build with it?

Explore all solutions

RETRIEVE

Search & RAG

Retrieve passages by meaning and keywords, then give your model source-backed context.

Vector / Full-text / SQL

REMEMBER

AI agents

Keep run state, retrieve useful memories, and trace the records behind each step.

SQL / Vector / Graph

DISCOVER

Recommendations

Find similar items and connected interests. Apply your own eligibility and ranking rules.

Vector / Graph / SQL

INVESTIGATE

Fraud investigation

Follow shared accounts, devices, and transactions to inspect connected activity.

Graph / SQL

ADAPT

Personalization

Use session preferences and relevant content to shape what your application shows next.

SQL / Vector / Full-text

UNDERSTAND

Operational analytics

Group orders, count events, and inspect the records behind your application's metrics.

SQL

07 / Make an informed choice

Look inside.
Then put it to work.

Review the architecture, test your workload, and know what your application will own.

01Architecture

Understand what runs underneath.

Read about the engine, indexes, persistence, and replication.

02Benchmarks

Inspect the test before the number.

Check workloads, configurations, and methodology before comparing results.

03Compatibility

Check the queries your app needs.

Review supported SQL and adapter behavior before planning an integration.

A few things
worth knowing.

Have a specific workload?

Talk it through with us

What does multimodal mean here?

Four ways to work with data in one engine: SQL for records, vector search for similarity, graph traversal for relationships, and full-text search for words. Natural-language /ask is another query interface.

Explore the database

Does adding a record also create its embedding and search index?

Your application generates embeddings and uses the dedicated indexing APIs. Shared identifiers connect the results to their source records. Your application coordinates these writes and combines query results.

Read the vector data model

Can I use my existing database tools?

Use the HTTP API and SDKs, or supported wire and Elasticsearch adapters. Compatibility depends on the enabled adapter and its supported operations; check your queries against the integration guides.

Find an integration

How do I move from an experiment to production?

Start on the free tier, then choose a dedicated configuration for your workload and region. Review access controls, capacity, snapshots, and the optional asynchronous standby before launch.

Plan your deployment

From your first query to your next application.

Bring your data.
Build your next idea.

Start free Talk to our team

Or run your first query ↗

One database.Four data models.

Your application needsmore than one kind of query.

Give each questionthe right query.