Why MetaScript?

TypeScript, now native.

Familiar syntax. Native binaries. No runtime overhead.

HTTP Server Throughputrequests/sec (higher is better)

1200K

NATIVE

Rust

1150K

NATIVE

→ MetaScript

1140Koptimized

NATIVE

→ MetaScript

840Kdefault

NATIVE

Bun

320K

RUNTIME

Deno

195K

RUNTIME

Node.js

78K

RUNTIME

* Synthetic benchmark on Apple M2 • MetaScript compiles to native C

Your TypeScriptcompiles to C

server.ms

import express from '@metascript/express';

const app = express();

app.post('/users', async (req, res) => {
  const user = new User(req.body.name, req.body.age);
  await db.insert(user);
  res.json({ ok: true });
});

app.listen(3000);

output.c

// Generated C - no runtime, no GC
void handle_post_users(Request* req, Response* res) {
  User* user = user_new(req->body.name, req->body.age);
  db_insert(user);
  response_json(res, "ok", true);
}

// ~50KB binary, <50ms cold start

npm create metascript@latest

Why Developers Choose MetaScript

TypeScript syntax you already know

C-level performance with zero learning curve

Native binaries - no V8, no runtime, no GC pauses

<50ms cold starts on AWS Lambda

~50KB binaries vs 50MB+ Node.js deployments

Tiny memory footprint - no runtime bloat

Get Started Learn More