Make it real.
You and your AI built something. Right now it only runs on your laptop. fline gives it an address, a database and a place in the world, so other people can use it.
Get in early. Tell me what is broken.
We are letting people in a few at a time. You will get an email when it is your turn, with everything you need to start.
It does not matter what you built.
A shop. An internal tool. A dashboard your team checks. A game. Something with no name for what it is. Hand it over and we work out what it needs.
You do not describe how it is put together, choose a plan, or answer questions about it.
An address, and something behind it.
A link you can send
It works the moment it is built. There is nothing to point anywhere and nothing to set up first.
A database of your own
We create it and we run it, so you do not have to.
Your own domain, when you want one
Prove the name is yours and the padlock is handled, then renewed, without you.
It stays the same
Deploying the same thing twice gives you the same thing. Going back to yesterday's version takes one instruction.
Your passwords stay yours
Your AI never sees them. You type them once, in your own browser, and nothing hands them back to it.
You hear when it breaks. An email when a build starts, when it goes live and when it fails.
The only research that counts.
You cannot learn whether people want it by asking them to imagine it. They have to be able to open it, use it, and leave.
That is the step fline exists for. Your idea stops being a description and starts being a thing with an address, which is the first moment anybody can tell you the truth about it.
Where we are, honestly.
This list exists because the alternative teaches you that the rest of the page lies. It is maintained, and it is dated.
- Deploying from your AI assistant, once you have granted it a short, named list of permissions
- The platform working out how to run your app, so you never have to write a configuration file
- A database of your own, created for you. We run it, so you do not have to
- A live address the moment it is built, with no step in between
- Your own domain, with the padlock issued and renewed for you
- Going back to an earlier version, as a new version rather than a number that moves back
- An email when a build starts, when it goes live and when it fails
- Seeing what your app is using: processor, memory, network and disk, with the gaps named rather than counted as nothing
- Searching what your app printed, on the project's screen, for the last seven days. Your assistant still only gets the most recent lines
- Every attempt at working out how to run your app is kept, including the ones whose output was rejected. A deploy turned away before the work begins leaves nothing behind
- There is no billing. No price, no currency and no invoice exists anywhere. What you use is measured. Nothing charges for it
- Nothing runs on a timer. An app that runs its own loop is fine. The platform will not wake anything up for you
- Your app runs on one machine. We choose which one, and there are no copies of it running beside each other. If that machine stops answering for five minutes we move your app to a healthy one and start it there. Not if it keeps files on that machine's own disk: those do not travel, so it waits for a person
- We will not promise your data is safe. The platform can copy a database aside. Nothing here puts one back for you. Whether yours is being copied is a setting on the machine it runs on, and this page will not tell you that it is. Keep your own copy of anything you cannot lose
- You cannot pause a project. Stopping one and starting it again is not built
- You cannot change how much your app is given. The sizes exist and nothing lets you pick one
- You cannot read the full record of a deploy. The attempts at working out how to run your app are kept. Reading them back is ours to do today rather than yours
- The walls around your app are ordinary ones. Standard isolation, with nothing heavier added for riskier work. We have checked the outermost of them on a live machine and not yet the rest
- Some of our own services trust the network between them. Others will not talk to a caller that has not proved who it is. Where that proof is not asked for, all that stands in the way is that those ports answer nothing from off the machine
Status as of 29 August 2026 · private beta
There is one person behind this
No support desk and no ticket queue. The mailbox is read; the other two are the same person somewhere more public. A question about whether it runs your stack is a fair thing to send.