Frequently asked
Kaitoi is a self-extending AI platform for creators and developers. It gives teams a browser-based workspace, a programmable platform/API, and Penny, an assistant that can help create missing capabilities directly inside the workflow.
Most software ships with a fixed feature list. Kaitoi is built around composable nodes and recipes, so when a capability is missing, Penny can generate a new node, connect an API, create a local recipe, or write custom Python that runs inside the same workflow system.
Kaitoi is built for studios, agencies, production teams, technical artists, creative technologists, researchers, educators, and developers building AI-native workflows. It is designed for teams that need creative flexibility, deterministic execution, and the ability to integrate custom tools.
You can request access, join the community, or work with us through the Design Partner program if your team is exploring AI production workflows in a real studio or agency setting.
Kaitoi Studio is the web workspace for building and running hybrid AI workflows. Kaitoi Core is the platform and API underneath: graph execution, sandboxing, media, integrations, access control, and billing. Kaitoi CLI is the terminal surface for local operations, runtime recipes, graph execution, and Agent mode.
Kaitoi supports workflows across images, video, audio, text, 3D, documents, web apps, vector graphics, structured data, simulation, research, and custom Python logic. A workflow can combine generative models with deterministic steps, APIs, local tools, and team-specific automation.
No. Kaitoi supports exploration, moodboarding, story development, graph-based prototyping, storyboard work, and repeatable production pipelines. The same project can move from early exploration into a structured workflow as it matures.
Not necessarily. Kaitoi is designed to connect models, APIs, local systems, and production tools into one workflow layer. It can generate assets directly, but it can also sit alongside existing editors, render tools, local models, and internal studio infrastructure.
Kaitoi is model- and provider-agnostic. It can route across hosted providers, custom APIs, local inference, and recipes built from model repositories. The goal is not to lock you into one model vendor, but to make models usable inside repeatable workflows.
Yes. You can write custom Python nodes, create runtime recipes, expose workflows as API endpoints, connect internal services, and use Penny to help generate missing capabilities. Extensions run as contained units with defined contracts rather than becoming one fragile monolithic codebase.
Kaitoi Studio runs in the browser. Workflows can use hosted services, Kaitoi-managed execution, local infrastructure, or your own API keys depending on how your team configures the project. A new open source version of Kaitoi that can run locally on your own machine is coming soon.
Kaitoi combines AI with deterministic code. That means a workflow can include generative steps, exact calculations, simulations, file operations, APIs, validation, and custom logic in one graph. Studio can be used for creative production, but the pattern is broader: if a domain needs a mix of AI, exact logic, files, APIs, and repeatable execution, Kaitoi can help turn that into working software.
Studios retain ownership of their content. Kaitoi isolates customer data by account and workspace, supports deletion, and does not train models on customer assets. Teams can also use their own keys or infrastructure for workflows that require stricter control.
Teams provide shared projects, shared apps, shared billing, member roles, and spending controls. Studio team subscriptions are tied to a specific team so an owner can manage seats, credits, budgets, and permissions for that workspace.
Yes, when a team has the right plan and the member has a role that can run work. Owners can manage team funds and member caps so the team can collaborate without every member needing a separate personal subscription.
Yes. Personal and team balances can use pay-as-you-go credits, while subscription plans provide included credits and plan features. Studio is the team-oriented plan for shared workspaces and seats.