Publishing an app built with Claude or Codex means that it no longer runs on a laptop but permanently on a server, and that other people reach it at a fixed address. For this, it needs more than working code.
What do I do next if the app only runs on my laptop?
Someone at your company has built a tool with Claude Code or Codex, for example a check for Excel imports or time tracking for a small team. The app works, but it only runs on the laptop, and the data sits on that one device. What remains open are the questions about operation: where is it hosted, who can get in, and what happens to this solution if the person is on holiday or leaves the company? Answer them before real data is in the app. Doing so afterwards takes considerably more effort.
What does a company app need besides working code?
Address
The app needs a fixed address, for example time.musterfirma.de, and a certificate for the encrypted connection. Certificates expire and should therefore renew automatically, otherwise the browser will show a warning at some point.
Sign-in
An internal app must not be open to everyone who knows the address. The best option is sign-in with the existing company account, for example with Microsoft or Google. That way, no further password is created and you control access centrally.
Database
On a laptop, the data often sits in a simple file. When several people work at the same time, the app needs a proper database. It must exist independently of the app, so that no data is lost with a new version.
Backups
Decide how often backups run, how long they are kept and how much data you could afford to lose in the worst case. Restore a backup as a trial at least once, so that you know restoring works.
Credentials
In a prototype, passwords and API keys often sit in the code or in a file on the laptop, and everyone manages their own. In operation, they belong in a protected place, apart from the code. They should also run on a company account and not on one person's private account.
Test and live
Live is the version everyone works with. Test is a second version with its own data, in which you try out changes. Without this separation, every mistake hits the real data straight away, and with AI tools changes happen quickly and often in large steps.
Responsibility
Each app needs a responsible person and a deputy. They decide who gets access, take care of updates and are the contact when the app is not running.
Where can I host an app built with Claude Code?
There are five usual routes. They differ mainly in who does the work around the app.
- Your own rented server. You set up everything yourselves: updates, database, backups, sign-in and certificates. This means the most control and the most work. It fits if someone in-house enjoys doing this and has a deputy.
- Cloud platform for developers. The provider takes care of the server. You often set up company sign-in, access rights and an overview of all apps yourselves. This fits if your team has development experience.
- Handover to an IT service provider. The service provider runs the app for you. This fits for important applications, but changes then take longer.
- Rebuild in a no-code tool. This fits for simple forms and lists. You usually build the app again from scratch and work within the limits of the tool.
- Platform for apps you build yourselves. Sign-in, backups, test and live are prepared, and several apps run by the same rules. This fits if several people build and you would rather not build up operations yourselves. Check whether you can take your code and data with you again.
In what order should you go about it?
- Clarify the users. Will only your team use the app, the whole company, or people from outside too?
- Classify the data. Does the app contain data about people or trade secrets?
- Assign responsibility. Name a responsible person and a deputy.
- Choose where to host. Decide where the app will run. The options are the five routes from the previous section: your own server, a cloud platform, an IT service provider, a no-code tool or a platform for self-built apps.
- Tidy up the code. Put the code in a Git repository, which is a store with a version history. Remove credentials from the code. The AI tool can help you with this.
- Set up a test version. Have two or three people work with sample data.
- Check operation. Test the sign-in with an account that has no permission, and restore a backup.
- Go live. Start with a small group and expand it once the app runs stably.
The checklist from prototype to company tool helps you tick off the individual points.
When is it better not to publish an app?
- Only one person uses the app, and that will stay the case. It can then stay on the laptop, as long as no sensitive data is stored there.
- Nobody can be found to take responsibility for the app.
- An existing standard product does the job just as well.
What Auftrieb takes care of
Auftrieb is a platform on which companies publish and run their apps built with Claude or Codex. You connect the AI tool once and sign in with your company account. Apps you build yourselves are internal, and test and live normally have separate data. Auftrieb looks after servers, backups and certificates, and you maintain the code of your own app with your AI tool. The comparison shows how this differs from other routes.
Updated: November 2026