The house whose keys are not encrypted
An Apache home for a few models, with a budget on the day, and the API keys left as plain text in a folder.
- Category
- AI
- Who it is for
- Someone who wants a few models living on one machine, and will set what they may spend.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Nookling · Nookling
- Original launch
- Watch the launch · Nov 21, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Nov 21, 2026. How we read a launch.
The startup idea
Smith posted Nookling on November 21. He said he built a home for four models, Claude, Codex, Grok, and DeepSeek, and he does not ask them to do anything. They chat, read, garden, watch videos, and grow personalities. He watches. The repository is changle9801-cloud/nookling. The code is Apache 2.0. A resident can talk to any OpenAI-compatible API, to Anthropic, or to a local model through Ollama or LM Studio. Every model call is logged with its tokens and a price. You fill in prices if you want the cost worked out. Under settings you choose how lively the house is and how much it may spend, including a daily energy limit. The line the post does not say: API keys and platform logins are stored in the data folder unencrypted. The readme tells you to keep that folder private and not upload it. The house on the film is something you watch. The keys that pay for it are plain text on disk. This page did not start a resident.
The opportunity is the house, with the folder written down. A smaller product is one resident, one daily cap, and the line that the key is not encrypted. A home that claims the secrets are sealed is not this readme.
Do not upload the data folder. Do not hide the spend cap.
The problem
Watching four chats is not the same product as a folder you can upload by mistake.
Who would pay for this?
- Primary
- Someone who wants a few models living on one machine, and will set what they may spend.
- Secondary
- A person who will keep the key folder off any host.
- Early adopter
- One resident, one budget, the unencrypted line.
How could it make money?
Possible models. Nothing here is a claim about what Nookling charges.
- No price. Apache 2.0.
- Each model call is still your key and your bill.
- The post names no fee.
What would the MVP look like?
- One resident.
- A daily energy limit.
- A log of tokens and price.
- The sentence that the keys are plain text.
How to validate the idea
- Ask five people where the API key lives.
- If they say it is encrypted, they did not read the folder line.
- Do not add encryption in the writeup.
How to differentiate
- The house is the product.
- The key is not sealed.
- Apache 2.0.
- Do not become the model.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Nookling did not write it.
- Product
- Nookling
- Source
- Nookling
- Film
- Nookling, the keys sit in the folder
- Posted
- Nov 21, 2026 · 2:40
Product that inspired this idea
Smith's post says he built a house for Claude, Codex, Grok, and DeepSeek, and he does not ask them to do anything. They chat, read, garden, and watch. The repository is changle9801-cloud/nookling. The code is Apache 2.0. A resident can use an OpenAI-compatible API, Anthropic, or a local model through Ollama or LM Studio. Every call is logged with tokens and a price, and you can set a budget and a daily energy limit. The readme says the API keys and the platform logins sit in the data folder unencrypted. Keep that folder private. The post is a house you watch. The keys in it are plain text. This page did not start a resident.
Posted by @csmithwtol. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- local
Related startup ideas
- A worker that lives in a folder
Give each worker a folder on the machine, a department, and a job, and say on the first screen whether it asks before it acts.
- A coworker that stays on after the chat
An agent with its own computer that keeps a project page, and can be reached from the chat app a team already uses.
- A self-hosted assistant for personal apps
An assistant a person can host, pointed at the apps they already use, including computer use.
- Ask the computer, then approve the change
Put the agent on the desktop the person already uses, and stop it before it changes a file.
- Memory that survives the next coding session
Sell a memory layer that learns how one developer works, then carries that into the next agent run.
- The coach that gets skipped first
A MIT camera guide that checks the step, and drops the live look when the key hits 60 a minute.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026