Terms for the private beta

It is free, and nothing meters it

There is no price, no card held and nothing counting what you use. There is also no billing system that could send you a bill by mistake. The front page's status list records the absence. If there is ever a price it applies to what you do after it exists, and you will not be charged for the beta afterwards.

There is no warranty and no uptime commitment

The platform is provided as it stands. It can be down, a deploy can fail, and a managed database can lose what it was holding. There is no response time, no support commitment and no compensation. Keep your own copy of anything you would mind losing.

It can change, and it can end

Tools change shape, defaults move and a thing that worked last week can be replaced by a better one. The beta itself can end, and nothing on this site is a commitment that it continues. The only address anybody here has for you is the one you signed up with.

An account is one person

One identity, one personal tenant. There is no membership, no roles and no invitations. Nothing in the product knows how to give a second person access to a project. Do not share a login to work around that. If two people need in, two people join the list.

What you may run

The fleet is small, shared and free, and every rule below follows from that.

• Nothing illegal, and nothing you do not have the right to deploy.
• Nothing that attacks anything, in either direction. Scanning, brute forcing, spam and denial of service end the account.
• Nothing whose purpose is to consume the hardware. Mining is the case with a name; the rule is broader than the name.
• No attempt to leave your container or reach another tenant. If you find a way out, that is a bug report and it is welcome. Send it to privacy@fline.sh, which is the address both legal documents publish.

Your project stays yours

You keep everything you upload. The platform reads it to work out how it builds, builds that, and runs it. The stage that costs the most never receives your file tree, and the one that writes the Dockerfiles sees no line of your source.

Ending it

You can stop at any time. Ask for deletion and the row goes, as set out in privacy. An account that breaks the rules above can be suspended, and one that attacks the platform or another tenant is suspended without notice.