# Architecture

> Deep dives into how Elide works, each traced through the code and primary sources.

<!-- Generated by `bun run sync:architecture` from architecture/manifest.mts and editorial.mts; never edit it by hand. -->

Each deep dive is an interactive tour: animated diagrams you step through scene by scene, with a written summary
here.

## One managed heap across languages

[![Interactive tour: One managed heap across languages](https://elide.help/assets/architecture/gc-light.jpg)![Interactive tour: One managed heap across languages](https://elide.help/assets/architecture/gc-dark.jpg)](https://deepdive.elide.dev/gc?source=docs&from=/docs/architecture)

One heap across languages. Two collectors for different workloads: Serial keeps memory use low for CLI tools, desktop apps and low-traffic servers; G1 targets high throughput and short pauses for demanding servers.

[Learn more](https://deepdive.elide.dev/gc?source=docs&from=/docs/architecture) · [Read the garbage collection summary](https://elide.help/docs/architecture/gc)

## Memory-safe semantics, optimized

[![Interactive tour: Memory-safe semantics, optimized](https://elide.help/assets/architecture/memory-safety-light.jpg)![Interactive tour: Memory-safe semantics, optimized](https://elide.help/assets/architecture/memory-safety-dark.jpg)](https://deepdive.elide.dev/memory-safety?source=docs&from=/docs/architecture)

Elide carries memory-safety checks from the interpreter into optimized machine code, giving guest languages one foundation for safety and performance.

[Learn more](https://deepdive.elide.dev/memory-safety?source=docs&from=/docs/architecture) · [Read the memory safety summary](https://elide.help/docs/architecture/memory-safety)

## Native libraries, linked at build time

[![Interactive tour: Native libraries, linked at build time](https://elide.help/assets/architecture/native-substrate-light.jpg)![Interactive tour: Native libraries, linked at build time](https://elide.help/assets/architecture/native-substrate-dark.jpg)](https://deepdive.elide.dev/native-substrate?source=docs&from=/docs/architecture)

Elide ships native transport, cryptography and codecs in one executable. Every guest language shares that foundation.

[Learn more](https://deepdive.elide.dev/native-substrate?source=docs&from=/docs/architecture) · [Read the native substrate summary](https://elide.help/docs/architecture/native-substrate)

## Unified diagnostics

[![Interactive tour: Unified diagnostics](https://elide.help/assets/architecture/observability-light.jpg)![Interactive tour: Unified diagnostics](https://elide.help/assets/architecture/observability-dark.jpg)](https://deepdive.elide.dev/observability?source=docs&from=/docs/architecture)

Debug across languages in one session. Profile guest code, inspect the shared heap, and diagnose JIT behavior, regardless of language.

[Learn more](https://deepdive.elide.dev/observability?source=docs&from=/docs/architecture) · [Read the observability summary](https://elide.help/docs/architecture/observability)

## Many contexts, one engine

[![Interactive tour: Many contexts, one engine](https://elide.help/assets/architecture/threading-light.jpg)![Interactive tour: Many contexts, one engine](https://elide.help/assets/architecture/threading-dark.jpg)](https://deepdive.elide.dev/threading?source=docs&from=/docs/architecture)

Run independent tasks in parallel, call across languages on one thread, and reuse compiled code through a shared engine.

[Learn more](https://deepdive.elide.dev/threading?source=docs&from=/docs/architecture) · [Read the threading summary](https://elide.help/docs/architecture/threading)
