SVM

Getting started with SVM

Prepare a Luau source file and use the Trusted access workspace.

Access

Open Trusted access from your dashboard. Before approval, this page shows the application form or your current application status. Approved members and administrators see the SVM workspace. Submitting an application does not grant compiler access.

Compilation requires a deployment with the compiler API enabled. A development preview without authentication can select files but cannot submit them for compilation.

Prepare a script

Save Luau source as a UTF-8 .lua or .luau file of at most 10 MiB. For a minimal source example, create example.luau containing:

return 42

Choose one file in the workspace or drop it onto the file picker. You can replace or remove it before compiling. An empty file or an unsupported extension shows an error without replacing a previously selected script.

The page keeps your selected source in memory. Leaving the workspace, refreshing your program status, reloading the page or signing out clears the selection. Source files are not restored from browser storage.

Compile and download

On a deployment with compilation enabled:

  1. Choose your script and select Compile.
  2. Keep the page open while compilation is in progress. The file controls are temporarily disabled.
  3. On success, select Download bytecode and save the .slbc binary result before leaving the page.
  4. On failure, read the diagnostic. Correct source errors in your editor, replace the file and compile again. For a temporary failure, retry explicitly.

The result is compiled bytecode, not a text copy of your source. It requires a compatible SVM runtime. Execution of hosted output in a Volt client is still awaiting runtime integration verification; compilation and download alone do not establish runtime compatibility.

Compiler features

Use compiler macros to select code at compile time and function attributes to control how individual functions are compiled. Check the version and configuration notes before depending on a feature.

API access

The workspace shows the compilation endpoint for the current environment. Manage personal API tokens in account settings; tokens use your account's current permissions and do not grant Trusted Access membership.

Send a POST request with the original UTF-8 source as text/plain; charset=utf-8 and your token in Authorization: Bearer <token>. Successful responses contain binary application/octet-stream bytecode; failed requests return a public JSON error. Respect Retry-After when requests are throttled.

Back to SVM workspace