Documentation
Connections
Providers
Use provider connections to make regions, sizes, images, SSH keys, repositories, branches, and DNS data available before launch.
Updated Jun 22, 2026
2 min read
What providers do
Providers give ForgedBase the accounts and metadata it needs to create infrastructure, deploy from source control, manage DNS records, and keep operational state visible. A provider connection should be treated as ready only after its latest metadata sync has completed successfully.
Before you connect
- Confirm who owns the cloud or source-control account.
- Check that billing, quotas, and regions are suitable for production work.
- Decide whether the provider should be shared across client projects or kept project-specific.
- Make sure the team member connecting the provider has the permissions required for the resources ForgedBase will manage.
Typical workflow
- Open the provider area in the dashboard.
- Connect the cloud or source-control provider.
- Complete the provider authorisation flow.
- Run or wait for the metadata sync.
- Review synced regions, sizes, images, SSH keys, repositories, branches, and account details.
- Use the synced provider data when creating servers or sites.
Checks before using a provider
- The connection is active.
- The latest sync is not failed or still running.
- Required regions, sizes, images, keys, repositories, and branches are visible.
- The provider account has enough quota for the planned launch.
- The workspace owner understands the provider billing path.
Common issues
- A server form has missing choices because provider metadata has not synced.
- A repository is connected, but the production branch is not visible yet.
- Provider credentials belong to one person and become a handover risk.
- A cloud account has a quota limit that blocks the selected server size.