Articles · Your data

Where does your data go when AI writes your software?

With CodeHero, the platform, your code, your databases, the project history and its knowledge stay on your own computer or server. What leaves is the part of the work an AI model needs for the current job — sent to the AI company you chose, or to nobody if you run local models. The values of the secrets you store never leave.

What stays on your machine

The CodeHero platform itself; the code of every application it builds; the applications’ databases and files; the specification, the plan, every ticket, decision and change with its reason; the project knowledge base and its search index; backups and snapshots. They live in your installation, on hardware you control.

What an AI service receives

An AI model works on text, so it receives what the agent shows it for the job at hand: the task, the files it reads, the output of the commands it runs, and the pictures it looks at. That is sent to the AI company you connected — Anthropic, OpenAI, Google, xAI, GLM, Qwen or OpenRouter — under that company’s own terms.

If that is too much for a project, connect local models (through Ollama or vLLM) and the work stays on your own hardware.

What never leaves: your secrets

Passwords and keys you store as secrets are used by your applications, but their values are never sent to the AI service: a command that would carry one is refused, and any output that contains one is replaced before the AI sees it. They are kept out of the project’s git and ZIP backups by default.

The honest limit: protection covers stored secrets of eight characters or more. A password typed into a chat message or visible in a screenshot cannot be recognised — so store every password as a secret.

What reaches us

From your installation, CodeHero sends Smartnav only its licence check: the licence key, an anonymous identifier of the machine and, when the licence is activated, the machine’s name. No project, code or data. This website itself uses no cookies — see privacy and cookies.

Practical rules

Store every password and key as a secret. Choose the AI companies a project may use; use local models for the most sensitive work. Keep backups on your own storage. And remember that the applications you build run on your machine, under your own security and access rules.

Questions people ask

All the articles

Am I tied to one AI company?

No. CodeHero works with many AI companies at once and with models on your own hardware. You can change company or model at any time — the project, its rules and its history stay. Read the article

Do my passwords and keys reach the AI company?

No. Passwords and keys you store as secrets are used by your application, but their values are never sent to the AI service. Read the article

Why do several AIs work on the same job?

Because one AI does not catch its own blind spots. In CodeHero one model builds and a model from a different company checks; problems go back for repair and are checked again. Read the article

How does CodeHero compare with other AI coding tools?

It is a different kind of thing. Coding tools help a person who writes code. CodeHero does the whole job — asks, plans, builds, checks, hosts and maintains — for the person who knows the business. Read the article

If CodeHero writes the code, what is my role?

You become the advisor: you decide the business rules, approve the plan and accept the result. CodeHero is the developer that asks, builds, checks and maintains. Read the article

How does the AI keep its memory on long jobs?

With memory folding: when the AI has finished with a long result it keeps a short note of what matters and puts the rest away — it can open it again at any time. So it works much longer without losing the thread. Read the article

How does the AI avoid forgetting or getting confused on a big project?

The factory gives it structure: smart tickets with one clear job each, a change ledger of every decision, a map of the code and search by meaning. The AI reads what it needs instead of guessing — which also saves a lot of cost. Read the article

Why do you call it a factory and not a tool?

Because it runs the whole production line on its own — planning, building, independent checking, repair, delivery and maintenance — with stations, rules and records, like a factory. A tool waits for a person to use it. Read the article

How can this change the world of applications?

When the person who knows the work can get software made, checked, hosted and maintained without a development team, software can be made for every business and every need — not only for those that can afford a team. Read the article

What does CodeHero mean for developers?

Less repetitive work and fewer late nights. The factory takes the routine building, checking and fixing; developers decide the architecture, review what matters and handle the hard problems. Read the article

Why does CodeHero host the applications too?

Because building and running belong together. The application runs where it was built, with its domain, secure connection, backups and recovery — and every later change returns to the same factory. No separate hosting panel to learn. Read the article

What technology do the applications use?

Always open, widely used technologies — PHP and MySQL first, and others such as Node, Python or .NET when the job needs them. Your application is never locked into a proprietary platform. Read the article

Why use AI subscriptions instead of paying per use?

Because in our own measurements, for heavy daily work, a subscription has cost up to about 40 times less than paying per use for the same work. CodeHero runs the subscription AI tools (Claude Code, Codex, Grok Build) as workers in the factory. Read the article

What happens to the knowledge about my project?

It is built up and kept inside your installation: decisions, rules, changes and their reasons, next to the code. A new person or a new AI continues from there — the knowledge does not leave with them. Read the article

Can small local AI models do real work?

Inside the factory, yes — more than on their own. Small, clear tickets, a checklist for finishing, tool help and a stronger model that checks the result let small models on your own hardware do much of the building. Read the article