# Engine

> Why Monok v1 renders with the system's WebKit behind its own engine interface, and where its own Rust engine stands.

Canonical: https://monok.io/blog/category/engine.md

Blog category

How Monok renders pages, and what comes later.

Monok v1 renders pages with the WebKit that ships with macOS, behind an engine interface of its own. These posts explain that choice and the paused work on an engine written in Rust.

[Engine](https://monok.io/blog/category/engine) Oct 25, 2026 · 4 min

## [Why a Lightweight Browser Blocks Ads at the Network Layer](https://monok.io/blog/network-level-ad-blocking-lightweight-browser)

Why a lightweight browser blocks ads and trackers before requests are made: scripts never run, pages get lighter. How the built-in blocking in Monok works.

[Engine](https://monok.io/blog/category/engine) Oct 24, 2026 · 3 min

## [Building a Browser Engine in Rust: Where It Stands](https://monok.io/blog/building-a-browser-engine-in-rust)

How Monok is built in Rust: an engine trait with WebKit behind it for v1, native chrome drawn with vello_cpu, and the paused plan for its own engine.

[Engine](https://monok.io/blog/category/engine) Oct 23, 2026 · 3 min

## [Browser Engine Without Chromium: Why v1 Runs on WebKit](https://monok.io/blog/browser-engine-without-chromium-or-webkit)

Monok doesn't use Chromium. Version 1 renders pages with the Mac's WebKit behind an engine boundary, and its own Rust engine is a paused, long-term project.