What Elide is

A runtime, compiler, and toolchain.

Elide is an all-in-one platform that spans the full software development lifecycle. A single distribution compiles source, executes services, and orchestrates builds, consolidating responsibilities that traditionally require three separate toolchains into one cohesive product.

Runtime

A unified polyglot runtime for JavaScript, TypeScript, Kotlin, Java, and Python. The Node.js API surface is implemented on a Rust core with zero-copy I/O through io_uring, kqueue, and epoll. Languages interoperate in-process, so a Kotlin service can invoke Python without crossing a serialization boundary.

Compiler

Ahead-of-time compilation for Kotlin, Java, and TypeScript. GraalVM Native Image produces self-contained binaries with no JVM or Node.js dependency in production. TypeScript is transpiled by OXC without a tsconfig.json, and Elide serves as a drop-in replacement for javac, kotlinc, and tsc against existing source.

Toolchain

A single CLI for dependency resolution, builds, container image assembly, and local development. Build definitions are declarative and typed, authored in Pkl. Existing Maven, Gradle, and Bazel projects are supported without migration.

JVM Toolchain

A modern toolchain for the JVM.

The JVM underpins a significant share of enterprise software, yet its traditional build tooling carries meaningful configuration and startup overhead. Elide provides a modern alternative without requiring teams to leave the ecosystem: same artifacts, same dependencies, substantially faster feedback loops.

Developer experience

Familiar NPM-style CLI

A minimal command surface with a refined terminal interface.

Performance

Millisecond startup

Ahead-of-time compiled via GraalVM Native Image.

Configuration

Zero setup required

Convention over configuration. No plugins, no boilerplate.

Build language

Typed Pkl DSL

Declarative by default, imperative when needed, safe to refactor.

Compatible by default

Same inputs. Faster everything.

Elide is a drop-in replacement for your standard JVM tools like Maven, Gradle, and Bazel. Your existing code, dependencies, and workflows. Only faster.

	Elide	Maven	Gradle	Bazel
Cold start	~30ms	~3s	~6s	~10s
Config format	Pkl (typed)	XML	Groovy / KTS	Starlark
Zero config	✓	×	×	×
Native compilation	✓	×	×	×
Container images	Built-in	Plugin	Plugin	rules_oci
Multi-language	✓	JVM only	JVM only	✓
Learning curve	Minimal	Steep	Steep	Very steep

Foundations

An open, production-grade foundation.

Elide integrates mature open-source components that the industry already depends on, then delivers them through a unified interface. Each foundational technology is listed below for transparency and to invite review.

GraalVM Native Image

Polyglot VM and ahead-of-time native compiler from Oracle Labs

Truffle

Language implementation framework enabling cross-language interoperability

OXC

Rust-based JavaScript and TypeScript toolchain for parsing and transpilation

Pkl

Typed, declarative configuration language from Apple

Rust

Native core for I/O, networking, cryptography, and platform primitives

Kotlin

Primary language for runtime subsystems and guest-language bindings

SQLite

Embedded relational database used throughout the toolchain

mimalloc

High-performance memory allocator from Microsoft Research

About

Una breve historia de los runtimes

Cada década trae una nueva abstracción: el código se escribe más rápido, pero se ejecuta más lento.
Elide rompe ese patrón.

1970s

Código máquina & Ensamblador

El software se escribía directamente para el hardware. Rendimiento máximo, portabilidad nula. Cada máquina era una isla.

1972

C & Unix

Ritchie y Thompson demostraron que el software de sistemas podía ser portable sin ser lento. C se convirtió en el lenguaje común.

1991

Java & Python

Las máquinas virtuales y los intérpretes intercambiaron rendimiento por productividad. La empresa eligió Java. La ciencia eligió Python. La división comenzó.

2008

Chrome & V8

Google demostró que los lenguajes interpretados podían ser rápidos gracias a la compilación JIT. Llegó Node.js. Todos empezaron a escribir servidores en un lenguaje de navegador.

Now

Un solo archivo ejecutable. Su lenguaje favorito. Rendimiento nativo.