Ubicloud

Bring Ubicloud spend into CostGraph, per resource and per day

CostGraph estimates the daily cost of your Ubicloud virtual machines, PostgreSQL databases, Kubernetes clusters and machine images at Ubicloud’s published rates. Runner minutes come from your GitHub connection, so they are not counted twice.

CostGraph also flags GitHub Actions cache that no build has restored in a week, per repository. Those stale entries crowd out the ones your builds use.

Before you begin

• In the Ubicloud console, open your project and go to Tokens, then select Create Token. A token belongs to one project.
• Copy the project ID from the console URL. It starts with pj and follows /project/.

Connect it

Open Settings > Integrations, pick Ubicloud, and enter the token and project ID.

What you see

CostGraph lists your Ubicloud spend under these services:

Service	Covers
Ubicloud Compute	VM vCPUs, disks, and IPv4 addresses
Ubicloud PostgreSQL	Database vCPUs and storage, with standby servers shown separately so you can see what high availability costs
Ubicloud Kubernetes	Control plane and worker vCPUs, and worker storage
Ubicloud Machine Images	Stored image versions
Ubicloud Runner Cache	GitHub Actions cache per repository, at zero cost

Ubicloud behavior

• Costs are estimates at Ubicloud’s published rates, not your invoice. Credits, discounts, and the runner concurrency add-on don’t appear.
• CostGraph prices what is running when it syncs. A resource deleted during the day is missed, and one created during the day counts from the start of the day, except PostgreSQL databases and machine images.
• GPUs, inference, and resources Ubicloud hosts on AWS, Google Cloud, or your own cloud aren’t priced. A resource with no published rate shows zero cost.