Status and access
How FluxonLab labels product maturity, grants access, and keeps previews honest.
FluxonLab uses status labels as an operating contract. A label should tell you what is real today, what is being built, and what is intentionally still closed.
Status labels
| Label | Meaning | Access path |
|---|---|---|
| Live | Publicly available and supported for real use. | Open or install it directly. |
| Split | One surface of the product is live; the larger product remains closed. | Use the live surface; the rest stays labelled coming soon. |
| Building | Actively in construction, previewed honestly. | Read the docs; it opens when its release gate passes. |
| Coming soon | Previewed publicly, not yet open for product use. | No signup wall and no fake door — it opens when it is real. |
Access principles
- Live products have no waitlist — you use them directly.
- Coming-soon labels are availability boundaries, not signup promises.
- Products that mutate outside systems use approval gates by default.
- Provider keys, credit gates and cost-sensitive runs stay server-side.
- Membership plans and FC credits are granted only by the verified server-side ledger — a checkout return page alone grants nothing. See FluxCore.
- Local-first products keep their working data on your machine unless you explicitly connect an external service.
What the docs promise
If a docs page describes a capability as usable, it should exist in the product. If something is planned, in build, or only previewed, the page should say so plainly.
Talking to us
For client work — a custom AI system or a website — use the free demo request flow: a short guided form, human review, and a tailored standard demo at €0. A free FluxonLab account and signed-in session protect the request and its history; the request creates no purchase obligation. For everything else, see Support. Live collaboration is in English or Turkish; the written product can be localized for the target language.