Kiri Developers

EXAMPLES

Examples

Each example goes from setup to use to the code behind it, with the permissions it asks for and why. Four are plugins that work with real tools, one is the plugin from the tutorial, and one is a module. Read the one closest to what you want to build: they’re written to be copied.

Plugins and a module

What each one uses

The plugins between them use every place a plugin can have, and both kinds of box. The table shows where to look for each.

Cloudflare Tailscale Coolify Trivy no-latest
Runs as container container WebAssembly container WebAssembly
Share with ›, Deploy to ›, Scan with › Share Share Deploy Scan
Check before run before pull
Status bar note ✓ ✓ ✓ ✓
Menu item and commands ✓
Tab and page line ✓
Column Compose Images
Page or section section page
Settings Sharing Sharing Deploy Plugins
Secrets header header or program header
Websites Cloudflare’s Tailscale’s the server you type Trivy’s database none
Which example fits what you want to buildWhat does it do?Shares, deploys, scansjoins Kiri’s menu[adds] share, deploy, scanSays yes or nobefore a pull, build, run[adds] checksShows its own thingsnotes, tabs, columns, pages[window]Is your own serviceKiri runs it for youkiri.yamlCloudflare and Tailscale,Coolify, Trivyno-latest, thenTrivy’s checkCoolify (most places),Trivy (column and page)a module, not a plugin:the shop module
Which example to read first. Start from what your plugin does: a job Kiri already has goes in its menu; a rule goes in a check; your own screens go in places of their own. A program of your own that Kiri runs is a module.

Three of these plugins come with Kiri: Cloudflare, Tailscale and Coolify. Trivy is in the marketplace, made by Kiri. no-latest is the plugin Your first plugin builds from an empty folder.

© 2026 Kiri · The SDK is open source under the Apache License 2.0 · Docs · runkiri.com