Infrastructure & Environment

Modular Runtime Separation

Separate application concerns can reduce blast radius and allow more targeted permissions, deployment rules, and monitoring.

Environment-Specific Configuration

Development, testing, staging, and production should use separate configuration and credentials. Production secrets must not be copied into lower environments unless specifically protected and approved.

• —Database and storage credentials
• —LLM provider keys
• —SMTP credentials
• —SSO settings
• —Webhook secrets
• —Encryption keys
• —Allowed domains
• —Logging and monitoring endpoints

Secure Email Transport

Rumbe can use ZeptoMail or another SMTP provider with TLS or SSL. Production certificate verification should remain enabled. A safeguard such as SMTP_REJECT_UNAUTHORIZED must not be disabled merely to bypass an invalid certificate.

Storage and Attachments

Customer uploads can be stored in an S3-compatible object store. Recommended controls include private buckets, encryption, tenant-scoped paths, short-lived signed URLs, malware scanning, lifecycle policies, and access logging.

Network and Provider Communication

Connections to model providers, vector infrastructure, payment systems, identity providers, and email services should use encrypted transport. Outbound endpoints should be restricted where practical, and inbound administration should be protected by strong authentication.

Availability and Recovery

Enterprise deployment review should address backups, restoration testing, queue durability, Redis persistence requirements, database recovery objectives, provider outages, rate limits, and fallback behavior when an LLM or vector service is unavailable.

Operational Security

Infrastructure security depends on patching, vulnerability management, access review, centralized logs, alerting, change control, backup protection, incident response, and documented ownership.