surface
More ways to put your ideas to work.

Publish projects as Stations, bring your agents into Studio, and build software with the media it needs. Plus simpler plans and more affordable Penny models.

When we opened the beta, the promise was simple: describe what you need, build it in Kaitoi, and keep extending it as the job changes. A model, a piece of ordinary code, a custom interface, an entire workflow. If the tool is missing, you can make it.

Since then, we’ve been working on what happens next. How do you publish that project as a Station a client can use? Let your preferred agent work on the graph? Build an application, then make the media that application needs?

There are now more ways to put what you build to work.

Simpler plans

More on pay-as-you-go. Studio for individuals and teams.

The REST API, your own provider keys, local integrations, template and community publishing, and workflow API endpoints now join Stations, MCP, Code and Crew on pay-as-you-go. No subscription needed; paid runs use credits as usual.

Indie is closed to new subscriptions. Studio is now our single self-serve subscription, for individuals and teams, adding included credits, collaboration, priority support and direct code editing. Existing Indie subscriptions keep their current terms.

See what each plan includes

01 · Stations

Turn your project into a Station.

A Station turns a project into a small app at its own link. You choose which inputs people can change and which results they see. They get a straightforward interface on their phone or computer, without needing to understand the graph behind it.

Stations now support step-by-step runs. In an image-to-video Station, visitors can make several images, pick one, and use it in the video step. They can try different videos from that image and choose which take to carry into a later Station step. Valid results from earlier Station steps can be reused, so trying another video doesn’t have to mean generating the starting image again.

StationImage to videoIllustrated example
In a Station, choose a take from one step and use it in the next.

You can offer choices such as a poster, a story or a banner, with the run making only the selected branch. Add a company name and logo, arrange the form, and choose which inputs visitors can leave blank. Results appear as their part of the run finishes, and supported failed runs can resume using valid saved work.

Share it with a client or your team. Whoever runs it uses their own credits. Publishing creates a versioned snapshot, so you can keep editing the original project and choose when an update goes live. A Station carrying your own custom nodes is shared by invitation and requires Studio.

Want people to discover it? Submit an eligible public Station to the Station gallery with a short description and an image or video cover. Listings are reviewed before they appear.

Stations can also include approved community nodes. Their makers receive the node’s fee when it runs, giving a useful tool another way to reach the people who need it.

02 · Connected agents

Bring your agent into Studio.

Already work with Claude Code, Codex, ChatGPT or another MCP client? Connect it to Kaitoi and give it the Studio tab you want it to work in. Your agent can handle the work through MCP without using Penny or paying for a Penny conversation. Paid Kaitoi runs still use credits.

Your agent can add, connect and run nodes, create and update custom scripts and reusable web tools, work with Blocks, and edit timelines and storyboards. The work appears in Studio as it happens.

You keep the controls. Turn agent access on for each tab, follow the activity, stop work when you need to, and use Studio’s normal Undo and Redo for supported edits. Paid runs use cost approval; connecting an agent doesn’t give it an open spending tab.

Your connected agent can also use AdMuse directly for advertising research and creative development.

For developers, the agent can find templates, inspect their inputs and outputs, and prepare API requests for the application you’re building.

Connect your agent to Kaitoi

03 · Kaitoi Code + Crew

Build the application. Make what goes inside it.

Kaitoi Code is a coding agent with Kaitoi’s creative tools within reach. While it writes the application, it can make the images, video, voiceovers, music, sound effects and 3D models the application needs, and save them into the project.

Use it in the terminal, in the VS Code extension, or in an editor that supports the Agent Client Protocol, including Zed and JetBrains IDEs. GitHub integration brings it to comments, pull-request reviews and fixes too.

It can delegate work to subagents, run dev servers in the background, and use MCP servers for other tools. You can inspect edits before approving them, rewind an exchange, and see the session’s cost as it works.

Use the agents and models that suit the job. Subagents can run through your installed Claude Code or Codex; their model usage goes through your existing subscription. Paid work they request through Kaitoi still uses Kaitoi credits. Or run Code on a suitable local model through Ollama, LM Studio or another compatible server, without a Kaitoi account or a Kaitoi charge for the local model’s work.

For larger jobs, Crew coordinates the build and runs independent test, build and smoke commands to check the result. Interrupted builds keep their work and can continue, and Crew now runs on Windows as well as macOS and Linux.

The CLI suite is now Apache-2.0 licensed: Kaitoi CLI, Code, Crew, Connect and Runtime. You can inspect and extend the tools you use to build.

Install Kaitoi CLI · Get started with Kaitoi Code

04 · The everyday work

A smoother Studio. More of your work kept within reach.

We’ve put substantial work into large graphs: panning, zooming, typing into nodes and working through a long editing session. Timeline projects with many clips open and play more smoothly too. The interface has a calmer, more consistent look across views.

Project saving has better conflict protection. An old tab cannot silently save over newer work, and recovery copies help you retrieve edits after a conflict or a restore. Newer autosaved work is preserved when you open an older saved version.

Penny keeps more of the conversation after large tool steps, edits selected custom nodes in place, and has better guidance for building working video, audio and web tools. Its recommendations use the current catalog and our team’s ranked picks and notes. Penny’s model picker lets you choose significantly cheaper models that can deliver very similar results for many everyday tasks.

Playbooks keep your direction ready. Save a brand voice, a creative method or a review checklist as a document, then activate it for a conversation in Lab or Graph Penny. You can import Markdown, paste text or write it in Kaitoi, instead of repeating the same instructions in every chat.

Also worth opening

Shared files, template API endpoints, and work ready to review.

  • Team Files: browse shared team assets alongside your personal Files, and move or copy files between them.
  • Template API endpoints: your application can request selected outputs and reuse eligible results from an earlier run of the same endpoint. Request an image first, then use that result in subsequent video requests.
  • Production and delivery: export storyboards as readable shot lists and image sequences in a PDF, export a timeline’s soundtrack on its own, and send finished renders back to the graph.
  • Easier handoffs: share a template link, send node results to Files or the Lab, and find expanded guides in the public documentation.

Explore the documentation

An expandable workspace

The nodes we add are a head start.

We’ve added more ready-made nodes, from model integrations to shot detection, subtitle rendering and social-video overlays. They are useful shortcuts when you want to get straight to work.

But you never have to wait for our catalog to catch up with your idea. When a new model comes out, you can add it yourself or ask Penny to build the integration. The same goes for ordinary code, a custom interface, an automation or a tool specific to your job.

Build the missing piece. Keep it in your library. Connect it to everything else. Then use a Station, your agent, Code or the API to put it where the work happens.

Available now

Pick something you’d like to put to work.

A Station to hand to a client. An agent to connect. An application that needs its own media. Open Kaitoi and give it a job.

Open KaitoiExplore Stations

Bugs, ideas and things you wish existed: support@kaitoi.io. A human reads it.

All posts
kaitoi BL-2 October 26, 2026 · 7 min read Product update

01 doc Product update all posts

More ways to put your ideas to work.

Publish projects as Stations, bring your agents into Studio, and build software with the media it needs. Plus simpler plans and more affordable Penny models.

by Jacobo

02 txt the post

When we opened the beta, the promise was simple: describe what you need, build it in Kaitoi, and keep extending it as the job changes. A model, a piece of ordinary code, a custom interface, an entire workflow. If the tool is missing, you can make it.

Since then, we’ve been working on what happens next. How do you publish that project as a Station a client can use? Let your preferred agent work on the graph? Build an application, then make the media that application needs?

There are now more ways to put what you build to work.

Simpler plans

More on pay-as-you-go. Studio for individuals and teams.

The REST API, your own provider keys, local integrations, template and community publishing, and workflow API endpoints now join Stations, MCP, Code and Crew on pay-as-you-go. No subscription needed; paid runs use credits as usual.

Indie is closed to new subscriptions. Studio is now our single self-serve subscription, for individuals and teams, adding included credits, collaboration, priority support and direct code editing. Existing Indie subscriptions keep their current terms.

See what each plan includes

01 · Stations

Turn your project into a Station.

A Station turns a project into a small app at its own link. You choose which inputs people can change and which results they see. They get a straightforward interface on their phone or computer, without needing to understand the graph behind it.

Stations now support step-by-step runs. In an image-to-video Station, visitors can make several images, pick one, and use it in the video step. They can try different videos from that image and choose which take to carry into a later Station step. Valid results from earlier Station steps can be reused, so trying another video doesn’t have to mean generating the starting image again.

StationImage to videoIllustrated example
In a Station, choose a take from one step and use it in the next.

You can offer choices such as a poster, a story or a banner, with the run making only the selected branch. Add a company name and logo, arrange the form, and choose which inputs visitors can leave blank. Results appear as their part of the run finishes, and supported failed runs can resume using valid saved work.

Share it with a client or your team. Whoever runs it uses their own credits. Publishing creates a versioned snapshot, so you can keep editing the original project and choose when an update goes live. A Station carrying your own custom nodes is shared by invitation and requires Studio.

Want people to discover it? Submit an eligible public Station to the Station gallery with a short description and an image or video cover. Listings are reviewed before they appear.

Stations can also include approved community nodes. Their makers receive the node’s fee when it runs, giving a useful tool another way to reach the people who need it.

02 · Connected agents

Bring your agent into Studio.

Already work with Claude Code, Codex, ChatGPT or another MCP client? Connect it to Kaitoi and give it the Studio tab you want it to work in. Your agent can handle the work through MCP without using Penny or paying for a Penny conversation. Paid Kaitoi runs still use credits.

Your agent can add, connect and run nodes, create and update custom scripts and reusable web tools, work with Blocks, and edit timelines and storyboards. The work appears in Studio as it happens.

You keep the controls. Turn agent access on for each tab, follow the activity, stop work when you need to, and use Studio’s normal Undo and Redo for supported edits. Paid runs use cost approval; connecting an agent doesn’t give it an open spending tab.

Your connected agent can also use AdMuse directly for advertising research and creative development.

For developers, the agent can find templates, inspect their inputs and outputs, and prepare API requests for the application you’re building.

Connect your agent to Kaitoi

03 · Kaitoi Code + Crew

Build the application. Make what goes inside it.

Kaitoi Code is a coding agent with Kaitoi’s creative tools within reach. While it writes the application, it can make the images, video, voiceovers, music, sound effects and 3D models the application needs, and save them into the project.

Use it in the terminal, in the VS Code extension, or in an editor that supports the Agent Client Protocol, including Zed and JetBrains IDEs. GitHub integration brings it to comments, pull-request reviews and fixes too.

It can delegate work to subagents, run dev servers in the background, and use MCP servers for other tools. You can inspect edits before approving them, rewind an exchange, and see the session’s cost as it works.

Use the agents and models that suit the job. Subagents can run through your installed Claude Code or Codex; their model usage goes through your existing subscription. Paid work they request through Kaitoi still uses Kaitoi credits. Or run Code on a suitable local model through Ollama, LM Studio or another compatible server, without a Kaitoi account or a Kaitoi charge for the local model’s work.

For larger jobs, Crew coordinates the build and runs independent test, build and smoke commands to check the result. Interrupted builds keep their work and can continue, and Crew now runs on Windows as well as macOS and Linux.

The CLI suite is now Apache-2.0 licensed: Kaitoi CLI, Code, Crew, Connect and Runtime. You can inspect and extend the tools you use to build.

Install Kaitoi CLI · Get started with Kaitoi Code

04 · The everyday work

A smoother Studio. More of your work kept within reach.

We’ve put substantial work into large graphs: panning, zooming, typing into nodes and working through a long editing session. Timeline projects with many clips open and play more smoothly too. The interface has a calmer, more consistent look across views.

Project saving has better conflict protection. An old tab cannot silently save over newer work, and recovery copies help you retrieve edits after a conflict or a restore. Newer autosaved work is preserved when you open an older saved version.

Penny keeps more of the conversation after large tool steps, edits selected custom nodes in place, and has better guidance for building working video, audio and web tools. Its recommendations use the current catalog and our team’s ranked picks and notes. Penny’s model picker lets you choose significantly cheaper models that can deliver very similar results for many everyday tasks.

Playbooks keep your direction ready. Save a brand voice, a creative method or a review checklist as a document, then activate it for a conversation in Lab or Graph Penny. You can import Markdown, paste text or write it in Kaitoi, instead of repeating the same instructions in every chat.

Also worth opening

Shared files, template API endpoints, and work ready to review.

  • Team Files: browse shared team assets alongside your personal Files, and move or copy files between them.
  • Template API endpoints: your application can request selected outputs and reuse eligible results from an earlier run of the same endpoint. Request an image first, then use that result in subsequent video requests.
  • Production and delivery: export storyboards as readable shot lists and image sequences in a PDF, export a timeline’s soundtrack on its own, and send finished renders back to the graph.
  • Easier handoffs: share a template link, send node results to Files or the Lab, and find expanded guides in the public documentation.

Explore the documentation

An expandable workspace

The nodes we add are a head start.

We’ve added more ready-made nodes, from model integrations to shot detection, subtitle rendering and social-video overlays. They are useful shortcuts when you want to get straight to work.

But you never have to wait for our catalog to catch up with your idea. When a new model comes out, you can add it yourself or ask Penny to build the integration. The same goes for ordinary code, a custom interface, an automation or a tool specific to your job.

Build the missing piece. Keep it in your library. Connect it to everything else. Then use a Station, your agent, Code or the API to put it where the work happens.

Available now

Pick something you’d like to put to work.

A Station to hand to a client. An agent to connect. An application that needs its own media. Open Kaitoi and give it a job.

Open KaitoiExplore Stations

Bugs, ideas and things you wish existed: support@kaitoi.io. A human reads it.

StationsMCPKaitoi CodeStudio