Skip to content
Back to search

kite

Open source no-code Discord bot builder. Make slash commands, event listeners, buttons and modals in a visual flow editor, and host your bot for free.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/merlinfuchs/kite with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/merlinfuchs/kite'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/merlinfuchs--kite/badge.svg)](/listings/merlinfuchs--kite)

HTML

<a href="/listings/merlinfuchs--kite"><img src="/api/listings/merlinfuchs--kite/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 184 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # 🪁 Kite
  2. [![Release](https://github.com/merlinfuchs/kite/actions/workflows/release.yaml/badge.svg)](https://github.com/merlinfuchs/kite/releases)
  3. [![Docker image](https://github.com/merlinfuchs/kite/actions/workflows/docker-push.yaml/badge.svg)](https://hub.docker.com/r/merlintor/kite)
  4. [![Release](https://img.shields.io/github/v/release/merlinfuchs/kite)](https://github.com/merlinfuchs/kite/releases/latest)
  5. [![MIT License](https://img.shields.io/github/license/merlinfuchs/kite)](LICENSE)
  6. [![Discord Server](https://img.shields.io/discord/845800518458540083)](https://discord.gg/rNd9jWHnXh)
  7. Make your own Discord Bot with Kite for free without a single line of code. With support for slash commands, buttons, select menus, events, and more.
  8. ![Flow Example](./example-flow.png)
  9. Commands and event listeners are built as flows of blocks in a visual editor.
  10. - Blocks for messages, members, roles, channels, threads, polls and voice
  11. - Conditions, loops, error handling and stored variables for more complex logic
  12. - A Discord API Request block for anything else in the Discord API
  13. - HTTP Request and AI blocks to connect your bot to other services
  14. - Event listeners that run on Discord events, on a schedule or when a webhook is called
  15. - A flow AI that builds flows from a description
  16. - A [Marketplace](https://kite.onl/marketplace) with 150+ templates from Kite and the community, like moderation, modmail and a welcomer
  17. Kite is actively developed and new blocks and integrations are added regularly. If something you need is missing, open an issue or ask on [Discord](https://discord.gg/rNd9jWHnXh).
  18. ## Self Hosting
  19. > [!WARNING]
  20. > Self-hosting is not officially supported. These instructions are provided as-is for people who are comfortable running Docker, Postgres and their own Discord application. We don't answer self-hosting questions in issues or on Discord, and they may be closed without a reply. Bug reports that also affect the hosted version of Kite are welcome.
  21. This describes the easiest way to self host an instance of Kite by using a single binary that contains both the backend and frontend.
  22. You can find prebuilt binaries of the server with the frontend files included [here](https://github.com/merlinfuchs/kite/releases/latest).
  23. To run Kite you will also need to run a [Postgres](https://www.postgresql.org/) server alongside it, so it's recommended to use `docker-compose` to simplify the process.
  24. ### Configure the server
  25. To configure the server you can create a file called `kite.toml` with the following fields:
  26. ```toml
  27. [discord]
  28. client_id = "..." # Your Discord client ID used for Oauth2
  29. client_secret = "..." # Your Discord client secret used for Oauth2
  30. [encryption]
  31. token_encryption_key = "..." # HEX encoded AES key for encrypting Discord tokens
  32. ```
  33. To generate an encryption key for tokens you can use `openssl enc -aes-256-cbc -k secret -P -md sha1`.
  34. You can also set the config values using environment variables. For example `KITE_DISCORD__CLIENT_ID` will set the discord client id.
  35. ### Using Docker (docker-compose)
  36. Install Docker and docker-compose and create a docker-compose.yaml file with the following contents:
  37. ```yaml
  38. services:
  39. postgres:
  40. image: postgres
  41. restart: always
  42. volumes:
  43. - kite-local-postgres:/var/lib/postgresql/data
  44. environment:
  45. POSTGRES_USER: postgres
  46. POSTGRES_DB: kite
  47. PGUSER: postgres
  48. PGDATA: /var/lib/postgresql/data/pgdata
  49. POSTGRES_HOST_AUTH_METHOD: trust
  50. healthcheck:
  51. test: ["CMD", "pg_isready"]
  52. interval: 3s
  53. timeout: 30s
  54. retries: 3
  55. minio:
  56. image: pgsty/silo
  57. command: server --console-address ":9001" /data
  58. ports:
  59. - "9000:9000"
  60. - "9001:9001"
  61. environment:
  62. MINIO_ROOT_USER: kite
  63. MINIO_ROOT_PASSWORD: 1234567890
  64. volumes:
  65. - kite-local-minio:/data
  66. kite:
  67. image: merlintor/kite:latest
  68. restart: always
  69. ports:
  70. - "8080:8080"
  71. environment:
  72. - KITE_API__HOST=0.0.0.0
  73. - KITE_DATABASE__POSTGRES__HOST=postgres
  74. - KITE_DATABASE__POSTGRES__USER=postgres
  75. - KITE_DATABASE__POSTGRES__DB_NAME=kite
  76. - KITE_DATABASE__S3__ENDPOINT=minio:9000
  77. - KITE_DATABASE__S3__ACCESS_KEY_ID=kite
  78. - KITE_DATABASE__S3__SECRET_ACCESS_KEY=1234567890
  79. - KITE_DATABASE__S3__SECURE=false
  80. - KITE_APP__PUBLIC_BASE_URL=http://localhost:8080
  81. - KITE_API__PUBLIC_BASE_URL=http://localhost:8080
  82. volumes:
  83. - ./kite.toml:/root/kite.toml
  84. depends_on:
  85. postgres:
  86. condition: service_healthy
  87. volumes:
  88. kite-local-postgres:
  89. kite-local-minio:
  90. ```
  91. Run the file using `docker-compose up`. It will automatically mount the `kite.toml` file into the container. You should not configure postgres in your config file as it's using the postgres instance from the container.
  92. Kite should now be accessible in your browser at [localhost:8080](http://localhost:8080).
  93. ### Building from source
  94. #### Building the website
  95. You can download NodeJS from [nodejs.org](https://nodejs.org/en/download/) and enable pnpm with `corepack enable`.
  96. ```shell
  97. # Switch to the kite-web directory
  98. cd kite-web
  99. # Install dependencies
  100. pnpm install
  101. # Start the development server (optional)
  102. pnpm run dev
  103. # Build for embedded use in kite-service (recommended)
  104. OUTPUT=export pnpm run build
  105. # Build for standalone use
  106. pnpm run build
  107. ```
  108. #### Building the docs
  109. You can download NodeJS from [nodejs.org](https://nodejs.org/en/download/) and enable pnpm with `corepack enable`.
  110. ```shell
  111. # Switch to the kite-docs directory
  112. cd kite-docs
  113. # Install dependencies
  114. pnpm install
  115. # Start the development server (optional)
  116. pnpm run start
  117. # Build for production use
  118. pnpm run build
  119. ```
  120. #### Building the server (kite-service)
  121. Install Go >=1.26 from [go.dev](https://go.dev/doc/install).
  122. ```shell
  123. # Switch to the backend directory
  124. cd kite-service
  125. # or if you are in the kite-web / kite-docs directory
  126. cd ../kite-service
  127. # Configure the server (see steps above)
  128. # Run database migrations
  129. go run main.go database migrate postgres up
  130. # Start the development server (optional)
  131. go run main.go server
  132. # Build and include the kite-web files in the backend binary (build website first)
  133. go build --tags "embedweb"
  134. # Build without including the frontend files in the backend binary (you need to serve them yourself)
  135. go build
  136. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.