# krakend mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für krakend in AI-Agent-Workflows.

## Installation

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

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install krakend
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:krakend
- **Paketmanager:** Homebrew
- **Paketmanager-Seite:** <https://formulae.brew.sh/formula/krakend>
- **Version:** 2.13.8
- **Quellzusammenfassung:** Ultra-High performance API Gateway built in Go
- **Homepage:** <https://www.krakend.io/>
- **Repository:** <https://github.com/krakend/krakend-ce>
- **Upstream-Dokumentation:** <https://www.krakend.io/docs>
- **Lizenz:** Apache-2.0
- **Quellarchiv:** <https://github.com/krakend/krakend-ce/archive/refs/tags/v2.13.8.tar.gz>
- **Zuletzt aktualisiert:** 2026-07-08T14:28:20Z
- **Generiert:** 2026-07-26T07:20:29+00:00

## Executables

- krakend (cli)
- krakend (Alias)

## Build-Abhängigkeiten

- go

## Installationsverhalten

- Post-install-Hook: nicht definiert
- Bottle: verfügbar auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux

## Version und Aktualität

- Seite generiert: 2026-07-26
- Manager-Version: 2.13.8
- Manager aktualisiert: 2026-07-08
- lokale Daten: OK
- Upstream-Repository: https://github.com/krakend/krakend-ce
- neueste erkannte Version: v2.13.8 (aktuell)
## Projektgeschichte und Nutzung

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

### Warum Paket-Nerds sich dafür interessieren

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.

### Zeitleiste

- 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.

### Quellen

- <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/>


## Sicherheitshinweise

Für krakend wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## 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
## Details aus der Quelldatenbank

- **Source Database:** Homebrew formula API
- **Tap:** homebrew/core
- **Full Name:** krakend
- **Version Scheme:** 0
- **Revision:** 0
- **Head Version:** HEAD
- **Bottle Stable Root URL:** <https://ghcr.io/v2/homebrew/core>
- **Deprecated:** no
- **Disabled:** no
- **Keg Only:** no
- **URL Keys:** head, stable


## Verwandte Links

- [Terminal utility packages](https://www.automicvault.com/de/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata.
- [Language runtime packages](https://www.automicvault.com/de/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata.
- [Networking and protocol packages](https://www.automicvault.com/de/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata.
- [Homebrew utility packages](https://www.automicvault.com/de/pkg/brew-utility-packages/) - Matched Homebrew package provider.
- [go](https://www.automicvault.com/de/pkg/brew/go/) - Build dependency declared by Homebrew.
- [gost](https://www.automicvault.com/de/pkg/brew/gost/) - Shares av.db curated category or tags: cli, go, networking, reverse-proxy.
- [traefik](https://www.automicvault.com/de/pkg/brew/traefik/) - Shares av.db curated category or tags: cli, microservices, networking, reverse-proxy.
- [algernon](https://www.automicvault.com/de/pkg/brew/algernon/) - Shares av.db curated category or tags: cli, go, networking.
- [aliddns](https://www.automicvault.com/de/pkg/brew/aliddns/) - Shares av.db curated category or tags: cli, go, networking.
- [bombardier](https://www.automicvault.com/de/pkg/brew/bombardier/) - Shares av.db curated category or tags: cli, go, networking.
- [caddy](https://www.automicvault.com/de/pkg/brew/caddy/) - Shares av.db curated category or tags: cli, networking, reverse-proxy.
- [chisel-tunnel](https://www.automicvault.com/de/pkg/brew/chisel-tunnel/) - Shares av.db curated category or tags: cli, go, networking.
- [coredns](https://www.automicvault.com/de/pkg/brew/coredns/) - Shares av.db curated category or tags: cli, go, networking.
- [varnish](https://www.automicvault.com/de/pkg/brew/varnish/) - Local package facts share a topical domain. Shared terms: cli, high, networking, performance, proxy.

## Combined YAML source

View the package source record on GitHub. [combined/krakend.yml](https://github.com/automic-vault/db/blob/main/combined/krakend.yml)


## Quellen

- Nucleus package database
- Geiger risk classifier
- package-page enrichment
- curated configuration and credential file locations
- curated package history
- package version freshness
- av.db category and tag curation
- package relationship graph
- cross-ecosystem install command graph
