# Overview

<figure><img src="/files/MVe7qUsgQdwUvDc1UVPi" alt=""><figcaption></figcaption></figure>

KRNL Studio is a visual builder for developers who are tired of wiring together APIs, smart contracts, and AI services by hand. Instead of writing glue code for every new feature, you drag blocks, connect them, and run the whole thing like a flowchart.

**Try it live:** [https://studio.krnl.xyz](https://studio.krnl.xyz?utm_source=chatgpt.com)

You can think of it like Zapier or GitHub Actions, but built with blockchain and AI in mind from day one. Every part of your workflow runs in a secure execution environment that generates cryptographic proof, so you are not just assuming it worked — you can verify it.

This is not a toy for demos. It is designed for real production workflows:

* Build complex blockchain logic without drowning in boilerplate
* Drop in AI models as decision points anywhere in the flow
* Run everything inside isolated, attestable containers
* Deploy workflows instantly with one command

If you have ever written a script that says “fetch data → process it → sign → send transaction”, KRNL Studio is that process turned into a visual system you can reuse, share, and evolve.

Stop stitching infrastructure together. Start building actual products.

### How the DSL Connects to the KRNL Node

KRNL Studio is not just a visual editor. Everything you build on the canvas is compiled into a DSL, a structured workflow definition that the KRNL Node understands and executes.

Here is the full loop:

#### 1. Visual Workflow → DSL

When you connect nodes in the Studio, the system generates a workflow definition in KRNL’s domain-specific language. It captures:

* The sequence of tasks
* What container or execution environment each one needs
* What inputs and outputs are passed between them

No visuals are stored. The KRNL Node only sees the DSL as a set of instructions to follow while your workflow is being executed.

#### 2. DSL → KRNL Node

That DSL is sent to a KRNL Node, which acts as a secure off-chain execution engine. Its job is not just to run the workflow but to **prove** that it ran correctly.

The node:

* Parses the DSL into an execution graph
* Spins up isolated environments for each task (gVisor sandboxes)
* Restricts outgoing network traffic and signs every call
* Generates cryptographic proof for each step

#### 3. Node → Blockchain

Once execution is complete, the node packages the result into a signed structure such as `AuthData` or a User Operation. That proof can then be sent to a smart contract or a bundler.

The smart contract does not need to trust the node. It verifies the proof and accepts or rejects the action based on it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.krnl.xyz/krnl-studio/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.