MatchBox

BUILT FOR DEVELOPERS. BUILT FOR AI. BUILT TO SHIP.

One productivity platform, from first prompt to production

A modern, expressive language and batteries-included JVM runtime, paired with predictable conventions, developer tools, an AI framework, and a growing choice of runtimes. Developers and AI agents work in the same feedback loop.

01 / BUILD

One language, familiar tools

Write BoxLang, run it from the MatchBox CLI, and package applications for the runtime and target you choose.

Start with a script 02 / DEVELOP

Work effectively with agents

Give coding agents repository context, MatchBox skills, and executable checks. Agentic development is about building the app, not adding AI to it.

Agentic development 03 / ADD AI

Put AI inside applications

BoxLang AI connects application code to models, providers, tools, and agents. Validate module and provider support for the runtime you deploy.

BoxLang AI 04 / VERIFY

Test real user journeys

Explore bxPlaywright for browser automation, web-first assertions, visual checks, and browser artifacts in BoxLang projects.

Explore bxPlaywright

THE PLATFORM AT A GLANCE

A shared platform. Runtime choices for the work.

Developers and AI agents use BoxLang's language, conventions, and tools, then target the runtime that best fits the application.

01DevelopersDesign, build, decide

02AI agentsPlan, implement, verify

SOFTWARE PRODUCTIVITY PLATFORMBoxLang

Language + conventionsExpressive code, predictable structure

AI + agent toolingBoxLang AI, skills, MCP

Build + verifyDeveloper tools, bxPlaywright, bxSites

RUNTIME ABoxLang on the JVMCLI · web · containers · serverless · desktop

RUNTIME BMatchBox on RustNative · browser/WASM · WASI · ESP32

Runtime APIs and module support differ. MatchBox is an independent implementation of an evolving BoxLang subset; check compatibility for your target.

RUNTIME CHOICE

Choose the runtime for the job

The BoxLang platform is not tied to one deployment shape. The official JVM runtime and MatchBox's independent Rust VM serve different environments and have different compatibility boundaries.

THE FULL JVM ECOSYSTEMJVM

BoxLang on the JVM

Choose the JVM runtime when you need the broader BoxLang language and standard library, Java interoperability, or libraries and frameworks built for the Java ecosystem.

Java APIs and JVM library access
Broad BoxLang runtime and module coverage
Fits established JVM application infrastructure

Read the BoxLang documentation

AN INDEPENDENT RUST VMRUST

BoxLang with MatchBox

Choose MatchBox when a native executable, browser-oriented WebAssembly build, WASI workload, or microcontroller is the better destination.

Core native runtime does not require a JVM
Target-specific builds for browser, WASI, and ESP32
Rust Native Fusion for native-only extensions

See compatibility and target differences

Portability is a design choice, not a blanket promise. MatchBox implements a strict, evolving subset of BoxLang. Code that runs on MatchBox generally has a path to the JVM; JVM applications may use APIs that MatchBox does not provide. Check the target matrix before choosing libraries or moving an application.

ONE RUST RUNTIME, DIFFERENT TARGET PROFILES

Run close to the workload

Build for the host that makes sense: from a standalone desktop or server process to a browser, a WASI host, or an ESP32 device. APIs and runtime features vary by target.

Native executable

Bundle a MatchBox runner with compiled BoxLang bytecode. Ordinary native applications need neither Java nor a separate MatchBox install on the destination.

Browser and JavaScript

Ship an AOT JavaScript module, a raw WebAssembly binary, or the browser runtime for dynamic BoxLang execution.

WASI and containers

Run isolated WebAssembly workloads in compatible hosts such as Wasmtime or WasmEdge. Filesystem and network access depend on host capabilities.

ESP32 devices

Cross-compile the embedded runner for supported Xtensa and RISC-V boards. The embedded web surface is intentionally smaller than the native server.

UNDER THE HOOD

Built for portable execution, tuned where it counts

MatchBox compiles BoxLang scripts to VM bytecode. The native CLI adds a tiered Cranelift JIT that profiles hot code and compiles supported loops and functions; unsupported operations continue in the interpreter.

See where JIT is available and what it compiles

RustIndependent VM implementation

BytecodeCompile once for a compatible runner

CraneliftTiered JIT in the native CLI

JIT is not enabled in WASM, ESP32, or cross-deployed native runner stubs. See the target-specific guide before comparing performance.

AI-FIRST DEVELOPMENT

A useful agent loop ends with evidence

Give agents the same project context, runtime tools, and test feedback as the developer. Let evidence from each run shape the next change.

01ContextConventions + agent skills
02BuildDeveloper + AI agent
03Run + inspectRuntime tools + MCP
04TestBrowser flows + assertions
05ShipChoose a supported target

Feed the result back. Test reports, runtime observations, screenshots, and traces help developers and agents make the next change with evidence.

Runtime introspection over MCP and browser tooling depend on the selected runtime and integration. See Agentic Development and bxPlaywright for AI agents.

PART OF THE BOXLANG ECOSYSTEM

More productivity around the language

MatchBox is one runtime pillar in a wider toolkit. These projects complement BoxLang development; their integrations and runtime requirements are documented by each project.

BoxLangThe language and official JVM runtime.Explore BoxLang BoxLang AIAI capabilities for BoxLang applications.Explore BoxLang AI bxPlaywrightBrowser automation, assertions, and visual checks.Explore bxPlaywright bxSitesDocumentation and static sites built with BoxLang.Explore bxSites

READY TO BUILD?

Start with a script. Pick the runtime after.

Try MatchBox with a small BoxLang program, then use the compatibility guide to decide whether JVM or Rust is right for the application.

Start with MatchBox Read the BoxLang docs

Build with BoxLang.Choose your runtime.