Why the console never sees a secret
DevSewa is split into an edge that owns nothing and an authority core that owns everything. Here is what that buys you.
Most developer platforms have one backend. The console talks to it, your app talks to it, and it talks to whatever infrastructure sits behind it. That is simple, and it means a bug in the console can read anything the backend can.
DevSewa is built differently, because it sits next to payment products on the same fleet and inherits their rules. There are two kinds of service. The edge — this site and the console — is stateless. It renders pages, checks your session and forwards a request with one header: who you are. The authority core owns the database, the registry of applications, and the credentials for every engine DevSewa mediates: identity, mail, vault.
The edge cannot reach an engine. It does not have the hostnames on its network, it does not have the certificates to trust them, and it does not have the shared secrets to sign a request. If someone compromises the console, they get a UI that can ask the core to do things on behalf of a signed-in customer — which is exactly what the console could already do — and nothing else.
What it means for you
The cost is one more service to deploy. The fleet already pays that cost for its payment products, so DevSewa got it for free — including a secret manager that materialises credentials into the core at deploy time and a runner that mints internal TLS. We did not have to invent any of it; we had to refuse to bypass it.