Self-host KrakenD with Levelrail

Stateless high performance API gateway on the official image. The install form carries krakend.json as an editable file, so it starts with a working route table instead of exiting on a missing config.

  • Authorkrakend
  • LicenceApache-2.0
  • Memory64 MiB
  • Services1

How to self-host KrakenD

  1. Pull the images

    One image is pulled on your server.

    Show images
    • krakend:3.0.3
  2. Create the app

    One service starts in a single Compose app, on port 8080.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Open the address followed by /__health to confirm the gateway is up, then edit the config file setting to add your endpoints and backends.

KrakenD requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8080
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then KrakenD. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the KrakenD docs page.

Deploy KrakenD your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy KrakenD from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain krakend=app.example.com.

levelrail-cli templates install krakend --name my-krakend

Deploy KrakenD with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/krakend/install \
  -d '{
    "name": "my-krakend"
  }'

KrakenD configuration

KrakenD services

ServiceImagePortsVolumes
krakend krakend:3.0.3 8080 none

KrakenD environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8080
Volumes
none

KrakenD FAQ

How much memory does KrakenD need?

The catalog lists about 64 MiB of memory for KrakenD.

Does KrakenD run on arm64?

For KrakenD, arm64 support is not confirmed; amd64 is unknown.

What licence is KrakenD under?

KrakenD is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does KrakenD need configuration before it starts?

No. The template fills in its own defaults.

Which ports does KrakenD use?

KrakenD listens on port 8080 inside the stack.

Can I deploy KrakenD on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for KrakenD, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image krakend:3.0.3 is what you deploy there.

levelrail-cli templates install krakend --name my-krakend