Galon Deploy

How do I deploy from GitHub with a spend cap?

Connect your GitHub repository to Galon Deploy: each commit is built in an isolated sandbox, served at a preview address and promoted to production when you choose. Every cost is paid from a prepaid balance, so spending stops at your balance and at the cap you set yourself; Galon sets no hard cap of its own.

Steps

  1. Connect the repositoryConnect your GitHub repository to your project from the console.
  2. Deploy a commitFrom the CLI, the API or your agent; the build runs in a sandbox and returns a preview address.
  3. Promote itPromote the preview you like to production, on your own domain if you want.

Deploy from the command line

# paste your key once
galon login

# a static site: the folder goes up as an archive, the CLI follows the steps
galon deploy ./dist

# or a commit of a connected repository
galon deploy start --repository akwaba/site --commit 4f2a9c1 --follow

Why a prepaid balance works as a cap

A deploy reserves its cost before it runs. When the balance cannot cover the next paid action, that action pauses: there is no invoice after the fact. You can set your own cap with an alert in the console.

What it costs

Running sites are priced per CPU-second, GiB-hour and GiB transferred, and preview deploys include 10 free deploys per account and UTC day.

Galon Deploy: prices and limits

Galon Deploy: prices read from the served price list, paid from a prepaid balance.
Plan or modelIncludedPricePer unit
Free10 preview deploys per account and UTC day, 1 preview builds running at once per account (the next one waits)$0No monthly fee
cpu_secondPay as you use$0.000011 per CPU-second—
gb_hourPay as you use$0.0105 per GiB-hour—
egress_gbPay as you use$0.055 per GiB transferred—
Galon Deploy: limits, read from the platform code. Galon sets no hard spending cap: you set your own.
LimitValue
Free preview deploys per account and UTC day10
Free preview builds running at once per account (the next one waits)1
Builds running at once on the shared builders (first come, first served)2
Dependency install time10 min
Build time15 min
Total time of a build20 min
CPU per build2 vCPU
Memory per build3 GiB
Workspace per build (counted in memory)1,536 MiB
Processes per build512
Dependency cache per project (emptied beyond)1 GiB
Build log lines kept20,000
Archive uploaded25 MiB
Files per archive512
One file in an archive2 MiB
Content of an archive, in total10 MiB

Let your agent ship
Never overspend