Skip to main content
CyborgDB transforms traditional databases into Confidential Vector Databases by leveraging their storage capabilities while adding encrypted vector search functionality. Choose the backing store that best fits your existing infrastructure and operational requirements. CyborgDB RAG Overview

​
PostgreSQL

Production-ready relational database with vector extensions PostgreSQL provides robust data durability, ACID transactions, and excellent tooling ecosystem. CyborgDB leverages PostgreSQL’s reliability while adding encrypted vector search capabilities on top.

​
Key Benefits

ACID Compliance
Full transactional consistency for mission-critical applications with guaranteed data integrity. Rich Ecosystem
Extensive tooling, monitoring, and operational expertise available across the industry. Enterprise Scalability
Support for read replicas, connection pooling, horizontal scaling, and mature backup solutions. Best For: Production applications requiring data consistency, teams with existing PostgreSQL expertise, and environments requiring strict data durability guarantees.

​
Redis

High-performance in-memory data store Redis delivers ultra-low latency access patterns, making it ideal for real-time applications. CyborgDB uses Redis’s memory-optimized storage for blazing-fast vector search operations.

​
Key Benefits

Ultra-Low Latency
Sub-millisecond response times for vector queries with excellent concurrent access performance. High Throughput
Optimized for high-volume concurrent operations with flexible data structures beyond simple key-value storage. Configurable Persistence
Choose between speed and durability with flexible persistence and replication options. Best For: Real-time applications with strict latency requirements, high-throughput vector search workloads, and caching scenarios.

​
Standalone

For our embedded libraries, Standalone is referred to as “RocksDB”
Persistent local storage for embedded deployments Standalone provides persistent key-value storage directly on local disk, with no network dependency. This makes it the recommended backing store for embedded/local CyborgDB deployments where simplicity and reliability are priorities.

​
Key Benefits

No Network Dependency All data is stored locally on disk — no external database servers to configure or manage. Persistent Storage Data survives process restarts with automatic durability via write-ahead logging. Optimized for Embedded Use Low memory footprint with configurable caching, compaction, and compression settings. Best For: Embedded/local deployments, single-machine applications, edge devices, and scenarios where you want persistent storage without external infrastructure.

​
Memory

For our embedded libraries, Memory is referred to as “ThreadSafeMemory”
Local in-process storage for development and testing Memory-based storage keeps all data in local process memory, providing the fastest possible access with zero network overhead. Perfect for development, testing, and single-process applications.

​
Key Benefits

Zero Network Latency
Direct memory access without serialization overhead for maximum performance. Development Simplicity
No external dependencies or configuration required - instant setup for prototyping. Deterministic Performance
Predictable access patterns with complete control over memory usage. Best For: Development and testing environments, single-process applications, proof-of-concept scenarios, and ephemeral data requirements.

​
Future Backing Stores

CyborgDB is designed to be extensible, allowing for future backing stores to be added as needed. Have one in mind? Let us know!

​
Managed Services Support

CyborgDB works seamlessly with managed database services, reducing operational overhead while maintaining security and performance.

AWS

Amazon RDS for PostgreSQL
Fully managed PostgreSQL with automated backups and scalingAmazon ElastiCache for Redis
Managed Redis with cluster mode and automatic failover

Azure

Azure Database for PostgreSQL
Managed PostgreSQL with built-in security and monitoringAzure Cache for Redis
Enterprise-grade managed Redis with geo-replication

Google Cloud

Cloud SQL for PostgreSQL
Fully managed PostgreSQL with automatic maintenanceMemorystore for Redis
Secure and highly available managed Redis service

​
Choosing the Right Backing Store

  • Embedded Deployment - You want persistent local storage with no external dependencies
  • Edge Devices - Running on hardware without network access to databases
  • Simplicity - You want a single-binary deployment with built-in storage
  • Local Development - Persistent storage that survives restarts without infrastructure
  • Single Machine - Your application runs on a single machine

​
Configuration Examples

from cyborgdb_core import DBConfig

# Local RocksDB (default path: ~/.cyborgdb/data)
db_config = DBConfig("rocksdb")

​
Performance Characteristics

Backing StoreLatencyThroughputDurabilityConsistency
Memory~1µsVery HighNoneSingle Process
ThreadSafeMemory~1µsVery HighNoneThread-Safe
RocksDB~10µsHighLocal DiskSingle Process
Redis~100µsHighConfigurableEventually Consistent
PostgreSQL~1msMediumFullACID
Choose based on your application’s specific requirements for speed, durability, and consistency.