Skip to main content

Security

Security is a top priority for ekoDB. Your data is protected with enterprise-grade features:

Encryption

  • End-to-end encryption - Data secure both at rest and in-transit
  • Encrypted IDs and operations - All database operations are protected
  • SSL enabled by default - Only HTTPS and WSS connections supported

Authentication & Access Control

  • JWT authentication - Enterprise-standard tokens with lifetime management
  • Collection-level permissions - Granular data access controls
  • Field-level access control - Read/write restrictions per field
  • API key management - Secure key rotation and management

Network Security

We do not believe in insecure connections. ekoDB only supports:

  • HTTPS - Secure HTTP connections
  • WSS - Secure WebSocket connections

We do not support insecure protocols:

  • ❌ HTTP
  • ❌ FTP
  • ❌ TCP (direct)
  • ❌ UDP

API Protection

  • Public endpoint: /api/health - Open for health checks
  • Protected endpoints: All other APIs require valid JWT token
  • Token validation: Every request is authenticated
  • Rate limiting: Protection against abuse

Best Practices

  1. Rotate API keys regularly - Use the dashboard to generate new keys
  2. Use collection-level permissions - Implement least-privilege access
  3. Monitor access logs - Review API usage in your dashboard
  4. Secure your tokens - Never commit API keys to version control
  5. Use environment variables - Store sensitive data securely

For security concerns or to report vulnerabilities, contact us at security@ekodb.io.