Flows for logic, UI Screens for menus, Quests for checklists — connect them visually in the browser, watch every node execute live once it's running, and a small runtime resource makes it real on your FiveM server.
Built for FiveM ·QBCore·ESX·Standalone
Shops · Bounty boards · MDTs · Garages · Delivery jobs — all built the same way
A Flow waits for a trigger — a button click, a chat command, a zone — then runs a list of steps. Check something, branch true or false, give an item, add money, send a notification. Drag a node in, fill in its fields, connect the branches.

Design shops, HUDs, and dashboards by dragging panels, text, and buttons onto a canvas — no HTML or CSS. Wire a button straight to a Flow, and a Flow can open, update, or close the screen right back. What you place on the canvas is the literal document the runtime interpreter renders on your server — same layout, same pixels, nothing regenerated or reinterpreted in between.


A Quest is deliberately simple — a named, ordered list of stages. All the real behavior (progress, rewards, reactions) is just more Flow steps, so a quest stays easy to design while still driving arbitrarily complex behavior.

Connect your server and see exactly what's executing, live — which node fired, from which Flow, for which player, how long it took, and whether it succeeded, warned, failed, or was skipped. This is the difference between a no-code toy and a tool you can actually debug in production.

A Pack bundles Flows, UI Screens, and Quests that already work together — one install, and every button is already wired to its logic. Then it's yours to edit however you like, not a black box.
A real Pack from the marketplace, shown exactly as priced today — see the full catalog after you sign up.
Sign up, and you'll have a working Flow connected to a real UI screen in a few minutes — no Lua to write, and Flow/UI Screen changes hot-reload on your server with one command, no restart.
Get started free