surface
kaitoi VS-1 compare
01 cmp comparison
All comparisons

Kaitoi and Figma Weave compared

For designers who like Figma Weave, formerly Weavy, for its node canvas and compositing, but want an agent that builds the workflow with them, steps written in code, or their own machines in the graph.

Figma Weave, called Weavy until Figma acquired it in October 2025, is a hosted node canvas. It combines image, video, audio and 3D models from many providers with editing tools such as compositing, masking and color correction, and a workflow can become a tool that others run without seeing the nodes.

Kaitoi is also a hosted canvas of nodes from many providers, built around an agent. Penny builds the graph from a conversation and writes the nodes that are missing in Python, and your own computer or a GPU machine elsewhere can join the graph through Kaitoi CLI.

Checked against each product's own documentation on .

02 str strengths

What Figma Weave does well

Many providers on one balance. Image, video, audio and 3D models from Google, OpenAI, Kling, Runway, Luma, Black Forest Labs and others run on Weave credits, and the same prompt can go through several models side by side.

Editing next to generation. The Compositor layers images, video, text and shapes and has its own timeline, and masking, color correction and levels sit beside AI edits such as inpainting and relighting.

Connected to Figma. Weave tools for image tasks run inside Figma Design on paid Figma plans, the Figma node keeps a frame linked to a workflow, and tools can be published to the Figma Community.

Workflows others can run. A workflow becomes a tool with a simple interface, shared by invite, with a workspace or by link, and lists and iterators turn one click into many variations.

Clear terms on training. Weave does not use your images or prompts to train its platform, and it publishes which models have contracts that stop providers from training on your content.

Bring your own models. Paid plans import models from fal, Replicate and CivitAI by pasting a link, and LoRA files can be uploaded and used with LoRA-capable models.

03 apr approach

How Kaitoi approaches it

Many providers on one balance. More than 1,400 generative models and around 400 language models run on Kaitoi credits at the provider's own price with no markup, or, for providers that accept them, on your own keys, with models from Google, OpenAI, Kling, Runway, Luma and Black Forest Labs among them. One output can feed several model nodes to compare them side by side.

Editing next to generation, as nodes. Inpaint, outpaint, erase, background removal, layer splitting and upscaling run beside overlay, blend and mask nodes and a drawing canvas for masks, color nodes handle levels, color wheels, LUTs and white balance, and a MiniMax model relights video. Video edit, extend, motion-control, swap, reframe and upscale models run as nodes, and clips are cut on a multi-track timeline. There is no layer-based compositor and no image relighting node.

Connected through MCP rather than Figma. Kaitoi's MCP server, on every plan, lets compatible AI clients build graphs, run approved work and inspect results, and on Studio write nodes. Penny calls outside MCP servers, and nodes and templates publish to Kaitoi's Community. There is no plugin inside Figma or other design apps.

Workflows others can run. A workflow becomes a Station at a stable link, a simple form or a custom app where each visitor runs on their own account, a template that starts new projects, or an API endpoint. Share links are read-only with optional cloning. An array input collects several results into one step; there is no iterator that runs a workflow once per item.

Clear terms on training. Kaitoi never trains models on your work, on any plan. When a node calls a provider, that provider handles the data under its own terms.

Bring your own models. LoRA nodes for FLUX.2, Qwen Image and others take your own weights, and a FLUX.2 trainer node trains them from your images. Penny turns a model without a node into one from the New Models panel, and Kaitoi Code turns a Hugging Face model or GitHub repository into a Runtime recipe on your machine.

Beyond that, the agent is part of the canvas. Penny builds and edits graphs from a conversation, writes a new node in Python when a step is missing, and edits storyboards and timelines.

Every node is code you can open. Nodes are Python with a declared interface, and a node can carry its own HTML, CSS and JavaScript interface, WebAssembly included.

The graph is not limited to the cloud. Kaitoi CLI connects your own computer or a GPU machine elsewhere, so ComfyUI, Ollama, Blender and Runtime recipes run as nodes, and Kaitoi Code writes a recipe from a Hugging Face model or a GitHub repository.

04 tbl side by side

Figma Weave and Kaitoi, side by side

Checked November 13, 2026.
QuestionFigma WeaveKaitoi
Models Which generative models you can reach.Image, video, audio and 3D models from many providers on one credit balance, with model import from fal, Replicate and CivitAI on paid plans. Video models need a paid plan.More than 1,400 generative models and around 400 language models from several providers as of September 2026, on credits or your own keys. When a provider releases a model that has no node yet, Penny can make one from the New Models panel. The catalogue is the same on every plan, with no subscription.
Agent An assistant that builds and runs the work with you.We found no built-in creative agent. On paid plans, outside agents can run published tools and models through Figma's MCP server after confirming the cost; creating or editing workflows that way is not yet supported.Penny builds and runs graphs, writes nodes, and edits storyboards, timelines and Lab boards, listing the tools it used in each reply. Kaitoi's MCP server, on every plan, lets compatible AI clients build graphs, run approved work and inspect results, and on Studio write nodes.
Editing and compositing Changing and combining images by hand and with models.The Compositor layers images, video, text and shapes, with blend modes, AI inpaint and split-to-layers, and a timeline. Editing nodes cover masking, color correction, levels and relighting.Inpaint, outpaint, erase, background removal, layer splitting and upscaling run as nodes, with overlay, blend and mask nodes, a drawing canvas for masks, and color nodes for levels, color wheels, LUTs and white balance. A MiniMax model relights video, and video is cut on a multi-track timeline. There is no layer-based compositor and no image relighting node.
Your own steps and code Adding a step the product does not ship.Model and LoRA import extend the catalogue. We found no way to write custom code nodes or plugins.LoRA nodes take your own weights, and Penny turns a model without a node into one. Every node is Python with a declared interface and packages from an approved list, and can carry its own HTML, CSS, JavaScript and WebAssembly interface. Penny writes nodes on every plan, editing code by hand needs Studio or Enterprise, and nodes can be published to Community.
Video and handoff Making and cutting video, and moving it to an editor.Video generation, editing with models such as Runway Aleph 2.0, trimming and upscaling, assembled on the Compositor's timeline. We found no EDL, XML or OTIO export.Video edit, extend, motion-control, swap, reframe and upscale models run as nodes, from Kling, Luma, Veo, LTX and Topaz among others; Aleph is not offered. A storyboard feeds a multi-track timeline that renders MP4, WebM or MOV in ProRes and exports and imports OpenTimelineIO for Premiere Pro, DaVinci Resolve or another editor.
3D and splats Generating and handling 3D models and scenes.3D models from Rodin, Meshy and Tripo, and explorable Gaussian splat scenes from World Labs that import and export as .ply files.3D generation through Tripo, Meshy, Hunyuan3D and World Labs, a Gaussian splat viewer and a 3D Editor node with render passes, and rendering in your own Blender.
Design apps Working from inside other creative tools.Weave tools run inside Figma Design for image tasks on paid Figma plans, and the Figma node keeps a frame linked to a workflow and pushes changes back to the file.Kaitoi's MCP server, on every plan, lets compatible AI clients build graphs, run approved work and inspect results, and on Studio write nodes. Kaitoi CLI connects a Blender you run, and nodes and templates publish to Kaitoi's Community. There is no plugin inside Figma or other design apps.
Apps for other people Letting someone run your workflow, and who pays.Tools shared by invite, with a workspace or by link, or published to the Figma Community. On Enterprise, the REST API runs published tools, and the account pays for every run, including by outside users.Stations at a stable link: a simple form, or a custom app built from a node's own interface. Visitors run on their own Kaitoi account and pay their own costs. A saved template becomes an API endpoint that runs on your own credits. Nodes and templates publish to Kaitoi's Community.
Teamwork Working on the same project with other people.A Team plan with shared workspace files and credit allocations per user. Workflows are shared read-only and duplicated to edit; we found no live co-editing or comments.Team workspaces with roles, shared projects and pooled credits on a team Studio subscription, with weekly caps per member, and share links are read-only with optional cloning. Edits do not sync live: when a teammate saves, Studio offers to load the newer version. There are no comments on the canvas.
Your own hardware Running models on a machine you control.Generations run on hosted third-party models. We found no self-hosted or local option.Hosted, and your own computer or a GPU machine elsewhere can join through Kaitoi CLI: ComfyUI, Ollama, Blender, and Runtime recipes that Kaitoi Code writes from a Hugging Face model or GitHub repository.

Each cell comes from the product's own website, documentation or code repository. "Not publicly documented" means we found no official page that says so, not that the feature is missing. Plans and features change; check the official pages before you decide.

05 fit which to choose

Which one fits

Choose Figma Weave if
  • You design in Figma and want generation tools inside Figma Design.
  • You want a layer-based compositor with blend modes and its own timeline next to generation.
  • You want to import a model from Replicate or CivitAI by pasting its link.
  • You want a published, per-model list of contracts that keep providers from training on your content.
Choose Kaitoi if
  • You want an agent that builds the workflow with you and writes the steps that are missing.
  • You want any step written in Python, with its own interface when it needs one.
  • You want your own machines in the graph: a GPU box, ComfyUI, Ollama, Blender, or a model from a GitHub repository.
  • You want a timeline that hands the cut to an editor through OpenTimelineIO.
  • You want to pay as you go with no subscription, at the provider's own price.
06 dem example

A real example: one image becomes a 3D space

Kaitoi Studio film

Kaitoi Signals #3 - Splats, 3D and Physics

A single image becomes an interactive space: Kaitoi separates environment and objects, rebuilds the scene as a navigable Gaussian splat, converts assets to 3D, adds physics and audio, and uses a viewer node generated by Penny for the workflow.

This film, from our Kaitoi Signals series, builds an explorable scene from a single picture, with a viewer Penny wrote for the job.

  1. Kaitoi separates the environment from the objects in one image.
  2. It rebuilds the scene as a navigable Gaussian splat and converts the objects to 3D.
  3. Physics and audio are added to the scene.
  4. A viewer node that Penny generated for this workflow shows the result.

Read more in the documentation:

07 prc pricing

Pricing and access

Figma Weave

Credit plans billed monthly or yearly: Free with 150 credits a month, then Starter, Professional, Max, a per-user Team plan, and Enterprise. Unused credits roll over on Professional, Team and Max, and the API and your own keys are on Enterprise.

Kaitoi

Free to start, with no subscription. Credits pay for hosted models, including Penny's, at the provider's own price with no markup, and for paid Community nodes; steps that call neither cost nothing. Your own provider keys work on every plan and are billed by your provider. Studio adds included credits, team seats and hand-edited code.

08 faq questions

Questions people ask

Is Figma Weave the same product as Weavy?

Yes. Figma announced in October 2025 that it had acquired Weavy, which now operates as Figma Weave, and weavy.ai redirects to weave.figma.com.

Does Kaitoi have a compositor like Weave?

Not a layer-based one. Image edits run as nodes, such as inpaint, layer splitting, overlay and blend, and video is cut on a multi-track timeline.

Can an agent build workflows in Kaitoi?

Yes. Penny builds and edits graphs from a conversation. On every plan, outside agents can build graphs and run work through Kaitoi's MCP server, and on Studio they can also write nodes.

09 mor more comparisons

Other comparisons