Self-host
Run it on your own box. Zero lock-in.
A single Go binary. Open source. Deploy in three minutes to Railway, Fly, Render, or Docker — or build from source and run it locally.
Why
Three reasons to self-host.
Videos never leave your network. Useful for confidential, regulated, or large-volume workloads.
Run as many concurrent jobs as your hardware allows. We don't gate you on volume.
Pure Go binary plus open-source server code. Fork it, modify it, ship it.
Install
One binary. Four ways to install.
The MCP binary is a thin client that forwards to a backend. By default it talks to our hosted backend; set SUBTITLESKING_URL to point it at your own.
# Grab the latest release for your platform
curl -L https://github.com/kirillzubovsky/subtitlesking-mcp/releases/latest/download/subtitlesking-mcp-darwin-arm64.tar.gz \
| tar -xz
sudo mv subtitlesking-mcp /usr/local/bin/
# Run against the hosted backend (default)
subtitlesking-mcp --version
# Or point at a local upload-server
SUBTITLESKING_URL=http://localhost:8080 subtitlesking-mcpConfiguration
Two env vars. That's it.
# Where the MCP bridge forwards JSON-RPC calls
SUBTITLESKING_URL=https://brains.subtitlesking.com # default
# e.g. http://localhost:8080 for fully self-hosted useThe bridge no longer needs an API key — every tool call is forwarded verbatim to <SUBTITLESKING_URL>/mcp, which mints its own presigned URLs internally. Override SUBTITLESKING_URL for full self-host. See the self-host docs for system requirements (ffmpeg + Whisper).
Find us in the registries
Listed in the MCP ecosystem.
Want a fully air-gapped subtitle pipeline?
Run the upload server, Whisper, ffmpeg, and the MCP binary all on your own hardware. The full guide walks through every step.