How applications connect to JetGraph
Pick the interface that matches your latency budget. gRPC is the native engine protocol. HTTP Cypher is universal. Bolt reuses compatible drivers for the supported query subset.
Official Rust client
The public crate/repository JetGraphClient talks gRPC with typed requests (velocity, context, ingest, schema). This is the highest-performance application path. Guide: Rust client docs.
HTTP / Cypher
POST http://localhost:8080/cypher with a JSON body {"query":"...","parameters":{}}. Any language with an HTTP client works. Guide: REST / Cypher API.
Bolt (compatible drivers)
Port 7687, demo auth empty user/password. Python neo4j driver, JavaScript neo4j-driver, and other official/community Neo4j drivers can run the supported openCypher subset. They will not make JetGraph emulate every Neo4j procedure. Guide: Bolt and Python.
Python beyond Bolt
gRPC protobuf bindings can call the same services as Rust. Bolt remains the fastest way to reuse existing Neo4j Python code for simple MATCH/CREATE.
Docker
Image alhascan/jetgraph-demo (engine binaries) and alhascan/jetgraph-ui-demo (Admin UI) are what the Quick Start compose file pulls. That is the documented install path on jetgraph.io.
Analytics sidecars
The demo compose can start segment-evaluator (port 8081) and pattern-miner (port 8082). They are separate processes that read the live graph — not extra Cypher dialects. Services documentation.