Luawl

Transparent image of encrypted compute hills
Transparent image of encrypted compute hills

  • New: Privacy and transparency

Unique obfuscation built on server-streaming.

Build now, start with server-gated security, and deploy securely within seconds.

Get started

Welcome back

Ready to obfuscate today, Alex?

-- Paste your Lua script to obfuscate.

Scripts

Obfuscations

Compute

Traces

Terrain Generator - 18.2k execs

Character Controller - 9.7k execs

World Generator - 4.9k execs

Pathfinding Module - 2.1k execs

Transparent image of encrypted compute hills

Intro

On runtime during an execution,
Luawl virtualizes your script
at runtime and sends back a
new, uniquely obfuscated build.

Scripts are compiled and run through the
custom Lua VM on a new, non-standard
instruction set built to virtualize each run.

For transparency to privacy,
Luawl is built to be a fully amnesic
a self-attestable obfuscation layer
hardware-isolated enclaves.

Core Features

Protection with a verifiable boundary

Luawl is a runtime obfuscator built around a zero-trust boundary, protected outputs, and independently verifiable handling.

VM

Runtime

Privacy

Transparency

Ask: Luawl privacy view verifying a protected execution record.
Luawl execution record with verification record, enclave proof, and run status.
Luawl runtime view showing a valid execution entry point.
Luawl protected execution settings view.

Configure your Luawl VM setting before obfuscation.

VM

Runtime

Privacy

Transparency

Ask: Luawl privacy view verifying a protected execution record.
Luawl execution record with verification record, enclave proof, and run status.
Luawl runtime view showing a valid execution entry point.
Luawl protected execution settings view.

Configure your Luawl VM setting before obfuscation.

Ask: Luawl privacy view verifying a protected execution record.
Luawl execution record with verification record, enclave proof, and run status.
Luawl runtime view showing a valid execution entry point.
Luawl protected execution settings view.

VM

Why Luawl

Protection built for secrecy, without sacrificing proof.

Luawl brings runtime protection, execution proof, and transparent boundaries into one service.

Protected execution

Every valid execution receives protected output.

Proof without exposure

Review each run through its verification record.

Obfuscated on submit

Each valid request is handled inside Luawl.

Built to forget

Request data is discarded after each run.

Runtime visibility

Track valid executions and activity.

Protected execution

Every valid execution receives protected output.

Proof without exposure

Review each run through its verification record.

Obfuscated on submit

Each valid request is handled inside Luawl.

Built to forget

Request data is discarded after each run.

Runtime visibility

Track valid executions and activity.

Protected execution

Every valid execution receives protected output.

Proof without exposure

Review each run through its verification record.

Obfuscated on submit

Each valid request is handled inside Luawl.

Built to forget

Request data is discarded after each run.

Runtime visibility

Track valid executions and activity.

What you get

Protect the source and verify every build.

Every valid execution receives protected output and a verification record.

Protected execution

Ship one loader, protect every valid execution.

Only valid executions receive protected output.

The loader does not expose the protected program.

Luawl VM workspace showing protected Lua execution controls.
Luawl VM workspace showing protected Lua execution controls.
Luawl verification workspace showing execution proof and handling status.
Luawl verification workspace showing execution proof and handling status.

Verifiable runs

Review each run without exposing the protected program.

Review each run and its outcome without exposing the protected program.

Verification stays separate from the program.

Runtime visibility

See every execution and runtime obfuscation.

Track attempts, valid executions, and verification signals across every project.

Clear signals from every valid run.

Luawl execution analytics showing protected runs and verification status.
Luawl execution analytics showing protected runs and verification status.

Integrations

Connect the systems behind your runtime

Luawl connects loaders, access controls, and internal tools to validate requests, deliver protected results, and trace every execution.

Loader endpoint

Deliver protected results without exposing the program.

Loader endpoint

Deliver protected results without exposing the program.

Loader endpoint

Deliver protected results without exposing the program.

Runtime API

Deliver protected results without exposing the program.

Runtime API

Deliver protected results without exposing the program.

Runtime API

Deliver protected results without exposing the program.

Authorization gate

Connect your execution requirements.

Authorization gate

Connect your execution requirements.

Authorization gate

Connect your execution requirements.

Webhook events

Track attempts, outcomes, and verification records.

Webhook events

Track attempts, outcomes, and verification records.

Webhook events

Track attempts, outcomes, and verification records.

Changelog

New features, fixes, and improvements

See all updates →

Privacy and transparency

Luawl can now show how a protected program was handled without exposing the program itself. Each valid run produces a verification record with its outcome and status.

Verification does not depend on our dashboard. Review the run record independently without exposing protected details.

Privacy and transparency

Luawl can now show how a protected program was handled without exposing the program itself. Each valid run produces a verification record with its outcome and status.

Verification does not depend on our dashboard. Review the run record independently without exposing protected details.

Execution receipts

We rebuilt how Luawl records executions. Every valid run now has a clear verification record you can inspect after completion.

Verification makes handling reviewable without exposing protected details. Requests that do not qualify remain separate from completed runs.

Transparency keeps each execution and its verification record together across the product.

Execution receipts

We rebuilt how Luawl records executions. Every valid run now has a clear verification record you can inspect after completion.

Verification makes handling reviewable without exposing protected details. Requests that do not qualify remain separate from completed runs.

Transparency keeps each execution and its verification record together across the product.

Loader authorization controls

Projects can now define execution requirements before protected output is returned. Existing access rules stay outside the protected runtime.

Valid executions receive protected output; requests that do not qualify stop before delivery. Records separate attempts from completed runs.

Loader authorization controls

Projects can now define execution requirements before protected output is returned. Existing access rules stay outside the protected runtime.

Valid executions receive protected output; requests that do not qualify stop before delivery. Records separate attempts from completed runs.

Protected execution model

Luawl now prepares supported scripts for its protected execution model. The loader is only the entry point; protected output is returned only for a valid execution.

Each valid execution is handled independently, with the details of that handling kept behind the service boundary. Support expands only as behavior preservation is proven.

Broader Lua support will follow as compatibility and behavior-preservation tests are completed.

Protected execution model

Luawl now prepares supported scripts for its protected execution model. The loader is only the entry point; protected output is returned only for a valid execution.

Each valid execution is handled independently, with the details of that handling kept behind the service boundary. Support expands only as behavior preservation is proven.

Broader Lua support will follow as compatibility and behavior-preservation tests are completed.

Pricing

Clear pricing plans that scale with you

Compare plans →

STARTER

Free

For small teams getting started with deploying.

Get Started

Team members: Up to 3

Obfuscations / mo: Credit based

Projects: Up to 3

Runtime obfuscation

Remote Attestation

Priority Queue

API access

BASIC

Yearly

$40

/month

For orgs with advanced security and scale needs.

Get Started

Team members: Up to 15

Obfuscations / mo: 100,000

Projects: Up to 15

Runtime obfuscation

Remote Attestation

Priority Queue

API access

PRO

Yearly

$110

/month

For growing teams to scale on actual compute with per-execution billing.

Get Started

Team members: Unlimited

Obfuscations / mo: Unlimited

Projects: Unlimited

Runtime obfuscation

Remote Attestation

Priority Queue

API access

STARTER

Free

For small teams getting started with deploying.

Get Started

Team members: Up to 3

Obfuscations / mo: Credit based

Projects: Up to 3

Runtime obfuscation

Remote Attestation

Priority Queue

API access

BASIC

Yearly

$40

/month

For orgs with advanced security and scale needs.

Get Started

Team members: Up to 15

Obfuscations / mo: 100,000

Projects: Up to 15

Runtime obfuscation

Remote Attestation

Priority Queue

API access

PRO

Yearly

$110

/month

For growing teams to scale on actual compute with per-execution billing.

Get Started

Team members: Unlimited

Obfuscations / mo: Unlimited

Projects: Unlimited

Runtime obfuscation

Remote Attestation

Priority Queue

API access

STARTER

Free

For small teams getting started with deploying.

Get Started

Team members: Up to 3

Obfuscations / mo: Credit based

Projects: Up to 3

Runtime obfuscation

Remote Attestation

Priority Queue

API access

BASIC

Yearly

$40

/month

For orgs with advanced security and scale needs.

Get Started

Team members: Up to 15

Obfuscations / mo: 100,000

Projects: Up to 15

Runtime obfuscation

Remote Attestation

Priority Queue

API access

PRO

Yearly

$110

/month

For growing teams to scale on actual compute with per-execution billing.

Get Started

Team members: Unlimited

Obfuscations / mo: Unlimited

Projects: Unlimited

Runtime obfuscation

Remote Attestation

Priority Queue

API access

FAQ

Answers to the questions that come up most.

Learn how Luawl works, how runtime builds and attestation are handled, and what to expect from every execution.

General

Plans & Billing

Privacy & Transparency

Got Questions?

Need help with a build or deployment? Our team is here to make things easy. Don’t hesitate to reach out.

Email us →

What happens when a loader is executed?

The loader can be run, but only a valid execution receives protected output. Requests that do not qualify stop there.

Does every execution follow the same path?

Each valid execution is handled according to its requirements. Internal handling details are not exposed.

What does the custom Lua VM protect?

The custom Lua VM changes how supported code is handled during an execution, keeping the protected program away from the public interface.

What does the public loader contain?

The public loader is the entry point for an execution. It does not expose the protected program or its internal handling.

How are loader requests authorized?

Projects can define what counts as a valid execution. Requests that do not meet those requirements stop before protected output is returned.

What can I track after deployment?

Projects can track attempts, completed executions, and verification status without exposing the protected program.

General

Plans & Billing

Privacy & Transparency

Got Questions?

Need help with a build or deployment? Our team is here to make things easy. Don’t hesitate to reach out.

Email us →

What happens when a loader is executed?

The loader can be run, but only a valid execution receives protected output. Requests that do not qualify stop there.

Does every execution follow the same path?

Each valid execution is handled according to its requirements. Internal handling details are not exposed.

What does the custom Lua VM protect?

The custom Lua VM changes how supported code is handled during an execution, keeping the protected program away from the public interface.

What does the public loader contain?

The public loader is the entry point for an execution. It does not expose the protected program or its internal handling.

How are loader requests authorized?

Projects can define what counts as a valid execution. Requests that do not meet those requirements stop before protected output is returned.

What can I track after deployment?

Projects can track attempts, completed executions, and verification status without exposing the protected program.

General

Plans & Billing

Privacy & Transparency

What happens when a loader is executed?

The loader can be run, but only a valid execution receives protected output. Requests that do not qualify stop there.

Does every execution follow the same path?

Each valid execution is handled according to its requirements. Internal handling details are not exposed.

What does the custom Lua VM protect?

The custom Lua VM changes how supported code is handled during an execution, keeping the protected program away from the public interface.

What does the public loader contain?

The public loader is the entry point for an execution. It does not expose the protected program or its internal handling.

How are loader requests authorized?

Projects can define what counts as a valid execution. Requests that do not meet those requirements stop before protected output is returned.

What can I track after deployment?

Projects can track attempts, completed executions, and verification status without exposing the protected program.

Blog

News and insights

Visit blog →

A lone tree in an open landscape representing a protected Luawl execution.
Why Every Valid Execution Gets Protected Output

Runtime

Jul 24, 2026

A branch against layered terrain representing Luawl’s protected execution model.
Inside Luawl’s Protected Execution Model

Engineering

Jul 17, 2026

A bird crossing a dark landscape representing independently verifiable handling.
How Obfuscation Becomes Self-Attestable

Product

Jul 10, 2026

A lone tree in an open landscape representing a protected Luawl execution.
Why Every Valid Execution Gets Protected Output

Runtime

Jul 24, 2026

A branch against layered terrain representing Luawl’s protected execution model.
Inside Luawl’s Protected Execution Model

Engineering

Jul 17, 2026

Get started today

Luawl is easy to set up, maintain, and use. It takes less than 5 minutes to get up and running.

Get a demo

Intel SGX

End-to-end encryption

Welcome back

Ready to obfuscate today, Alex?

-- Paste your Lua script to obfuscate.

Scripts

Obfuscations

Compute

Traces

Terrain Generator - 18.2k execs

Character Controller - 9.7k execs

World Generator - 4.9k execs

Pathfinding Module - 2.1k execs

Transparent image of sand dunes

, the runtime obfuscation interface by Luawl.