Overview
Opening progressively: the routes on this page answer when the service is enabled for your account. Until then they answer 404 not_found. Ask support to enable it.
Galon Deploy builds a commit of your repository in an isolated sandbox, serves it as a preview with its own address, then promotes a verified preview to production on your domain. Every step is available in the console, in the galon CLI and through the API.
1. Connect a GitHub repository
Console › Deploy › Connect GitHub. Install the Galon GitHub App on the repositories you choose: Galon reads only those. The connection id (ins_…) identifies it in the CLI and the API. Galon detects the framework, the package manager (npm, pnpm or yarn) and the build command; you can override them in the build settings.
2. Your first preview
A test key with deploy:create and job:read starts a preview deploy. With --follow, the CLI runs each step until the preview is ready or failed.
export GALON_API_BASE="https://api.galon.ai/v1"
export GALON_API_KEY="gln_test_..."
galon deploy start --repository acme/site --commit <40-char sha> \
--installation ins_... --domain site.example --follow
galon deploy logs djy_... --follow
galon deploy listAPI: POST /v1/deploy/journeys with an Idempotency-Key, then POST /v1/deploy/journeys/{journey_id}/resume until status is ready (202 while a step is running, with Retry-After). Free preview quotas and build bounds: Limits.
3. Go to production
Production needs a live key and a production plan (GET /v1/deploy/production/plans, POST /v1/deploy/production/plan, prices in USD). A test key only makes previews: a production write with it answers 403 deploy_production_live_key_required. Promoting serves the verified preview of the test project twin.
galon promote djy_... --yes
galon deploy status4. Custom domain and TLS
POST /v1/deploy/production/domains with {"domain": "www.example.com"} returns the records to publish at your DNS host: a TXT record _galon-challenge.<domain> proves ownership, then a CNAME (subdomain) or A records (apex) route the traffic. Call POST /v1/deploy/production/domains/{domain}/verify once they are published. The TLS certificate is issued automatically, on demand, for a verified domain; nothing to upload.
5. Roll back
Production keeps the previous release. A rollback switches back instantly, without a new build. Choosing an older release by id is available on request.
galon rollback --yesEnvironment variables
Set variables in the console (Project › Variables). galon env pull writes the names of all variables and the values of public ones to .env.local (mode 0600). A secret's value is never returned by the API.
galon env pull --file .env.local
galon logs rti_... --lines 200Deploy webhooks
Subscribe a webhook endpoint (console › Webhooks) to deploy.created, deploy.succeeded, deploy.failed, deploy.promoted, deploy.rolled_back. They are signed like every Galon webhook (Galon-Signature).