Skip to main content

Before you deploy: account, project, billing and API

Cloud Run needs a Google Cloud project with billing enabled. Do this once, in the Google Cloud console.
  1. Sign in. Open console.cloud.google.com and sign in with your Google account. If you are new to Google Cloud, create a Google Cloud account when prompted.
  2. Create or select a project. Open the project selector. To create one, open the Manage resources page, click Create Project, fill in Project name (4 to 30 characters), then click Create. Keep the project selected in the drop-down at the top of the console for the next steps.
  3. Check or link billing. Open the navigation menu (☰) and select Billing. If billing is active, the billing Overview page opens. If the console says This project has no billing account, click Link a billing account and choose an active billing account.
  4. Enable the Cloud Run Admin API. Open the Cloud Run Admin API page of the API Library, check that your project is selected, then click Enable. If you push your image to Artifact Registry, enable the Artifact Registry API the same way.
  5. Check your roles. To deploy, your account needs Cloud Run Admin (roles/run.admin) and Service Account User (roles/iam.serviceAccountUser) on the project.
The same steps with the gcloud CLI:
Sources: Google Cloud documentation, Cloud Run quickstart, creating projects, verifying billing, enabling APIs, all last updated on 30 September 2026. Console labels can change; if one differs, the linked page has the current wording.

Deploy

No procedure for this platform has been tested yet. What any deployment needs, taken from the Docker Compose stack:
  • the published images apowerb/apowerb (API, port 8000) and apowerb/apowerb-ui (interface, port 3000), at the tags pinned together in docker-compose/docker-compose.yml; nothing has to be built;
  • a PostgreSQL database, passed to the API as DB_HOST, DB_PORT, DB_NAME, DB_USER, DB_PASSWORD;
  • ENCRYPT_KEY, a Fernet key: openssl rand -base64 32 | tr '+/' '-_';
  • API_URL on the interface, set to the API’s internal address.
For a managed platform that runs a Compose file, the Hostman page is the closest tested reference.