Metascript
Why Metascript?

TypeScript Syntax.
Native Performance.
Three Runtimes.

Write once in familiar syntax. Compile to C for Lambda, JavaScript for browsers, or Erlang for distributed systems. No runtime overhead.

See it in actioncompiles to 3 targets
input.ms
@derive(Eq, Clone, Debug)
class User {
  name: string
  age: number
}

const user = new User(
  name: "Alice",
  age: 30
)
output (C, JS, or Erlang)
// Auto-generated methods:
user.equals(other)  // deep equality
user.clone()         // deep copy
user.toString()      // debug repr

// + native binary OR
// + browser bundle OR
// + BEAM bytecode
npm create metascript@latest

One Language, Three Runtimes

C Backend
Lambda, CLI, Edge
Cold Start<50ms
Performance~90% of C
Binary Size~1MB
JavaScript
Browser, Node, Bun
Cold Start~200ms
EcosystemFull npm
Bundle Size~50KB
Erlang
Distributed, OTP
Uptime99.9999%
Hot ReloadYes
ConcurrencyMillions

Why Developers Choose Metascript

TypeScript syntax you already know

Native performance without learning C or Rust

Compile-time metaprogramming with @derive, @comptime

One codebase deploys to Lambda, browser, or distributed systems

Real static types (not just hints like TypeScript)