Why GCP
Fugaro runs in one Google Cloud project, and the reasons are Firebase's. Here is what the project holds, what Fugaro puts in it, and why a second cloud would split the thing in two.
One project
Fugaro's control plane is Firebase — the budget, the dashboard and the stats — and it is not behind the backend seam.
Source: docs/backends.md ·
A Firebase project is a Google Cloud project. The runs bucket, the custom roles, the job accounts and the images a run uses are resources of it, and fugaro setup is what provisions them.
Source: docs/gcp-setup.md ·
One Fugaro project is one Google Cloud project: the installation's APIs, roles, bucket, log isolation and budget live in it, and so do each repository's secret containers, registries, job accounts and jobs.
Source: docs/gcp-setup.md ·
A project created for Fugaro is a new project that holds only Fugaro's resources. The Terraform state it plans with, the spend history and the kill switch all live there rather than in your application's project.
Source: docs/design/managed-projects.md ·
Other clouds
A new project costs nothing by itself. What bills is the resources Fugaro creates in it.
Source: docs/design/m9-budget-and-dashboard.md ·
Nothing of yours moves: Fugaro works in the Google Cloud project you give it, one Firebase project serves one installation, and where your application runs is not a question this asks.
Source: docs/gcp-setup.md ·
Only GCP is implemented. A cloud is a backend behind the interface plus its provisioning, and the runner does not know which cloud it runs on.
Source: README.md ·
No other cloud offers this as one integrated project.
Source: docs/backends.md ·