What else is connected?
Find neighbouring records and use their attributes to build a fuller view of a person, document or asset.
Neighbours & reverse lookupsGraph
Your data connects.
Make those links useful.
Follow relationships between records to find context, trace dependencies and investigate patterns. Keep those connections beside the data your application already uses.
Context through connections
Ask a connected question
See more than
a single record.
A connection can explain context, reveal a dependency or give an investigation its next step.
How are these related?
Explore bounded neighbourhoods and choose a path method to investigate the route between records.
Traversal & pathsWhich patterns stand out?
Use supported ranking and community methods to investigate influence and groups within your relationships.
Ranking & communitiesModel the relationship
Start with the references
already in your data.
Give a reference field a named relation so the database can follow it.
Source fieldrecords.topic_id
The reference on your record.
Named relationshipabout
Target keytopics.id
The record it connects to.
Define the connection.
Choose the source field, target key and relation name. Set the traversal direction your application needs.
Keep working with records.
The engine maintains declared relationships as rows are written, updated or removed.
Follow the relation.
Use the graph API or supported Cypher patterns to reach connected identities and records.
Choose your query
One connection.
Several ways to explore.
Choose a method that returns what your application needs: nearby identities, a neighbourhood, a route or the fields of connected records.
Explore the graph API01 Follow a declared relationship
Start with one record and inspect its neighbours. Use reverse lookups when the relation's configured direction supports them.
Neighbour endpoints return record identities. Fetch the underlying rows when your application needs their fields.
Explore one-hop queries02 Explore a bounded neighbourhood
Use breadth-first traversal to find records within a chosen number of hops. Keep the scope relevant to the question.
Choose a path endpoint when you need a route. Reachability and a materialized path are different results.
Explore traversal methods03 Return connected records with Cypher
Describe a supported pattern and return the fields your application needs from the matching records.
OriginChainDB implements a documented Cypher subset over declared relations. Check supported patterns before porting queries.
Read the Cypher guideConnected to the rest of your data
Make a search result
the start of discovery.
Use record IDs to move from a match to its source, then explore the relationships around it.
01
Find a starting point.
Use SQL, vector or full-text queries to locate the relevant records.
02
Add the connections.
Follow declared relationships to retrieve the context around a match.
03
Build the experience.
Combine the results your application needs for discovery, recommendations or investigation.
Graph capabilities and algorithms depend on your configuration. Compare plans and add-ons.
Build with OriginChainDB