Why is Vahana Hub tightly bound to the Vahana Org ID and App ID? Why isn’t it designed as an API Provider independent of org/app context?

Vahanahub
1

I’ve observed a challenge when managing multiple applications (e.g., Mobile and Web). In such cases, we need to configure and maintain Vahana Hub APIs separately for each application, which increases maintenance effort, reduces traceability, and adds additional configuration overhead. This also creates confusion instead of enabling centralized handling.

Is there any way to handle this centrally for multiple applications?

2

Yes,

Like any other API,

You can create one project on Vahanhub and can consume in any number of projects. There is no hard binding