CyborgDB Service provides a self-hosted microservice deployment with REST API and client SDKs. This model offers the perfect balance between control and convenience - you maintain ownership of your infrastructure while enjoying the benefits of a service-oriented architecture.

Why Choose CyborgDB Service?

Faster Development
REST API and multi-language SDKs accelerate development across different teams and technology stacks.
Built for Scale
Designed for high-throughput production workloads with horizontal scaling capabilities and connection pooling.
DevOps Friendly
Docker-based deployment with comprehensive monitoring, logging, and operational tooling built-in.
Multi-Language Support
Native SDKs for Python, JavaScript/TypeScript, Go, and C++ - use your preferred language stack.

Deployment Options


Client SDKs

Access CyborgDB Service from any language using our comprehensive SDK collection:

Quick Start Paths

API Key Limitations

Free API Key Users: If you’re using a free API key, CyborgDB Service will automatically use cyborgdb-lite under the hood, which includes:
  • Up to 1M vectors maximum
  • 4 CPU threads limit
  • PostgreSQL and Memory backing stores only
  • No GPU acceleration
Upgrade to a paid plan to unlock cyborgdb-core with unlimited vectors, all backing stores, GPU acceleration, and full performance capabilities.

Architecture Overview

CyborgDB Service runs as a containerized microservice in your infrastructure: Key Benefits:
  • Language-agnostic API access
  • Horizontal scaling capabilities
  • Operational monitoring and logging
  • Production-ready deployment patterns

When to Use Service vs Embedded

  • Multi-language teams - Need to support different programming languages
  • Microservice architecture - Want to separate vector operations from application logic
  • Operational simplicity - Prefer service-based deployment patterns
  • Horizontal scaling - Need to scale vector operations independently
  • Team collaboration - Multiple teams need access to the same vector data
  • REST API preference - Want standard HTTP endpoints for integration

Production Considerations

Scaling and Performance

  • Horizontal Scaling: Deploy multiple service instances behind a load balancer
  • Connection Pooling: Configure database connections for high concurrency
  • Caching: Use Redis backing store for low-latency workloads
  • Monitoring: Enable telemetry and monitoring for production visibility

Security

  • API Key Management: Rotate keys regularly and use environment variables
  • Network Security: Deploy within private networks or use TLS/SSL
  • Database Security: Secure backing store connections and credentials
  • Access Control: Implement proper authentication and authorization

Next Steps

Ready to deploy CyborgDB as a scalable service? Start with our Docker Quickstart guide!