Frameworks

Remix on Stackap

Stackap does not recognize Remix yet: a Remix project is kept off the static path on purpose, and it can run only as a generic Node app if it has a start script, which has not been tested.

How Stackap recognizes Remix

Any dependency that starts with @remix-run/ disqualifies a project from the static-site path, because a Remix app renders on a server and its build output is not a folder of finished pages. Detection then continues down its list: there is no index.html at the root, so the plain-static case does not apply, and the only remaining match is a start script, which would make it a Node app.

What Stackap builds

If your Remix project has a start script, Stackap would generate the Node image: install with the package manager the lockfile implies, run the build script if there is one, and run the start script as an unprivileged user. Remix's starter templates usually define such a script, which serves the compiled server bundle.

The app would have to listen on the port Stackap passes in the PORT variable, and answer a health request on the default path or one you configure.

If there is no start script and no Dockerfile, the build is refused with a stated reason and whatever was live keeps serving. You can always bring your own Dockerfile, which Stackap uses in place of detection.

What a Remix project needs

• A start script that launches the production server and does not exit.
• The server reading PORT from the environment.
• A route that answers a health check.
• Secrets set through Stackap, not committed.

Verification status

Verification pending. No Remix app has been built on Stackap. The reasoning above comes from reading how detection works, not from running a Remix project.

What is tested is the generic Node path, with a toy API, and the rule that a project with no usable start script is refused.

Early-access scope

• Remix is not a supported framework today. Treat this page as an explanation, not a promise.
• Remix's server runs as a long-lived Node process, so the limits of the Node path apply: HTTP only, no persistent disk, one container per copy.
• Platform features that a Remix adapter may rely on, such as edge runtimes, are not available.

Questions

Last updated 2026-10-03.