Kong Dev
Kong Dev provides prebuilt development, nightly, and pull-request container images for developers testing changes to the Kong open-source API gateway.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
50/100 Fair
- Maintained
- 100last commit 3 days ago
- Popular
- 2928 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 05 serious findings, CI, tests
Based on 4 of 5 factors.
Security check: 5 serious findings
- A private key is committed in the source code (api-specs/gateway/admin-oss/3.4/openapi.yaml:224)
- A private key is committed in the source code (api-specs/gateway/admin-oss/3.5/openapi.yaml:224)
- A private key is committed in the source code (api-specs/gateway/admin-oss/3.6/openapi.yaml:234)
- A private key is committed in the source code (api-specs/gateway/admin-oss/3.7/openapi.yaml:241)
- A private key is committed in the source code (api-specs/gateway/admin-oss/3.8/openapi.yaml:242)
Automated checks on commit 8b9fe57, 16 Nov 2026. Not an audit.
- GitHub stars
- 28
- Open issues
- 504
- Last commit
- 2026-11-18
- License
- MIT
- Activity
- steady
Checked 3 days ago - source: GitHub (Kong/developer.konghq.com)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Prepare Kong's database first Run `kong migrations bootstrap` before `kong start`. This prepares Kong's database for a fresh install, and without it Kong can fail to start. source
- Use the same config file for both steps Kong reads `/etc/kong/kong.conf` by default, but you can pass `-c /path/to/your/kong.conf` to both commands. Using a different or missing config file can make Kong use the wrong database or settings. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I run before starting Kong on a fresh install?
Run kong migrations bootstrap before kong start. Use the same config file for both steps to avoid Kong using the wrong database or settings.
Can Kong fail to start with the default Docker Compose configuration?
A self-hosted report says Kong fails to start with default Docker Compose configuration. The report was on Ubuntu 24.04 and was not attributed to Windows-style line endings.
Why might some pages be missing when generating the Kong developer docs locally?
Some page generation is skipped by default for performance. Comment out the entire skip section in jekyll-dev.yml to generate the entire site locally.
Which Kong CLI is listed for API lifecycle automation?
decK is listed as a command-line tool for API lifecycle automation. It is described as offering commands to orchestrate and automate API delivery.
Answers sourced from developer.konghq.com, github.com, github.com, github.com
Community
- Kong Nation (forum)
Collected 48 days ago - public community threads