Encryption Built Into Every Setting
Configuration Values Leave the Console Already Protected
No Raw Secrets in Deployment Files
When the Control Panel generates configuration values for a microservice, those values are encrypted before you ever see them.
What you copy into a service definition file is already protected — not a password, not a connection string, not a key.
The configuration material that reaches your deployment pipeline cannot be used directly even if intercepted.
Safe to Store, Safe to Distribute
Because the Control Panel encrypts every output value, those values are safe to store in your existing deployment tooling.
You do not need a secrets manager layered on top to protect them further.
The encryption is already there, applied uniformly to every setting the Control Panel produces.