> For the complete documentation index, see [llms.txt](https://docs.opensoutheners.com/oss/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opensoutheners.com/oss/lambdary/getting-started/installation.md).

# Installation

Install Lambdary with Homebrew, Go, a prebuilt binary or the Docker image.

## Requirements

* Linux or macOS, on `amd64` or `arm64`.
* Go 1.26 or higher, only when you install with `go install`.
* Optionally Docker, Podman, Finch or nerdctl, for the [container backend](https://docs.opensoutheners.com/oss/lambdary/getting-started/how-it-works.md#two-execution-backends).

## Installing Lambdary

{% tabs %}
{% tab title="Homebrew" %}
Homebrew works on macOS and Linux:

```sh
brew install open-southeners/tap/lambdary
```

{% endtab %}

{% tab title="Go" %}

```sh
go install github.com/open-southeners/lambdary/cmd/lambdary@latest
```

{% endtab %}

{% tab title="Prebuilt binary" %}
Prebuilt binaries for Linux and macOS, `amd64` and `arm64`, are attached to each [GitHub release](https://github.com/open-southeners/lambdary/releases). Download the archive for your platform, extract it, and put `lambdary` somewhere on your `PATH`.
{% endtab %}

{% tab title="Docker" %}
The `ghcr.io/open-southeners/lambdary` image runs `lambdary dev` as a Docker Compose service:

```yaml
services:
  lambdary:
    image: ghcr.io/open-southeners/lambdary:latest
```

See [Docker Compose](https://docs.opensoutheners.com/oss/lambdary/guides/docker-compose.md) for the full setup.
{% endtab %}
{% endtabs %}

Check the install:

```sh
lambdary --version
```

## The process backend's emulator

Both backends run your code through AWS's [Runtime Interface Emulator](https://github.com/aws/aws-lambda-runtime-interface-emulator). The container backend uses the copy inside AWS's base images. The process backend runs it as a host binary.

Release binaries, including the ones Homebrew installs, carry that emulator built in and write it to `~/.lambdary/bin/` on first use. A `go install` build doesn't, so the first process-backend start clones AWS's pinned emulator source and builds it, which needs `git` and `go` once. The result is cached in the same folder.

{% hint style="info" %}
`LAMBDARY_RIE_PATH` points Lambdary at an emulator binary you already have, and `LAMBDARY_HOME` moves `~/.lambdary`. See [Environment Variables](https://docs.opensoutheners.com/oss/lambdary/configuration/environment-variables.md).
{% endhint %}

## Next steps

Head to the [Quick Start](https://docs.opensoutheners.com/oss/lambdary/getting-started/quick-start.md) to scaffold and run your first function.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opensoutheners.com/oss/lambdary/getting-started/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
