Minimize secret exposure.
OjasBase uses encrypted storage, scoped access and controlled runtime injection. Source tests do not establish that a real deployment is immune to leaks.
- AES-256-GCM encryption in source
- Project + environment + service scoping
- Normal API responses omit plaintext
- Role-protected changes and version history