CyborgDB offers two deployment approaches, each optimized for different use cases and operational requirements. Both models are self-hosted and work with your existing database infrastructure.
Self-deployed REST API serviceDeploy CyborgDB as a standalone microservice that provides REST API access to confidential vector search. The service runs on your infrastructure and can scale independently from your applications.
Independent Scaling
Scale vector operations separately from your main application. Handle high query loads without impacting your core services.Self-Optimization
The service automatically optimizes index performance, manages memory efficiently, and adapts to query patterns over time.Multi-Language Access
One service deployment supports multiple applications and programming languages through REST API and client SDKs.Operational Simplicity
Centralized deployment, monitoring, and maintenance. Update vector search capabilities without touching application code.
Direct library integrationEmbed CyborgDB directly into your applications using Python or C++ libraries. This approach provides maximum control and performance by eliminating network overhead.
Maximum Performance
Direct memory access and zero network latency. Ideal for latency-sensitive applications requiring sub-millisecond response times.Deep Integration
Customize every aspect of vector operations. Perfect for specialized workflows and performance tuning requirements.Complete Control
Full ownership of the vector search stack. No external dependencies or service management overhead.Advanced Customization
Access to low-level APIs for custom index configurations, memory management, and algorithm tuning.
Multi-application architecture - Multiple services need vector search capabilities
Team scalability - Different teams use different programming languages
Operational simplicity - You want centralized vector search management
Independent scaling - Vector workloads need to scale separately from applications
Microservice patterns - You prefer service-oriented architecture
Start with embedded libraries for rapid prototyping, then scale to service deployment for production multi-application environments, or vice versa based on your specific requirements.