Self-host RedisInsight with Levelrail
A GUI for browsing keys, running commands, and profiling performance on any Redis instance.
- Authorredis
- LicenceSSPL-1.0
- Memory256 MiB
- Archarm64
- Services1
How to self-host RedisInsight
-
Pull the images
One image is pulled on your server.
Show images
redis/redisinsight:2.70
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5540.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
RedisInsight requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 5540
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- SSPL-1.0, source available
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 5540 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then RedisInsight. 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 RedisInsight docs page.
Deploy RedisInsight your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy RedisInsight from the CLI
levelrail-cli templates deploy redisinsight --name my-redisinsight Deploy RedisInsight with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/redisinsight/deploy RedisInsight configuration
RedisInsight services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| redisinsight | redis/redisinsight:2.70 | 5540 | redisinsight_data -> /data |
RedisInsight environment variables
| Variable | Service | Value |
|---|---|---|
| RI_APP_HOST | redisinsight | Preset by the template |
| RI_APP_PORT | redisinsight | Preset by the template |
| RI_ENCRYPTION_KEY | redisinsight | Generated at deploy |
Ports and volumes
- Ports
- 5540
- Volumes
- 1 named mount: redisinsight_data -> /data
RedisInsight FAQ
How much memory does RedisInsight need?
The catalog lists about 256 MiB of memory for RedisInsight.
Does RedisInsight run on arm64?
For RedisInsight, an arm64 image is published; amd64 is image published.
What licence is RedisInsight under?
RedisInsight is licensed under SSPL-1.0, which is source-available, so read the terms before commercial use.
Does RedisInsight need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does RedisInsight bundle?
The template includes Redis, running as part of the stack.
Which ports does RedisInsight use?
RedisInsight listens on port 5540 inside the stack.
Where does RedisInsight keep its data?
In a named volume: redisinsight_data mounted at /data.
Can I deploy RedisInsight 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 RedisInsight, 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 redis/redisinsight:2.70 is what you deploy there.