Source control, chat notifications, webhooks and DNS providers.
GitHub, GitLab (including a self-hosted one) and Bitbucket, plus any other Git server through a Custom Git URL. Push to deploy needs one of the three connected hosts. See Connect GitHub and Connect GitLab, self-hosted GitLab and Bitbucket.
repo, admin:repo_hook and read:org. SrvYard checks the token with GitHub before saving it and tells you if one is missing. Without admin:repo_hook, push to deploy cannot register its webhook. See Connect GitHub so SrvYard can deploy your repositories.
GitLab uses a personal access token with the api and write_repository scopes. Bitbucket uses your username and an app password, not your email address or account password. See Connect GitLab, self-hosted GitLab and Bitbucket.
Create an incoming webhook in Slack or Discord, paste its address into SrvYard as a channel, press Test, then choose the events and severities it receives. A single site can also have its own channel. See Send notifications to Slack and Discord.
They send signed JSON about deployments, certificates and more to your own software. They need the Pro or Business plan and a public https address, and an organisation can have 20. See Send events to your own systems with outgoing webhooks.
No. Cloudflare is used only to prove you control a domain for certificate validation. You still create the A and CNAME records that point the domain at your server at your DNS host. See Connect Cloudflare for DNS validation.
Yes. A read-only token lets SrvYard draft your servers, sites and settings, and you then connect the real server and adopt its sites. Nothing is changed in the old panel. See Migrate from Laravel Forge, Ploi or VitoDeploy.