CodeHero CodeHero · Your own software factory
User guide · backup and restore
Backups and restore.
The factory hosts and maintains your software. This guide explains how to save the project and restore it when needed.
CodeHero asks, builds, checks, runs and maintains on your server. You decide the rules; you don’t write code.
01
Preserve the state
The three ZIP levels add to each other. Read warnings and exclusions before relying on the archive.
Backup levels
Read the diagram as text
- Quick|files + databases.
- Full|+ services.
- Complete|+ work history.
Choose a level in Backup & Restore.
- Quick: project files, the project database and the container’s databases.
- Full: Quick plus service configuration and port forwards.
- Complete: Full plus tickets, conversations and the knowledge graph.
Inspect what the backup could not save.
Unreadable files, failed database dumps and a stopped container appear as warnings in the result, the backup list and the manifest. A backup enters the list only when its archive is complete.
Review the exclusions.
Manual ZIP levels use the project’s editable exclusion list. Secrets and dependency, build and cache directories are excluded by default. Export and automatic backups apply only the secrets exclusion from that list.
02
Protect the present
before restoring the past.
An in-place restore takes a safety copy first. If that fails, the restore does not proceed.
The restore sequence
Read the diagram as text
- Safety copy.
- Restore.
- Inspect the app.
Select the required state.
Inspect the backup time, level, warning manifest and exclusions. Confirm which data will be replaced.
Let the safety copy complete.
Container projects take a Safety snapshot and a complete ZIP before an in-place restore. Image import takes the ZIP first because snapshots are replaced with the image.
Check the restored application.
Verify the services, data and the workflow your operating procedure names. Record the result and any remaining issues.
How the factory does this · for developers
Continue in the full guide · EnglishQuestions people ask
All the articlesAm 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