Connect a repo the way you would connect a WordPress site, only simpler
There is nothing to install on the site and no key to paste. Install the Em Region GitHub App on your organization, choose the repos, and add each one to your fleet.
What you get
Built for one organization
Keep every client repo in one GitHub organization and connect each repo on its own.
You choose the repos
The App only sees the repos you select in GitHub, and you can change that at any time.
Personal accounts work too
An organization is the best setup for a host, but it is not required.
Fresh after every push
A push to the main branch queues a new check, so the panel keeps up with the repo.
Why it matters
An Astro site has no admin area to install an agent into, and it does not need one. The repo already describes the site: its dependencies, config, hosting and CI. Reading the repo gives a fuller picture than a plugin could, with nothing extra running on the site.
Questions
Why does the App ask for write access?
One-click updates will open pull requests, which needs write access. Asking now means you will not need to approve the App again later. Monitoring only reads.
Can one customer see another customer's repos?
No. Every connection is checked with GitHub against the person making it, and every record is tied to one workspace.
Bring your whole fleet into view
We are onboarding a small group of hosts and agencies first.