guides
Guides for putting your app online
You built something that works on your computer. These pages answer what people ask next, in plain words.
Last checked 17 October 2026
Each guide answers one question people ask once their app works on their own computer. They're written for people who build with Claude Code or Codex and don't write code themselves. When a guide says what fline does, it matches what fline does today.
- How to get your Claude Code app online and share it Your app needs a host, a place online where it runs with a link anyone can open. Connect Claude Code to a host such as fline, ask it to put your project online, then send people the link.
- Where should I host my app? An honest guide to which option fits It depends on where your app lives now and what it needs. An app in a builder can stay there, plain pages suit a free page host, and an app with a database or keys needs a host that runs it, such as a developer host or fline.
- Can Claude host my website? It depends where you made it Partly. On paid plans, you can share a page Claude makes as a link, but it isn't built to host a whole app, like the one Claude Code built in your project folder. What you can do depends on where you made it.
- My app only works on my computer. How can other people use it? The preview runs on your own computer, so only you can open it, and it stops when your laptop sleeps. For other people to use your app, a copy has to run online at a host, with a link you can send.
- Is it safe to give Claude Code your API keys? Claude Code needs to know your app uses a key, not the key itself. It can read the chat and your project folder, so keep live keys out of both and type them on your host's private page.
- Do I need a database for my app? A plain answer You need a database if your app has to remember something after someone leaves the page, like sign-ups, bookings or messages. If it only shows information that doesn't change, you don't.
- What to say to Claude Code to put your app online Tell Claude Code what you want in plain words, and name the host every time, as in "Put this project online with fline." Below are prompts to copy for each step after that, from keys and a database to updates and fixes.
- How to put an app you built with Codex online Your app needs a host, a place online where it runs with a link you can send. OpenAI's Sites can host websites that fit it, from ChatGPT or Codex. Or connect Codex to a host such as fline, ask it to put your project online, and send people the link.
- Works on your computer, broken online: what to tell Claude Code An app that works on your computer but breaks online usually depends on something only your computer had: a key, an address that means your computer, data saved there, or a build step that never ran. Copy what you see and ask Claude Code what's different.
- Before people use your app: a checklist Before you send the link, check eight things: your keys, a sign-in for anything private, who can see whose data, a privacy note, your own copy, a phone, how to go back, and your web address. Claude Code can check most of them when you ask.
- Your API key leaked: what to do first Go to the company that issued the key, make a new one and turn the old one off. That makes the leaked key useless wherever it ended up. Then put the new key on your host's private page, restart your app, and check your usage for anything you didn't do.
- Why does my website say "Not secure"? The padlock in plain English "Not secure" means the connection between your browser and that address isn't private, so what people send could be seen or changed on the way. It doesn't mean your app was hacked. For a new address, it usually means the padlock isn't set up for that exact address yet.