Fluid Engineering
Build the tools your business keeps asking for.
Start internal tools, storefront code, and integrations from a working project that’s already wired to your company. Connect your systems through signed webhooks and callbacks, and see every change before it goes live.
Start
Start from a working project, not a blank repo.
Ask Mist for a tool and it sets up the right kind of project, already connected to your company’s data. Nothing is created until a person approves it.
- Six kinds of projectA storefront theme, a hosted app, a rep portal, a portal widget, a rep’s MySite, or a Mist skill, each with its own dev server and publish command.
- Approved before it existsCreating a project waits for a one-time approval that expires 15 minutes after the click.
- Hosted apps, managed in the adminRun a Mist app as a droplet, inside a page, on the mobile app, or on its own, and see every deployment in one list.
- Previewed where it livesSee the app inside the admin, on the phone, or on the checkout page it extends, before it ships.
Connect
103 events. 24 callbacks. One signed contract.
Subscribe your systems to what happens in Fluid, and put your own code inside tax, shipping, discount, payment, and sign-in decisions.
- 103 webhook eventsAcross 30 resources. Orders alone have 16, including edits and fulfillment changes.
- Signed and typedEvery delivery is signed with HMAC-SHA256, and every event has a versioned JSON schema to generate types from.
- Your code inside checkout20 of the 24 callbacks wait for your answer, with a timeout of up to 20 seconds.
- Apps other brands can installDroplets get scoped tokens, signed install and uninstall calls, and a private or public listing.
Automate
Chain the steps, with a reviewer on each.
Workflows run steps in parallel, have a second agent check each one against its acceptance criteria, and hand you anything that still fails.
- A check on every stepStrict, normal, or loose, with rework rounds before a person is asked.
- Approve or retryA step that still fails waits for someone to approve it or send it back.
- On a schedule or on an eventRun hourly, every weekday at 9, on the first of the month, or when an order completes.
- Share them as JSONExport a workflow and paste it into a teammate’s builder.
Code
Design mode for the team. Code mode for you.
The page editor switches between visual editing and the template’s Liquid, CSS, and variables. Engineers can work in their own editor through the CLI and review changes as pull requests.
- One template, two modesThe same page, edited visually by your team or as code by you.
- GitHub sync per branchEach repository branch becomes its own theme, with its sync status in the editor.
- A CLI that respects liveHot reload locally, lint without uploading, and push without publishing until you say so.
- Skills for your coding agentsOne command installs Fluid’s theme skills where your coding agent can read them.
Release
Compare it, publish it, watch it run.
Every version of a page is kept and can be compared, a whole theme can go back to an earlier published version, and every webhook delivery leaves a record.
- Compare any two versionsThe editor’s history shows the Liquid and CSS that changed between them.
- Go back to a published versionRestore the whole theme to an earlier published version when a release goes wrong.
- Delivery logs you can act onSee each webhook’s status and response code, and send a failed one again.
- Test stores for integrationsSpin up a sandbox store to build and test against.
What it replaces
Fewer one-off tools. One platform to build on.
Operations teams keep asking for small tools, and each one tends to become its own vendor, script, or backlog item. On Fluid, they start from a real project, connect through the same events and callbacks, and ship through the same review.
Usually
- Internal-tool builders
- Workflow automation tools
- Repetitive development work
- One-off integration scripts
- Reporting requests
- Projects started by Mist
- Hosted Mist apps
- 103 webhook events
- 24 checkout callbacks
- Workflows with QA
- Code mode, CLI, and GitHub sync
FAQs
Questions engineers ask.
Here’s how building on Fluid works today.
Is there a no-code tool builder in the admin?
No. Tools are real code projects. Mist starts them in its desktop app, now in beta, or you start them from the CLI, and the admin lists and manages what’s deployed.
Can our code take part in checkout?
Yes. Callbacks put your endpoint inside tax, shipping, discount, payment, and sign-in decisions. 20 of the 24 wait for your answer, with a timeout you set of up to 20 seconds.
How do we know a webhook came from Fluid?
Every delivery is signed with HMAC-SHA256 over its timestamp and body, and every event has a versioned JSON schema you can generate types from.
Does Mist publish anything on its own?
No. Creating a project needs a one-time approval, publishing a theme needs an explicit request or a Publish click, and Safe Mode blocks every change to production while it’s on.
Where do scheduled automations run?
Today they run in Mist’s desktop app, with a catch-up rule for runs missed while it was closed.
Can we work in our own editor and Git?
Yes. The CLI gives you a local dev server with hot reload, linting, and push without publishing, and GitHub sync turns each repository branch into its own theme, reviewed through pull requests.
Explore the platform
Build on the whole platform.
Your tools can use the same data, events, and people as everything else in Fluid.
See it with your team
Bring us the tool your team keeps asking for.
We’ll start it together in Fluid, from the request to a working preview.