Deploy links with hangar.yaml#
A hangar.yaml at the root of a repository describes the services, databases, volumes and variables that a Deploy on Hangar link creates. The deploy page shows what the manifest will create and asks its questions before anything launches. The manifest's JSON Schema is published at /schema/hangar.v1.json, so editors complete and check the file as you write it.
Nine of the deploy guides now start with a one-click starter. See hangar.yaml and the Deploy button.
Domains#
- A domain can redirect to another host with a 301, 302, 307 or 308, keeping the path and query.
- Each domain shows whether it is valid, invalid or pending, from a live DNS lookup.
- The dashboard lists the exact records to create, with copy buttons.
- Adding a domain asks only for the hostname and suggests the apex and
wwwpair.
See Domains.
Pix and boleto#
Organizations in the Brazilian market can buy usage credit in reais with Pix or boleto. The credit carries over and is spent after the plan's own credit. The billing page also opens Stripe's customer portal for invoices and cards, and saving a card asks for 3D Secure when the bank requires it.
Deploys you can read#
- Every deployment log ends with how long each step took.
- A deploy started by a push shows as queued while it waits for a build server.
- Builds with the automatic builder keep their cache from one build to the next.
- When a new version fails to start and Swarm rolls it back, the log says how it died.
Improvements and fixes#
- Plan limits apply per service, as on Railway: CPU, memory and replicas are capped for each service.
- One AI agent connection can act in several organizations.
- Hangar's MCP server has its own address,
mcp.tryhangar.io. The old address redirects to it. - A trial without a card moves to the free plan when it ends.
- Health checks no longer hang a deploy when a region's manager is slow to answer.
