# Install krakend with Homebrew

Ultra-High performance API Gateway built in Go. Version 2.13.8 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:krakend
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install krakend
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:krakend
- **Package manager:** Homebrew
- **Version:** 2.13.8
- **Source summary:** Ultra-High performance API Gateway built in Go
- **Homepage:** <https://www.krakend.io/>
- **Repository:** <https://github.com/krakend/krakend-ce>
- **Last updated:** 2026-07-27T21:58:41+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- krakend (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 2.13.8
## Project history and usage

KrakenD is an open-source, Go-based API gateway built around stateless, declarative configuration. Its package-manager significance comes from turning API gateway deployment into a single binary plus a JSON/YAML configuration file, rather than a heavyweight service stack.

### Project history

KrakenD's own team page says the project started in late 2016 as a library for engineers to create fast and reliable API gateways. The Community Edition repository was created on GitHub on 2017-12-03 and describes KrakenD CE as the open-source distribution of KrakenD.

The project later separated the reusable gateway engine from the product distribution. KrakenD documentation says the engine was formerly the KrakenD Framework and became the Lura Project when it joined the Linux Foundation in 2021.

### Adoption history

KrakenD was adopted by teams using microservices and backend-for-frontend patterns because it emphasizes stateless nodes, declarative configuration, composition, rate limiting, telemetry integration, JWT/security features, and low operational overhead.

The official case-study and documentation corpus positions KrakenD as a production gateway for cloud-native and self-hosted environments, while Homebrew packaging gives developers a local CLI path for validating and running gateway configs.

### How it is used

The normal package-manager workflow installs the krakend binary, then runs it against a configuration file commonly named krakend.json. Official docs describe /etc/krakend/krakend.json as the default container-style path and krakend.json as the simple local configuration name.

KrakenD configurations declare endpoint arrays and backend relationships, with extra_config sections used by optional components outside Lura's core behavior.

### Why package nerds care

KrakenD is interesting because it packages an API gateway as a Go CLI/server binary with config-first operations. The Lura split also makes it a visible example of a productized open-source distribution built over a reusable framework governed separately.

### Timeline

- 2016: KrakenD started as a library for creating API gateways.
- 2017-12-03: The krakend-ce GitHub repository was created.
- 2019: KrakenD 1.0 was announced.
- 2021: The KrakenD Framework became the Lura Project under the Linux Foundation.
- 2022-06-15: KrakenD v2.0.5 recorded the organization rename from devopsfaith to krakend in the official changelog.

### Related projects

- Lura is KrakenD's engine and the direct framework-level related project. KrakenD also belongs to the broader API gateway ecosystem alongside products such as Kong, Tyk, and other reverse proxy or service-edge gateways.

### Sources

- <https://github.com/krakend/krakend-ce>
- <https://www.krakend.io/blog/announcing-krakend-1.0/>
- <https://www.krakend.io/blog/krakend-framework-joins-the-linux-foundation/>
- <https://www.krakend.io/changelog/>
- <https://www.krakend.io/docs/overview/>
- <https://www.krakend.io/docs/overview/lura-vs-krakend/>
- <https://www.krakend.io/team/>


## Security Notes

No matching local secret-handling manifest was found for krakend. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: /etc/krakend/krakend.json, krakend.json

## Combined YAML source

View the package source record on GitHub. [combined/krakend.yml](https://github.com/mxcl/pkgdb/blob/main/combined/krakend.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph