FluxonLab Roadmap
Roadmap
The constellation in three delivery waves: live-at-launch foundations and FlowHub, the product being completed for the approved launch target, and work planned on the horizon.
The surfaces that work on day one — the public site, shared account core, prompt bench, services studio, and FlowHub marketplace/import/runtime/billing experience.
The multilingual home of the constellation: a fast, light-first site that explains the studio, the products and the work. The Journal publishes human-reviewed field notes from the workshop instead of automated content.
One FluxonLab account with a shared credit wallet that every product in the constellation draws from. Members manage plans and usage in self-service; operators get a proper control plane.
Fluxie’s Prompt Engineer turns a rough idea into a structured, provider-aware prompt on a guided bench. Deterministic refine steps and quality gates — live at prompt.fluxonlab.com on launch day.
The services line ships from day one: custom web platforms, dashboards, automations and AI assistants built per client. Funding-aware digitalization packages for eligible Vienna and Austrian SMEs.
Live at initial launch on flowhub.fluxonlab.com: curated catalog discovery, clean downloads, guarded imports, and an approved provider runtime. Account-backed purchase access and billing are included; Canvas/Studio and the full AI Assistant follow later as Coming Soon.
Design Studio’s first-party commerce surface belongs to the launch target and is completed within the launch window.
A first-party theme catalog at design.fluxonlab.com with checkout, entitlements and protected delivery. Every theme is built and maintained by FluxonLab — no third-party sellers.
Planned after the launch waves — designed on the same shared account and credit core.
A controlled playground where image, video, voice, music and text tools run on the shared credit wallet. Planned after the launch waves, with cost visibility designed in from the first run.
Bring a workflow, product idea or existing system. We’ll map the clearest route from scope to a working first release.
Roadmap rules
Each wave starts with a public or internal surface that can be tested before it becomes a larger platform promise.
The website stays a marketing and account surface; heavy production engines belong in controlled tools and desktop workflows.
Credits, media runs and model calls need ledgers before they become customer-facing features.
Delivery horizon
The website, account core, prompt bench, services, and FlowHub are live at initial launch. Design Studio is completed within the approved launch target; Labs follows on the horizon.
