Hi team,

I'd like to share some feedback on Vercel Connect, specifically regarding GitHub connector setup.

For some context, I'm building an AI agent with eve (eve.dev), and repositories are sometimes located in our clients'/partners' organizations. Because of this, being able to control exactly which organizations a connector can be installed into matters quite a bit for us.

To install a GitHub App across multiple organizations, GitHub itself requires the app to be made public. That's a GitHub-side constraint, not a Vercel one — but the side effect is that the app becomes available globally, so any organization can install it. For our use case, this is more permissive than we'd like.

When building a GitHub App from scratch, you can work around this by using the installation callback to filter and control which organizations are allowed to install the app. This isn't a built-in GitHub App feature — it's something you implement yourself in the installation flow. With Vercel Connect, that level of control isn't currently available.

It would be really helpful if Vercel Connect offered a similar capability — a way to restrict or allowlist which organizations can install a connector, on top of GitHub's public setting.

Thanks for considering this, and happy to provide more details if useful!