BoxLang Runtimes

Deploy ColdBox on BoxLang — MiniServer, Docker, DigitalOcean, servlet containers, desktop, and pre-compiled builds.

BoxLang is the recommended ColdBox runtime, and it offers the widest range of deployment targets. Every option below is documented in depth in the BoxLang book.

The Preferred Stack

# Install the pre-compiled ColdBox edition into the BoxLang engine
box install bx-coldbox

# Start your app on the BoxLang MiniServer
box server start serverConfigFile=server-boxlang.json

Using bx-coldbox gives you native compilation, faster startups, and BoxLang Prime across CacheBox, LogBox, and WireBox.

Runtime Options

MiniServer

BoxLang MiniServer is the lightweight, production-grade web server built for BoxLang — the default for new apps and the server CbGenesis ships with. Run it directly or through CommandBox.

Docker

Official images live at ortussolutions/boxlang. A minimal Dockerfile:

FROM ortussolutions/boxlang:miniserver
COPY . /app
WORKDIR /app
RUN box install
EXPOSE 8080
CMD ["box", "server", "start", "--no-open-browser"]

Full guidance: BoxLang Docker docs.

DigitalOcean App Platform

BoxLang apps deploy straight to DigitalOcean App Platform — point it at your repo, set the run command, done.

Servlet Containers (WAR)

Need Tomcat/Jetty or an existing Java EE estate? Package your app as a WAR with the boxlang-servlet runtime and deploy it like any Java web app.

Serverless

BoxLang runs on AWS Lambda and Google Cloud Functions — ColdBox REST APIs work well as function targets.

Desktop Applications

BoxLang apps can ship as cross-platform desktop applications — see Desktop Applications.

Production Notes

Pre-compile with Build.bx (included in the BoxLang template) for faster cold starts
Set enableNullSupport in Application.bx for full null handling
Keep boxlang.json and server.json in source control so every environment boots identically