Put your app online

This page walks you through your first launch with fline, from a project that works on your computer to a link you can send. It covers the few steps that need you, the sentence to type, what you see while fline gets your app ready, and what to say to Claude Code afterwards.

Before you start: is this you?

This path fits if:

• you built your app with Claude Code;
• your project is a folder on your computer, and the app runs there;
• your fline account is open. If it isn't yet, see Getting your account.

If you made your app in ChatGPT, on the Claude website, or in an app builder like Lovable or Bolt, fline can't take it yet. Other AI apps explains why.

If you use the Code tab in the Claude desktop app: we haven't tested it with fline yet. The path we've tested is Claude Code in your computer's Terminal app.

1. Connect Claude Code to fline

Your fline dashboard shows one line to copy. Open your computer's Terminal app, go to your project folder, paste the line, and approve fline in your browser. For now, you do this once for each project folder. It's copy and paste, and none of it is coding.

Connect Claude Code has every step, including how to open Terminal. Using Cursor, Codex or VS Code? Use the setup steps for Cursor, Codex or VS Code instead. They aren't yet tested from start to finish.

2. Ask Claude Code

In your project folder, start Claude Code and tell it:

Put this project online with fline.

Name fline in the sentence. Left to choose, Claude Code may pick a different host.

3. Let Claude Code send your project

Claude Code packs up a copy of your project folder and sends it to fline. Before it does, it may ask your permission to run a few commands, and to use fline's actions. That's the upload, and it's expected. Allow it.

Your original stays in your folder. fline keeps a copy so it can build and run your app.

fline then reads the copy and works out how to build and run your app, so there are no setup files to write. To do that, fline sends parts of your code to an AI model made by OpenAI. Passwords and keys you save on fline never go to that model.

A few limits to know: your project can be up to 100 MB once Claude Code packs it up, not counting the add-ons your app downloads when it's built.

4. Type passwords and keys on the private page

If your app uses a password or key, like a payment key or an email service key, Claude Code gives you a link to a private fline page.

1. Open the link in your browser. If you're not signed in to fline there, sign in first.
2. Type each value in its box and save.
3. Go back to Claude Code and tell it you're done.

You type the key there, not in the chat. Claude Code sees that you did it, not what you typed. The page works once, for 10 minutes, and only while you're signed in to your own fline account. If it has stopped working, ask Claude Code for a new link. Once saved, nothing in fline shows the key again, not to Claude Code and not on your dashboard.

If you paste a key into the chat instead, Claude Code sees it. It can save it on fline itself, and it should suggest you replace it with a new key on fline's private page. To keep a key away from Claude Code, type it only on fline's page.

Passwords and keys your app uses has more, including where to find the keys services give you.

5. If your app needs a database

If your app needs to remember things, like sign-ups or bookings, Claude Code can have fline create a database of your own. fline runs it. Claude Code takes care of connecting it to your app. If it needs you, it asks you to copy one line from your fline dashboard and tells you where it goes.

A database of your own explains the rest.

6. Watch it get ready

Open your fline dashboard. Your project appears there, with a short line that says what fline is doing, such as reading your code or building. If something needs you, like keys, the dashboard says so.

Claude Code keeps checking too, and tells you when it's done. fline also emails you when it starts getting your app ready and when your app is live.

If Claude Code stops before the end, tell it:

Keep going until my project is live on fline.

7. Open the link

When your app is ready, your dashboard shows your app's link. If you have the dashboard open while it gets ready, it says "It's live." Claude Code gives you the link too.

The link starts out long, because it's made automatically. It ends in apps.dev.fline.sh. Open it on your phone to check it works away from your computer.

For a short address, put your app at a web address you own, like www.yourbakery.com. See Use a web address you own.

8. Before you send the link

• The link is public. Anyone who has it can open your app. If your app holds private information, like customers' names or orders, give it a sign-in, and ask Claude Code to check that each person sees only their own data. fline doesn't check your app's own code.
• There's no uptime promise yet. During the private beta every app runs on one rented machine, with no spare. It suits trying your app with your first users.
• Keep a copy of anything you can't lose. We don't promise backups yet, and there's no button to download your database.
• Size. Each project gets 1 processor core, about 1 GB of memory and 8 GB of storage. Nothing runs on a schedule, and a project can't be paused yet.
• Cost. fline is free during the private beta, with no card. Claude Code's own plan is separate: when it puts your app online or fixes something, that uses your plan as usual.

Then send the link to your first users.

If something goes wrong

If a launch fails, your dashboard says so, and a button copies the problem for Claude Code. Paste it in and ask for help. Claude Code can see what went wrong and try a fix. Whether it finds the fix depends on Claude Code, so we can't promise it will.

When something goes wrong covers what you might see.

Things to say to Claude Code

Put this project online with fline.

My app needs a key for [SERVICE]. Give me fline's private page instead of asking me to paste it here.

Check that each person who signs in can see only their own data.

The last update on fline failed. What went wrong? Try a fix, or put the earlier version back.

Save fline's build plan in this project, so later updates follow the same plan.

Attach www.[YOURNAME].com to this project on fline and tell me which record to add.

To change your app later, ask Claude Code to update it on fline. The current version keeps running while the new one is prepared. See Change your app after it is online.

Next: Change your app after it is online or Passwords and keys your app uses