Every feature of Keou is on GitHub under MIT — the studio, the video engine, the export packs, the production prompt stack. Take it, run it, sell what you make with it. Nothing is withheld.
What we sell is the work: a version of Keou shaped around what you actually make — 3D models, music, audio, editing, VFX, whatever your pipeline needs and the public build doesn't do yet. Wired into the systems you already run, deployed under your own brand.
There's no price on this page because there's no product to price. Tell us what you need and we'll scope it together.
There is no feature behind a paywall, no watermark to remove, no seat limit to buy out. If the open-source build does what you need, use it and never pay us anything. That is the honest answer, and it is the whole point.
Generic software solves the generic 80%. The remaining 20% — your naming rules, your approval chain, your catalogue schema, the 3D or audio step nobody else needs — is where the hours actually go. That gap is the work, and it is what a custom build closes.
The code we write for you is yours, under the same MIT terms. No licence to renew, no vendor to be locked into, no kill switch. If you never speak to us again, it keeps running.
Every engagement is different, but they cluster into five shapes. Most projects combine two or three.
3D models, music, sound design, editing, VFX — the parts of a production pipeline the public build doesn't cover yet. If your work needs them, they get built into Keou properly, not bolted on the side as a script.
Keou reading from your PIM and writing back to your DAM. Assets landing straight in Shopify, WooCommerce or your own back office. An approval step that posts to the channel your team already watches, instead of a new inbox nobody checks.
Your servers, your domain, your brand throughout. For regulated work or client confidentiality: an install where images, prompts and client data never leave infrastructure you control. Air-gapped is possible.
Route generation to models running on your hardware (Ollama, vLLM, LM Studio), to OpenRouter, or to any private provider API — including endpoints that never leave your network. Wired once, for the whole team.
Prompt libraries tuned on your own catalogue, roles and quotas that match how you're organised, and a session with the people who will use it daily. Software nobody adopts is a cost, not a tool.
You get the source, the deployment runbook, and a walkthrough with whoever maintains it on your side. The aim is that you don't need us afterwards. If you want us on retainer anyway, that's a separate conversation.
You wouldn't, unless you want something the public build doesn't do. Plenty of people will clone the repo and never contact us — that's a good outcome, not a lost sale. Paying makes sense when the gap between what Keou does and what your workflow needs is worth more to you than the cost of closing it.
No, and this is worth being precise about. It used to be — polish, remix, export packs and the production prompt stack were held back as an upgrade funnel. That's over. The public repository now carries the complete studio, including the prompt stack that makes the output good. Two things stay private, and neither is a feature: our provider costs and margin table, and the Stripe plumbing that bills our own hosted instance.
Because a number here would be a guess, and a guess is worth nothing to either of us. A single integration against a documented API and a full 3D-plus-VFX pipeline are not the same job, and pretending they sit on one scale would only mislead you.
You get a written scope, a fixed price and a delivery date before anything starts — and that number doesn't move unless you change what you asked for. Write to kevyn@kanaky.xyz and we'll get there in one conversation.
You do, MIT, same as the rest. Where a piece is generally useful and not specific to your business, we may fold it back into the public repository — we'll say so during scoping, and you can decline.
No. MIT permits commercial use, modification and redistribution. Run it for clients, charge them, keep the money. Attribution is appreciated and not required.
Yes — that's the managed arrangement, priced separately on usage rather than a build fee. Say so in your first email and we'll scope both so you can compare.
Ask. If it's a short job we'll often just answer the question. The documentation covers the standard path and is meant to be enough on its own.
Tell us what your team does, and what Keou would have to do for it to earn a place in the workflow. If we can't help, we'll say so in the first reply.