Hi Fundamentally, it means about two different approaches: 1. Without workspace, it means one Polaris server == one Console 2. With workspaces, it means one Console == several Polaris servers
Initially, the intent was (1), but we discussed (2) as well. Personally, when I started the Console, I was more (1) as it's easier in terms of infrastructure (local to the server) and security (no proxy, etc), and the Console doesn't need any state/storage for the access to the different servers. I'm fine with the workspaces, even if it's a change in the paradigm. I will take a look at the workspaces PR. Regards JB On Sun, Feb 1, 2026 at 8:24 PM artur rakhmatulin < [email protected]> wrote: > Hi all, > I’d like to start a discussion on introducing "workspaces" in the Polaris > Console UI. > > The idea is to move away from environment-variable–based configuration > toward a UI-managed model, where a workspace represents an isolated Polaris > context (server, realm, and authentication). This allows a single console > instance to work with multiple realms and Polaris environments in a clean > and scalable way. > > A preliminary PR is available for review [1] > > Thanks, Artur. > > [1]: https://github.com/apache/polaris-tools/pull/138 >
