Self-host ByteStash with Levelrail

Verified

A fast, self-hosted code snippet manager with syntax highlighting, tagging, and a built-in MCP endpoint for AI assistants.

  • Authorjordan-dalbyVerified by Levelrail
  • LicenceGPL-3.0
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host ByteStash

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/jordan-dalby/bytestash:1.5.13
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5000.

  3. Fill in the secrets

    6 settings are preset, 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.

ByteStash requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 tested
Ports
5000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0, copyleft license
  • Verified. Verified on arm64 with image tag 1.5.13. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 5000 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 ByteStash. 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 ByteStash docs page.

Deploy ByteStash your way

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

Deploy ByteStash from the CLI

levelrail-cli templates deploy bytestash --name my-bytestash

Deploy ByteStash with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/bytestash/deploy

ByteStash configuration

ByteStash services

ServiceImagePortsVolumes
bytestash ghcr.io/jordan-dalby/bytestash:1.5.13 5000 bytestash_data -> /data/snippets

ByteStash environment variables

VariableServiceValue
ALLOW_NEW_ACCOUNTS bytestash Preset by the template
BASE_PATH bytestash Preset by the template
DISABLE_ACCOUNTS bytestash Preset by the template
DISABLE_INTERNAL_ACCOUNTS bytestash Preset by the template
OIDC_ENABLED bytestash Preset by the template
TOKEN_EXPIRY bytestash Preset by the template

Ports and volumes

Ports
5000
Volumes
1 named mount: bytestash_data -> /data/snippets

ByteStash FAQ

How much memory does ByteStash need?

The catalog lists about 256 MiB of memory for ByteStash.

Does ByteStash run on arm64?

For ByteStash, arm64 is tested; amd64 is image published.

What licence is ByteStash under?

ByteStash is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does ByteStash need configuration before it starts?

No. The template fills in its own defaults.

Which ports does ByteStash use?

ByteStash listens on port 5000 inside the stack.

Where does ByteStash keep its data?

In a named volume: bytestash_data mounted at /data/snippets.

Can I deploy ByteStash on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id bytestash for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/jordan-dalby/bytestash:1.5.13 is what you deploy there.

levelrail-cli templates deploy bytestash --name my-bytestash