Build native Switch 2 homebrew.

A practical reference for kaiHEN application development, from your first NRO to graphics, JIT, and resident services.

Understand the runtime. Build with the right libraries. Keep source versions and verification scope close to the code.

Start building Explore the API reference

Start with a native build

Install the Switch 2 overlay on devkitPro, then build a small reference application. The Vulkan clear example gives you a focused first test of the native graphics path.

git clone https://github.com/ouncebrew/ounce-devkit.git
cd ounce-devkit
sh install.sh 20261114
make -C examples/vulkan-clear

Reference baselineounce-devkit 20261114 · kaiHEN 20261114cPrerequisites and full setup

Find your next step

Your first application Native entry, HEN status, input, and a clean exit.Graphics and UI Vulkan, OpenGL ES, presentation, and resolution.JIT and runtimes Staging, publication, code caches, and emulation.Plugins and IPC Resident services, discovery, and resource ownership.Port an existing app Library selection, platform boundaries, and case studies.Debug and verify Trace failures and test a complete application lifecycle.

The development stack

Each layer has a different job. Knowing which one owns a failure makes a port easier to debug.

kaiHEN: The resident environment and service interfaces that support native homebrew.
libounce: The libnx-compatible runtime and platform wrappers for Switch 2.
OunceVK: Native Vulkan, with EGL and OpenGL through Mesa's Zink.
ounce-devkit: The libraries, rules, toolchain overlay, and examples for your builds.

Understand the runtime architecture

Use the docs in your tools

Search and retrieve these same guides through a read-only MCP endpoint. Responses include section links, source references, and research dates.

https://kaihen.timsfun.com/mcp

Connection guide and available tools

Read the evidence with the guide.

This reference is based on the November 13, 2026 research snapshot. Source declarations, build checks, and console tests establish different things. See sources and verification scope.