Deploy CyberChef | (Just Updated) Data Decoder, Encoder and Analyser, Gzip-Served for a 3.9 MB Load

CyberChef self-hosted data decoder, encoder and cipher toolkit web app

Deploy CyberChef | (Just Updated) Data Decoder, Encoder and Analyser, Gzip-Served for a 3.9 MB Load

Just deployed

Deploy and Host CyberChef on Railway

Built for an LLM agent to deploy and use. The deploy form has no fields to fill, there is nothing to log in to, and the app is served compressed so the first load is about 3.9 MB instead of 13.6 MB. CyberChef is the "Cyber Swiss Army Knife" from GCHQ: a browser app with 400+ operations to decode, encode, hash, encrypt, decompress and parse data, from Base64 and hex to AES, JWT and file carving.

About Hosting CyberChef

This template runs one service, cyberchef: the upstream CyberChef v11.5.0 nginx image, pinned by digest, through a thin wrapper. One public domain serves the app, and the listener is on Railway's injected PORT. The healthcheck is GET /healthz. There is no volume and no variable: CyberChef runs entirely in the visitor's browser, so the server only hands out static files and stores nothing.

What the wrapper fixes. Upstream's nginx sends the 13.6 MB main.js uncompressed even though the build ships main.js.gz beside it. The wrapper enables gzip_static, so a client that accepts gzip downloads 3.97 MB instead (measured: 13,616,390 bytes against 3,973,592). It also sizes nginx workers from the container's cgroup rather than the host's cores, revalidates the unhashed bundles on every load so an upgrade is never served stale, caches the content-hashed fonts and images for a year, and adds nosniff and no-referrer headers.

Using it. Open the domain. To hand someone a ready operation, put the recipe in the URL fragment, for example https://DOMAIN/#recipe=To_Hex('Space',0). The fragment never reaches the server. The offline build is served too, at /CyberChef_v11.5.0.zip. Because the app has no server API, an agent that wants to run operations in code uses the cyberchef npm package (the Node API) and uses this deployment as the browser front end for people.

Agent contract

  • Public URL: https://RAILWAY_PUBLIC_DOMAIN (the generated domain of the cyberchef service)
  • Private URL: http://cyberchef.railway.internal:8080
  • Credentials: none; the deploy has no variables and the app has no login
  • Auth: none. CyberChef is a static site, so every GET is public and there is no write endpoint; a POST is refused with 405
  • Health: GET /healthz returns 200
#!/bin/sh
# needs: RAILWAY_PUBLIC_DOMAIN (the cyberchef service's public domain); also curl, grep, wc.
# write-auth: none - CyberChef is a static site with no write endpoint; a POST is refused, shown below
# signup: none - CyberChef has no accounts; it keeps no data on the server
R="https://$RAILWAY_PUBLIC_DOMAIN"
n=0
until [ "$(curl -s -o /dev/null -w '%{http_code}' "$R/healthz")" = 200 ]; do
  n=$((n+1))
  if [ "$n" -gt 60 ]; then break; fi
  sleep 5
done
curl -s -o /dev/null -w "health: %{http_code}\n" "$R/healthz"
curl -s -o /dev/null -w "page: %{http_code}\n" "$R/"
if curl -s --compressed "$R/" | grep -q 'CyberChef v11'; then echo "title: found"; else echo "title: MISSING"; fi
curl -s -o /dev/null -w "bundle: %{http_code}\n" "$R/assets/main.js"
# main.js goes out compressed to a client that accepts gzip: 3.97 MB instead of 13.6 MB
if curl -s -D - -o /dev/null -H 'Accept-Encoding: gzip' "$R/assets/main.js" | grep -qi '^content-encoding: gzip'; then echo "bundle gzip: yes"; else echo "bundle gzip: NO"; fi
BYTES=$(curl -s -H 'Accept-Encoding: gzip' "$R/assets/main.js" | wc -c)
if [ "$BYTES" -lt 5000000 ]; then echo "bundle under 5 MB: yes"; else echo "bundle under 5 MB: NO ($BYTES)"; fi
curl -s -X POST -o /dev/null -w "POST refused: %{http_code}\n" "$R/"
curl -s -o /dev/null -w "missing file: %{http_code}\n" "$R/not-here"

Expected output against a fresh deploy (measured on a Railway deploy of the generated draft):

health: 200
page: 200
title: found
bundle: 200
bundle gzip: yes
bundle under 5 MB: yes
POST refused: 405
missing file: 404

The refusals are the contract: POST refused: 405 and missing file: 404. CyberChef has no write endpoint and no account registration, so there is nothing else to open: the write-auth and signup lines in the snippet say so.

Why Deploy CyberChef on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying CyberChef on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

  • Agent-ready - no deployer fields, a contract block, and one script that proves the instance is healthy, compressed and refuses writes.
  • Fast first load - gzip_static turns a 13.6 MB bundle into 3.97 MB on the wire.
  • Your own copy - data you paste stays in your browser, and the page is served from a domain you control instead of a public instance.
  • Pinned - the upstream image is pinned by digest and the wrapper by tag and digest.

Common Use Cases

  • Incident response and forensics - decode payloads, carve files and parse timestamps on a host inside your own network.
  • CTF and security training - one shared CyberChef for a class or a team, with recipes shared as links.
  • Development debugging - Base64, JWT, hashes, JSON and regex checks without pasting secrets into a third-party site.
  • Data cleanup - convert formats, extract IOCs and URLs, and chain operations into a repeatable recipe.

Dependencies for CyberChef Hosting

  • The cyberchef service, created by the template. A custom domain is optional; the wrapper does not need the domain name.

Deployment Dependencies


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0