CodeHero · Your own software factory

What stays inside the factory

The knowledge stays.
Whoever comes next.

Your decisions, rules, changes and their reasons stay in the platform. The next person or AI starts from the work already recorded.

CodeHero asks, builds, checks, runs and maintains on your server. You decide the rules; you don’t write code.

You decide
CodeHeroBuilds · checks · maintainsThe knowledge stays inside
On your server

The knowledge stays in the box

People change.
The knowledge stays.

What you decided. What changed. Why. CodeHero keeps that record with your project, on your server.

A new person, a new AI company or a new AI model can pick up from there. Your software’s story stays with you, beyond one developer’s memory.

See what stays with you

Inside the box · illustrative record

Decision
Notify the customer when a repair is one day late.
Reason
They should not have to call to find out.
Later change
Ask the workshop manager to review the message first.
Next person
Reads the rule, the change and why it was made.

A change of people or AI

Continue the work.
Keep its history.

The next person does not have to reconstruct the project from a chat or someone’s memory. The platform holds the rules, the work, the checks and their reasons.

  1. New person or model
  2. Reads the project record
  3. Continues from there

A record you can inspect

The fix has a history, too.

In the recorded equipment-request build, the checker found two layout problems. The repair and the passing recheck stayed with the project.

Recorded product screen↗
Actual CodeHero project progress: all three tickets completed.
The completed build, verification and repair remain in the project record.
Read the recorded run

Your installation holds the record

Know where the work lives.

Project knowledge stays in the platform. If you choose a cloud AI service, the selected context is sent to that service. Hosting the platform yourself does not make those calls local.

How knowledge is stored and reused

Two things it does for you — automatically

It manages its own memory. Your secrets never reach the AI.

Long projects fail in two quiet ways: the AI drowns in its own history, or a password slips into a prompt. CodeHero handles both inside the factory, for every agent it runs.

Memory that manages itself

Like a person at a desk: when the agent has finished with a long report, it keeps a short note of what matters and puts the report away in a drawer. It works much longer without losing the thread — and nothing is lost: the report can be opened again.

  • Pictures it has already looked at are put away automatically (when CodeHero talks to the AI directly)
  • Works with every AI the factory uses — with most at once, with some from the next time they start

Secrets the AI never sees

Passwords and keys you store as secrets are used by your application, 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 first.

  • Kept out of the project’s git and ZIP backups by default
  • It protects the passwords and keys you store as secrets (eight characters or longer). It cannot see a password typed into a message or shown in a screenshot — so store every password as a secret

How these work underneath

For engineers and developers

See how the factory works.

Architecture, independent checks, repair limits, hosting and retained knowledge. The high-level analysis and the implementation detail live here.

Open the developer page

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