Platform overview
How the studio, the product lab, and the platform surfaces around them fit together.
FluxonLab is one brand with several moving parts. They share a design system, a common philosophy and — for the site-native surfaces — the FluxCore account and credit foundation. Each part does a distinct job.
The studio
The consulting and build arm: custom AI systems, websites and automations for clients, delivered the same way we build our own products — approval-gated, local-first where it matters, shipped in weeks rather than quarters. This lane is live today: see Services and the free demo request flow.
The product lab
The public roster currently has nine products. FluxCore appears beside them as the shared platform foundation and is not counted as a product. It supports the site-native products — Prompt Studio, FlowHub, Labs, Blog and Design Studio — while Skillry, Gondar, Nisaba and Obsermania keep independent distribution or runtime boundaries. See Products for the full list with honest statuses.
The platform surfaces
Around the lab we run a set of connected surfaces:
- FluxonLab site — the public marketing, legal, support and docs surface you are on now. See FluxonLab site. (Live.)
- Blog — the editorial journal with a review-gated content pipeline. See Blog. (Live.)
- Docs — what you are reading: the reference for everything above. See Documentation model. (Live.)
- Prompt Studio — Fluxie Prompt Engineer is live; the larger gallery, archive and testing Studio is coming soon. See Prompt Studio. (Split.)
- FlowHub — the first-party workflow marketplace, supported imports, approved provider runtime, and Account purchase and billing are live and usable at initial launch on its own subdomain. Canvas, Studio, and the full AI Assistant arrive later as coming-soon surfaces. See FlowHub. (Live at initial launch.)
- Labs — a credit-gated playground of focused AI tools. See Labs. (Coming soon.)
What ties it together
Three things: a single visual language, the shared FluxCore identity and credit layer for the gated surfaces (see FluxCore), and a rule we do not break — systems over hype. Every surface is labelled with its current availability or explicit launch commitment.
Internal consistency
The same rules show up across the platform: provider keys stay protected, generated outputs keep enough provenance to review later, and risky external actions wait for operator approval. See Privacy and security and Media and prompt rules for the reference version.