{Why Kinode?}

Simplifying dApp development

It turns out there's a lot that you can't (or shouldn't) do with a blockchain, and some processes are better left to an off-chain computing environment.

Empowering developers to build with a blend of on- and off-chain components

What if there was a simple way to build on blockchain's potential — without attempting to put so many operations onchain?

Kinode's innovative approach offers developers a streamlined path to harness blockchain's strengths while overcoming its constraints.

Why Kinode

On-chain when you need it to be, off-chain when you don’t

Kinode empowers developers to build with a blend of on- and off-chain components. We’ve handled primitives like identity, peer-to-peer, and chain integrations by building them straight into the OS and making it simple to get applications up and running.

A legible stack, designed for modularity at it’s core

Write apps in any language that compiles to Wasm, and each part of Kinode OS — from the virtual machine to the networking protocol — is modular. So you can easily plug in new features without disrupting the entire system.

Permissionless, composable,  built to last

Kinode is designed to be permissionless, composable, and enduring. Build freely with modular components that seamlessly integrate, empowering you to create scalable, future-proof applications.

Default-private and censorship-resistant

Kinode enables encrypted peer-to-peer communication and offers the data sovereignty that centralized platforms lack. Plus, distributed code can’t be censored or blocked.

An easier approach to dApp development

Networking, permissions, deployment, distribution, and even file management are all built into the Kinode system. Managing app state is a breeze, and you don’t have to bother with wrangling huge databases or making data persist between application launches.

A capabilities-based security model

Kinode’s composability is tightly-linked with its permissions system. Each component can be configured with specific permissions to minimize security risks. The permissions model is designed for smooth integration between components, resulting in a powerful balance between security and flexibility.

Get involved as a builder or community member