Why Ant?
Most JavaScript runtimes inherit their size and startup overhead from the engines they embed. Ant takes a different path: Ant Silver is a hand-built engine designed to be small and fast from the ground up. The result is a runtime that’s a fraction of the size of its peers while remaining WinterTC conformant.WinterTC refers to the WinterTC Minimum Common API specification — the standard for server-side JavaScript interoperability developed by Ecma TC55.
Ant vs. the alternatives
| Ant | Node | Bun | Deno | |
|---|---|---|---|---|
| Binary size | ~9 MB | ~120 MB | ~60 MB | ~90 MB |
| Cold start | ~5 ms | ~31 ms | ~13 ms | ~25 ms |
| Engine | Ant Silver | V8 | JSC | V8 |
| JIT | ✓ | ✓ | ✓ | ✓ |
| WinterTC conformant | ✓ | partial | ✓ | ✓ |
What you can build with Ant
Ant is designed for environments where binary size and startup time are constraints, not afterthoughts.Serverless functions
The ~5 ms cold start makes Ant a natural fit for function-as-a-service platforms where every millisecond of initialization counts.
Edge computing
A ~9 MB binary deploys easily to resource-constrained edge nodes without the overhead of a full V8 or JSC runtime.
Embedded systems
Ant’s small footprint makes it viable in environments where a 50 MB+ runtime is simply not an option.
CLI tools
Fast startup and a self-contained binary mean your CLI scripts launch instantly and ship as a single file.
Key capabilities
Ant supports the patterns you already know from other runtimes:- TypeScript — run
.tsfiles directly with no transpilation step or config file required - npm packages — install and import packages from the npm registry via
ant add - HTTP server — export a
{ fetch(req) }object as the default export to start a WinterTC-compatible HTTP server - FFI — call native libraries from JavaScript
- WebAssembly — run
.wasmmodules natively - Embeddable — embed Ant into your own application via the C API in
libant/