## The symptom
On a self-hosted Stormkit instance (v2026.08.02.1), following the Application
runtime docs for a Go binary to the letter: build the binary to
`.stormkit/server/app`, set the output folder to `.stormkit`, set the Start
command to `./app`. Every deployment failed with:
```
Error: cannot auto detect serverless entry file: expecting a file name called
(index|server).{js,mjs,cjs}
```
The presence of the `server/` subfolder routed the deployment into
serverless/SSR entry detection, and the Start command was never consulted, so
the documented config could not succeed.
## Why
A platform bug. The bundling logic treated any `server/` subfolder in the
output as a serverless entry and skipped the Start command entirely.
## The fix
Fixed upstream in PR #410: the Start command now takes effect, and a `server/`
folder no longer hijacks entry detection. If you are self-hosting, upgrade your
instance to a release after 2026-08-03 that includes the fix. The documented
config (binary at `.stormkit/server/app`, Start command `./app`) then deploys
normally.
## The general lesson
When the documented config cannot possibly succeed no matter how carefully you
follow it, suspect the platform, not your reading of the docs. A config option
that is silently ignored is almost always a bug on the other side.