Zebkit – Chromium's engine as a library you link, not a runtime you live in

Zebkit is Chromium's engine presented as a library that developers can link into their own applications, rather than a runtime that the application must run within. This library includes Blink, V8 with all JIT tiers, PDFium, FFmpeg, and more, without including any of Chrome's browser components or Electron's runtime. The application can maintain its own main() function and call into the engine as needed, rendering PDFs, compressing and encrypting data, handling URLs and image codecs, and accessing ICU libraries—all without needing any additional installation.

When the application needs to use the web, it can add a zebkit view, and when it needs PDFs, media, compression, or crypto, it can call on the engine's API directly, regardless of the language it's written in—C, C++, Rust, Python, or JavaScript. The engine is distributed as a package, which includes the library, a helper, the engine's data, and the necessary include files, and can be built using a single command.

It is designed to be sandboxed, with specific requirements for different operating systems, and its use of the engine can be controlled by the application itself, with default options that offer sensible behavior and the option for the application to override those defaults if needed.