Adios
Apps and APIs · plans from $10/month

Deploy Go.Run the compiled binary.

Compile a Go service from the repository, start the production binary, verify its health endpoint, and promote the exact version you reviewed.

Deploy my projectDeploy a template
Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

Go

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

Go modulesCompiled binariesHTTP APIsWorkersWebSockets

The production path

A working Go project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Keep the Go build you already use

Use Go modules and the same go build command you run in CI. The release artifact is a small binary rather than a second, provider-specific project definition.

Promote the version that reports healthy

Bind the service to the declared port, expose a lightweight health route, and inspect startup or request failures before the candidate owns the production route.

Trace production back to source

Build output, runtime logs, health state, secrets, domains, and the promoted release stay attached to the project instead of being split across unrelated tools.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: orders-api
build_cmd: go build -o /app/server ./cmd/server
start_cmd: /app/server

runtime:
  name: go@1.25
  port: 8080
  health_path: /healthz
Adjust the package path, binary name, port, and health route to match the service.

Deployable starting points

Start Go from a template when the repository is not ready.

Start with Gin, Chi, or Fiber source that already includes a production entrypoint and Adios runtime contract.

API starters

Go Gin

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGo modules
Template key
go-gin
Runtime
go
Repository
templates
Source path
go/gin
git clone https://github.com/adiosdotdev/templates.git
cd templates/go/gin
adios up
DeployView source

API starters

Go Chi

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGo modules
Template key
go-chi
Runtime
go
Repository
templates
Source path
go/chi
git clone https://github.com/adiosdotdev/templates.git
cd templates/go/chi
adios up
DeployView source

API starters

Go Echo

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGo modules
Template key
go-echo
Runtime
go
Repository
templates
Source path
go/echo
git clone https://github.com/adiosdotdev/templates.git
cd templates/go/echo
adios up
DeployView source

API starters

Go Fiber

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGo modules
Template key
go-fiber
Runtime
go
Repository
templates
Source path
go/fiber
git clone https://github.com/adiosdotdev/templates.git
cd templates/go/fiber
adios up
DeployView source

API starters

Go Beego

Gin, Chi, Echo, Fiber, and Beego starters with compiled production binaries.

GoGo modules
Template key
go-beego
Runtime
go
Repository
templates
Source path
go/beego
git clone https://github.com/adiosdotdev/templates.git
cd templates/go/beego
adios up
DeployView source
Read the Go deployment guide

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • go build succeeds from a clean checkout.
  • The binary listens on the configured host and port.
  • A health route does not depend on optional downstream work.
  • Runtime credentials come from secrets or environment variables.

Preview when…

  • The build uses CGO or operating-system libraries.
  • The service needs a database, queue, or private network dependency.
  • Graceful shutdown or long-running connections need load testing.

Questions, answered

What to know before deploying Go.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can Adios deploy an existing Go project?

Yes. Run the Adios CLI from the project root, keep the repository and dependency files you already use, and add an adios.yaml file that describes the production build, start command, port, and health path.

Do I need Docker to deploy Go?

Not for a standard supported runtime. Use the project's normal production commands in adios.yaml. If the build needs unusual operating-system packages or native libraries, verify those dependencies in a preview before promotion.

Which Go frameworks have Adios templates?

The current catalog includes Gin, Chi, Echo, Fiber, and Beego starters. Plain net/http services can use the same Go runtime contract without adopting a framework.

Can a Go worker run without a public website?

Yes. Use a persistent start command for the worker and define the health behavior appropriate to that process. Confirm queue connectivity and shutdown handling in a preview.

What happens when the build or health check fails?

The candidate release keeps its build and runtime output for inspection. It must report healthy before it becomes the promoted version serving the application route.

Can I start from a template instead of an existing repo?

Yes. This page links to the closest official Adios Go starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

Related deployment paths

Connect the rest of the stack.

Browse all deployment pages

Deploy Python

Run a Python web app or worker with the dependency file, process command, health route, and secret-backed configuration kept beside the source.

Deploy Node.js

Deploy a persistent Node.js web process or worker from its existing package scripts, with release health, logs, secrets, routing, and Git history attached.

Deploy Adios workflows

Deploy scheduled jobs, webhook processors, approval gates, maintenance tasks, and operational automation from a versioned workflow manifest.

Deploy PostgreSQL

Choose a PostgreSQL version, keep database credentials out of Git, attach persistent storage, connect the application, and verify data after a restart.

The first release

Deploy Go with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.

Start with AdiosCompare plans