The Quiet Hour
A concept campaign for a sleep brand that does not exist, about the hour before bed that belongs to no one else.
When Kaitoi can't do something yet, ask Penny, its built-in AI. You get the missing piece as a working node, right inside your workflow.
Two examples play in turn. In the first, Penny is asked for a color grading node, writes and tests it, and adds a Color Grade node with lift, gamma and gain wheels; the sunset picks up the grade. In the second, Penny is told Nano Banana 2.1 has just been released, reads its documentation, writes a node for it, runs a test generation, and the new node generates an image of a banana.
Missing a tool or the newest model? Penny builds the node.
For illustration only. Not the actual Kaitoi interface.
Kaitoi Studio, the AI production workspace built on Kaitoi Core.
How it works
The whole job happens in one workspace. When it needs something Kaitoi doesn't have yet, Penny builds it on the spot.
From idea to rough cut
A brief, a client ask, or half an idea. Write it the way you would say it out loud.
briefPenny works with AdMuse, our own creative engine for advertising, to pitch original concepts, then develops the one you pick into a script, a look and a shot list.
conceptsscriptlookThe shots land on the storyboard and the timeline as a rough cut you can watch, reorder and refine.
storyboardtimelineThen make it yours
Need a look, a format, a model or a tool Kaitoi doesn't have? Penny builds it as a node, an agent, a plugin or a custom UI.
nodesagentspluginscustom UIsTurn the workflow into a simple app at its own link. People run it on their own credits, not yours.
stationown linkShowcase
A concept campaign for a sleep brand that does not exist, about the hour before bed that belongs to no one else.
An ad for a vintage sneaker brand that never existed, told through the man who keeps its archive.
A short film concept built as a movie trailer.
A one-minute travel story following two stuffed characters on their journey.
Memories brought to life from old still photos
The product family
Start in Studio. Build on Core when you want your own AI apps.
The browser workspace for creative production.
The platform and public API beneath Studio.
Works with
Use Kaitoi's keys and pay with credits. From the Indie plan up, bring your own keys; on Studio, run models on your own GPU.
Kaitoi's own keys, paid with credits. Nothing to set up.
From the Indie plan up, bring your own key. A few need none at all.
On the Studio plan, run models on your own GPU through the CLI.
Connect the accounts you already use, to read from them, write to them and publish.
If it has an API, Kaitoi can call it. Paste the docs link, add the key to your Variables or connect it with OAuth, and Penny writes the node that calls it.
The shift
Software has always shipped with its limits built in. Each product offers a fixed set of actions, and when your work needs something outside it, you improvise: workarounds, exports to other tools, or a wait for a feature that may never arrive.
Kaitoi moves that line. Describe the capability you need, and Penny builds it as a node, recipe, integration, or skill that runs inside the same system. The software adapts to the work, not the reverse.
The feature list is no longer the ceiling. What you can describe, generate, verify, and run is.
When Kaitoi can't do something yet, ask Penny, its built-in AI. You get the missing piece as a working node, right inside your workflow.
Two examples play in turn. In the first, Penny is asked for a color grading node, writes and tests it, and adds a Color Grade node with lift, gamma and gain wheels; the sunset picks up the grade. In the second, Penny is told Nano Banana 2.1 has just been released, reads its documentation, writes a node for it, runs a test generation, and the new node generates an image of a banana.
Missing a tool or the newest model? Penny builds the node.
For illustration only. Not the actual Kaitoi interface.
The whole job happens in one workspace. When it needs something Kaitoi doesn't have yet, Penny builds it on the spot.
From idea to rough cut
A brief, a client ask, or half an idea. Write it the way you would say it out loud.
briefPenny works with AdMuse, our own creative engine for advertising, to pitch original concepts, then develops the one you pick into a script, a look and a shot list.
conceptsscriptlookThe shots land on the storyboard and the timeline as a rough cut you can watch, reorder and refine.
storyboardtimelineThen make it yours
Need a look, a format, a model or a tool Kaitoi doesn't have? Penny builds it as a node, an agent, a plugin or a custom UI.
nodesagentspluginscustom UIsTurn the workflow into a simple app at its own link. People run it on their own credits, not yours.
stationown linkA concept campaign for a sleep brand that does not exist, about the hour before bed that belongs to no one else.
An ad for a vintage sneaker brand that never existed, told through the man who keeps its archive.
A short film concept built as a movie trailer.
A one-minute travel story following two stuffed characters on their journey.
Memories brought to life from old still photos
Start in Studio. Build on Core when you want your own AI apps.
The browser workspace for creative production.
The platform and public API beneath Studio.
Use Kaitoi's keys and pay with credits. From the Indie plan up, bring your own keys; on Studio, run models on your own GPU.
Kaitoi's own keys, paid with credits. Nothing to set up.
From the Indie plan up, bring your own key. A few need none at all.
On the Studio plan, run models on your own GPU through the CLI.
Connect the accounts you already use, to read from them, write to them and publish.
If it has an API, Kaitoi can call it. Paste the docs link, add the key to your Variables or connect it with OAuth, and Penny writes the node that calls it.
Software has always shipped with its limits built in. Each product offers a fixed set of actions, and when your work needs something outside it, you improvise: workarounds, exports to other tools, or a wait for a feature that may never arrive.
Kaitoi moves that line. Describe the capability you need, and Penny builds it as a node, recipe, integration, or skill that runs inside the same system. The software adapts to the work, not the reverse.
The feature list is no longer the ceiling. What you can describe, generate, verify, and run is.