A high-level checklist for preparing CortexDB for production use.
Production Checklist
Use this checklist before rolling CortexDB into a production environment.
Security and access
Protect access to the service
Require authenticated access for applications and operators. Store secrets in your standard secret-management workflow rather than in checked-in files.
Use trusted network boundaries
Place CortexDB behind your normal ingress, reverse proxy, or network controls. Do not expose self-hosted services more broadly than necessary.
Review tenant and environment boundaries
Make sure production tenants, workspaces, and environments are clearly separated in the way your applications use CortexDB.
Persistence and recovery
Use durable storage
Run production deployments on storage appropriate for a stateful service, not on ephemeral container filesystems.
Define backup and restore procedures
Backups should be automated, retained according to policy, and tested regularly with real restore exercises.
Plan for capacity growth
Estimate storage, traffic, and memory growth based on expected usage rather than waiting for operational pressure.
Operations and observability
Set up health monitoring
Use the health endpoint in your platform checks so you can quickly detect service availability issues.
Collect metrics and logs
Feed service metrics and logs into the monitoring tools your team already uses for alerting and incident response.
Document ownership and response paths
Make it clear who owns upgrades, incidents, backups, and operational changes for the deployment.
Scale and rollout readiness
Validate the initial deployment shape
Start with the simplest deployment that meets your needs, then scale out only when traffic, governance, or availability requirements justify it.
Test upgrade and maintenance workflows
Practice the steps for restarting, upgrading, and recovering the service before those actions are needed under pressure.
Confirm application behavior end to end
Verify the exact SDKs, APIs, connectors, and agent workflows your teams depend on before launch.
Pre-launch verification
# 1. Health check
curl https://your-cortexdb/v1/admin/health
# 2. Write test
curl -X POST https://your-cortexdb/v1/remember \
-H "Authorization: Bearer $CORTEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"content":"Production readiness test.","tenant_id":"production-check"}'
# 3. Recall test
curl -X POST https://your-cortexdb/v1/recall \
-H "Authorization: Bearer $CORTEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"production readiness test","tenant_id":"production-check"}'
# 4. Metrics check
curl https://your-cortexdb/v1/admin/metrics \
-H "Authorization: Bearer $CORTEX_API_KEY"