A small crew shipping tools, games, and infrastructure in public.
KBVE is an open-source studio and community that’s been building software since 2017. One monorepo, public CI, public roadmap, public game dev. If it’s worth building, it’s worth building where people can read the source.
- Founded
- 2017
- Repo
- One monorepo
- License
- MIT / Unlicense
- Funded by
- The community
What we ship
Four lanes, one monorepo. Each lane is independently usable and feeds back into the others.
Rust crates, Astro components, Python helpers, Bevy and Unity SDKs. Reusable building blocks for the rest of the stack — and yours.
Browse the monorepo →GamesOriginal titles built in Unity, Bevy, and Unreal — including Rareicon, ChuckRPG, and an isometric arcade hub. Source and design notes live in the same monorepo.
Visit the arcade →InfrastructureKubernetes, Cilium, Argo, Talos, Longhorn, KubeVirt — the platform under everything. Dashboards and runbooks are linked from the public dashboard.
Open the dashboard →Docs & guidesThis site. Engineering notes, game design docs, recipes, theory, and journal entries. Everything we learn we write down here.
Read the guides →How we work
A few principles that shape every PR, every commit, every stream.
Build in the open. Repo public, CI public, roadmap public. If you can read the code, you can review the decisions behind it.
One monorepo, many lanes. Tools, games, infra, and docs share a single Nx workspace so changes land consistently across the stack.
Permissive licensing. Most of what we ship is MIT or Unlicense. Fork it, ship it, sell it — just don’t pretend you wrote the parts you didn’t.
Small surface, sharp tools. We’d rather ship one well-tuned crate than ten half-finished ones. New abstractions earn their place.
Community-funded. No VC, no investors. GitHub Sponsors and Patreon keep the lights on, so the work answers to the people who use it.
The crew
KBVE is a community-first project — contributors come and go, the work stays public.
A small core team reviewing PRs, cutting releases, and running the public infrastructure. Decisions land in the repo, not in a back room.
Anyone whose PR landed. Issues, bug reports, doc fixes, art, audio — all of it counts. The contributor wall is the git log.
Saturday dev streams on Twitch. Discord runs 24/7 with announcements, build help, and game-night channels.
GitHub Sponsors and Patreon backers funding open-source work, bounties, and infrastructure. See the donate page for what that pays for.
Find us
Same crew, different surfaces. Pick whichever fits how you like to lurk.
The monorepo, releases, public discussions, and every CI run. Start here if you want the source of truth.
github.com/kbve →DiscordCommunity chat, dev help, game-night coordination, and the bot lab. Easiest place to say hi.
Join the server →TwitchLive dev streams — debugging in public, game work, infra tinkering. Catch us most Saturdays.
twitch.tv/kbvepoint →itch.ioGame builds, demos, and “name your price” releases. The storefront side of the studio.
kbve.itch.io →SteamWishlist upcoming KBVE titles. Rareicon and friends ship to Steam alongside itch.
Wishlist on Steam →ForumLong-form threads — feature requests, design discussions, bug triage. Lives on kbve.com so it’s searchable forever.
Open the forum →Get involved
Three doors. Walk through whichever fits. None of them require permission.
Issues labelled good first issue are picked
for newcomers. Submit a draft early — we’d rather pair on
a half-baked idea than wait for a polished one.
GitHub Sponsors and Patreon. Recurring support is the most useful — it lets us plan beyond the next month.
Ways to give →Hang outLurk in Discord. Show up to a stream. Post in the forum. Community presence is part of the work — not separate from it.
Open the server →