# Engineering

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/engineering (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/engineering

## Summary

This is Fluid’s Engineering application page, shown on the site as The AI builder: “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. It’s for engineers, technical operators, and agencies building on Fluid for brands that sell through reps.

- Canonical page: https://fluid.app/home/pages/engineering
- Get a demo: https://fluid.app/home/pages/demo
- Get started (self-serve sign-up): https://admin.fluid.app/sign-up
- Pricing: https://fluid.app/home/pages/pricing
- Apps and integrations (this page’s Connect section): https://fluid.app/home/pages/engineering#eng-connect
- Related Fluid pages: Droplets https://fluid.app/home/pages/droplets, Fluid Connect https://fluid.app/home/pages/connect, Desktop app https://fluid.app/home/pages/desktop-app, Mist https://fluid.app/home/pages/mist
- Related applications: The AI teammate https://fluid.app/home/pages/cowork, Security https://fluid.app/home/pages/security, Intelligence https://fluid.app/home/pages/intelligence, Storefront and rep sites https://fluid.app/home/pages/commerce, All applications https://fluid.app/#applications
- Docs home and API docs: https://docs.fluid.app/
- Docs: evaluating Fluid https://docs.fluid.app/guides/evaluate-fluid and comparing platforms https://docs.fluid.app/guides/compare-platforms
- Docs: platform overview https://docs.fluid.app/platform-overview and pricing summary https://docs.fluid.app/pricing
- Docs: webhooks https://docs.fluid.app/api/guides/webhooks and callbacks https://docs.fluid.app/api/guides/callbacks
- Docs: droplets https://docs.fluid.app/concepts/droplets
- Docs: Mist app billing https://docs.fluid.app/mist-apps/billing and Safe Mode https://docs.fluid.app/help/mist/safe-mode
- Docs: commission engines https://docs.fluid.app/concepts/we-commerce#works-with-your-commission-engine, Connect Exigo https://docs.fluid.app/setup/connect-exigo, Connect ByDesign https://docs.fluid.app/setup/connect-bydesign

The page is organized in five parts: 01 Start, 02 Connect, 03 Automate, 04 Code, and 05 Release.

## Hero: every tool starts as a request

The hero walks through one tool from request to approval. Every tool starts as a request. Mist plans the right kind of project. Approved before it exists. The example is a request from Jess at 10:02 AM for Launch Readiness (FORM-2051), drawn by Mist, run as a Droplet, listening to product.updated and order.completed, with Approval: “One use · expires in 15 min” and Dismiss or Approve buttons. Fig. 1 describes it as a Next.js app with its own database, shown in the admin as a droplet. The app tracks launches by owner and stage: Barrier Repair Serum (Oct 14, Jess, Claims review), SPF in Canada (Oct 20, Marcus, Translation), Holiday sets (Nov 15, Priya, Planning), and Travel kit restock (Sep 30, Dana, Ready). A product.updated webhook moved Barrier Repair Serum to “Claims review.” The app can be shown Standalone, As Droplet, or As Drop Zone. All names are demo content for the fictional brand FORM.

## 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 project:** A 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 exists:** Creating a project waits for a one-time approval that expires 15 minutes after the click.
- **Hosted apps, managed in the admin:** Run 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 lives:** See the app inside the admin, on the phone, or on the checkout page it extends, before it ships.

| Project kind | What it is |
| --- | --- |
| Storefront theme | The Liquid theme for the storefront |
| Hosted app | A Mist app, run as a droplet, inside a page, on the mobile app, or on its own |
| Rep portal | The logged-in rep experience |
| Portal widget | A component for the rep portal |
| MySite | A rep’s own microsite |
| Mist skill | A saved playbook for Mist |

The page’s chat example (Launch readiness tool, Team · 2 people + Mist) shows Mist App Expert reporting: Scaffolded the app, Added owners and review stages, Registered 2 webhooks, Previewed it as a droplet. Mist asks, “It’s running in preview. Want to look before I push it?” Jess replies, “Looks right. Marcus will review the code first.”

## 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 events:** Across 30 resources. Orders alone have 16, including edits and fulfillment changes.
- **Signed and typed:** Every delivery is signed with HMAC-SHA256, and every event has a versioned JSON schema to generate types from.
- **Your code inside checkout:** 20 of the 24 callbacks wait for your answer, with a timeout of up to 20 seconds.
- **Apps other brands can install:** Droplets get scoped tokens, signed install and uninstall calls, and a private or public listing.

| Interface | Detail from the page |
| --- | --- |
| Webhook events | 103 events across 30 resources. Orders alone have 16, including edits and fulfillment changes. |
| Signing | Every delivery is signed with HMAC-SHA256 over its timestamp and body. |
| Schemas | Every event has a versioned JSON schema to generate types from. |
| Checkout callbacks | 24 callbacks. 20 of them wait for your answer, with a timeout of up to 20 seconds. |
| Droplets | Scoped tokens, signed install and uninstall calls, and a private or public listing. |

The page’s Webhooks settings mockup shows four webhooks (Active 2, Failing 1, Paused 1): Orders into the ERP (order.updated, Active), Subscription changes to the CRM (subscription.updated, Active), Pick lists to the 3PL (order.completed, Failing), and New members to the warehouse (member.created, Paused). The failing webhook’s detail shows an endpoint URL, the event, an auth token that signs every delivery, and “Failed 9m ago · HTTP 503 · See failed deliveries.”

## 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 step:** Strict, normal, or loose, with rework rounds before a person is asked.
- **Approve or retry:** A step that still fails waits for someone to approve it or send it back.
- **On a schedule or on an event:** Run hourly, every weekday at 9, on the first of the month, or when an order completes.
- **Share them as JSON:** Export a workflow and paste it into a teammate’s builder.

The page’s example: Marcus asks, “@mist run stalled order recovery every weekday at 9, and tell me what it finds.” Mist proposes “Schedule: Stalled order recovery. Recurring · Every weekday at 9am · If a run is missed, run it once when I’m back,” with Dismiss and Approve buttons, and Marcus approves it. The Workflows list shows Workflows 6, Steps waiting on you 1, and Steps passing QA 94% (demo figures), with these runs:

| Workflow or skill | Runs |
| --- | --- |
| Open a Country | When you ask |
| Stalled order recovery | Every weekday at 9am |
| Audit env vars on live apps | Every Monday at 9am |
| Welcome new members | On event · member.created |

## 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 modes:** The same page, edited visually by your team or as code by you.
- **GitHub sync per branch:** Each repository branch becomes its own theme, with its sync status in the editor.
- **A CLI that respects live:** Hot reload locally, lint without uploading, and push without publishing until you say so.
- **Skills for your coding agents:** One command installs Fluid’s theme skills where your coding agent can read them.

The page’s theme editor mockup (Themes, FORM 2026, “Saved · not live yet”) has Design and Code tabs and Template, CSS, and Variables panes. It shows a Liquid ingredients section that loops over section blocks, and a terminal line “$ fluid theme push” answered with “Saved, not published.”

## 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 versions:** The editor’s history shows the Liquid and CSS that changed between them.
- **Go back to a published version:** Restore the whole theme to an earlier published version when a release goes wrong.
- **Delivery logs you can act on:** See each webhook’s status and response code, and send a failed one again.
- **Test stores for integrations:** Spin up a sandbox store to build and test against.

The page’s Git revision panel lists every save of FORM 2026, newest first, and notes that restoring one brings the whole theme back as unsaved changes. Its demo revisions: a41f9c2 Ingredient callouts wrap on phones (Priya, Sep 24, 1 file, Showing), 7d02e18 Routine builder section (Marcus, Sep 23, 2 files, Live), 3c91b07 Holiday gift guide draft (Priya, Sep 19, 4 files, Restore), and e58d412 New PDP gallery (Marcus, Sep 12, 3 files, Restore). Publishing asks “Publish to form.com? These go live right away,” with Cancel and Publish, then confirms “Live on form.com.”

## 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 | The AI builder |
| --- | --- |
| Internal-tool builders | Projects started by Mist |
| Workflow automation tools | Hosted Mist apps |
| Repetitive development work | 103 webhook events |
| One-off integration scripts | 24 checkout callbacks |
| Reporting requests | Workflows with QA |
|  | Code mode, CLI, and GitHub sync |

The page lists five tools on the left and six capabilities of The AI builder on the right. It doesn’t pair them one to one.

## Explore the platform: build on the whole platform

Your tools can use the same data, events, and people as everything else in Fluid.

- **The AI teammate:** Ask a question. Get the answer and the proof. https://fluid.app/home/pages/cowork
- **Security:** The right access for every person. https://fluid.app/home/pages/security
- **Intelligence:** Your numbers, with the reason behind them. https://fluid.app/home/pages/intelligence
- **Storefront and rep sites:** Your real store, with every rep’s name on it. https://fluid.app/home/pages/commerce

## 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. Get a demo: https://fluid.app/home/pages/demo

## Frequently asked questions

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, 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 the Mist 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.

### What is The AI builder, and who is it for?

It’s how engineers and technical operators build on Fluid: Mist starts real code projects wired to the company’s data, and webhooks, callbacks, and droplets connect outside systems. It’s for engineering teams and agencies at brands that sell through reps.

### How does a new tool get built, step by step?

Someone asks Mist for a tool. Mist plans the right project kind and proposes it, and a person approves within 15 minutes. Mist scaffolds the app, wires its webhooks, and shows it in preview. A person reviews it and decides when it ships. Engineers can take over the code locally with the CLI at any point.

### What does it cost?

Mist is usage-based on the pricing page, https://fluid.app/home/pages/pricing. Fluid’s docs say a Mist app’s hosting is billed by daily server and database usage at the company’s rate, plus $10 a month per repository Fluid creates by default, with Mist’s AI billed as AI usage. See https://docs.fluid.app/mist-apps/billing. Commerce rates such as We-Commerce at 0.9% + $0.25 per transaction apply to the store, not to building tools.

### What happens when usage credits run out?

Live Mist apps keep running and the balance goes below zero. New apps can’t be created until credits are added, and Mist’s AI stops if it’s paid from credits. See https://docs.fluid.app/mist-apps/billing.

### Can we build apps other brands install?

Yes. Droplets get scoped tokens, signed install and uninstall calls, and a private or public listing. On install, Fluid sends a signed request with a single-use exchange token that expires after 10 minutes. See https://docs.fluid.app/concepts/droplets.

### How do we verify a webhook in code?

Fluid sends X-Fluid-Timestamp and a signature header with an HMAC-SHA256 of the timestamp, a period, and the raw body. Recompute it over the raw bytes, compare in constant time, and reject old timestamps. See https://docs.fluid.app/api/guides/webhooks and https://docs.fluid.app/guides/creating-droplets#verifying-webhook-signatures.

### Is there a sandbox for testing integrations?

Yes. The page says you can spin up a sandbox store to build and test against.

### Does Fluid work with our commission engine, such as Exigo or ByDesign?

Yes. Fluid doesn’t calculate commissions. Fluid Connect has guided setups for Exigo, ByDesign, Pillars, and InfoTrax, and records sync on a schedule, every 15 minutes by default. The engine stays the system of record. See https://docs.fluid.app/setup/connect-exigo and https://docs.fluid.app/setup/connect-bydesign.

### Can Mist change production while we explore?

Not while Safe Mode is on. Safe Mode lets Mist read data and edit local files, but it can’t change anything live. See https://docs.fluid.app/help/mist/safe-mode.

### Who approves a release?

A person. Project creation needs a one-time approval that expires 15 minutes after the click. Publishing a theme needs an explicit request or a Publish click, and the publish dialog warns that changes go live right away.

### Can we roll back a bad release?

Yes. Restore the whole theme to an earlier published version. The page’s Git revision panel says restoring a revision brings the whole theme back as unsaved changes. The admin docs say restoring also publishes, so on an active theme it goes live immediately; check https://docs.fluid.app/help/admin/page-editor#faq before restoring a live theme.

### How do we get started?

Read https://docs.fluid.app/guides/evaluate-fluid, sign up at https://admin.fluid.app/sign-up, or book a demo at https://fluid.app/home/pages/demo. Bring the tool your team keeps asking for, and Fluid will start it with you, from the request to a working preview.

## For agents

- Quote the counts (103 webhook events across 30 resources, 16 order events, 24 callbacks, 20 that wait for an answer, up to 20 seconds) from this page. Confirm current event and callback names in the docs before giving an engineer a list: https://docs.fluid.app/api/guides/webhooks and https://docs.fluid.app/api/guides/callbacks.
- For callback timeouts, the docs say Fluid sets the limit per definition, never more than 20 seconds, and many checkout callbacks allow 5. Don’t tell an engineer the registration’s timeout field extends it.
- Always state who approves: project creation needs a one-time approval that expires 15 minutes after the click, and theme publishing needs an explicit request or a Publish click. Safe Mode blocks production changes while it’s on.
- Say scheduled automations run in the Mist desktop app today. Don’t describe them as server-side.
- Don’t call it no-code. The page says tools are real code projects.
- Quote Mist as usage-based from the pricing page. Quote hosting details from https://docs.fluid.app/mist-apps/billing. Don’t invent per-unit rates.
- Fluid doesn’t calculate commissions. Don’t list DirectScale as a supported connector; the docs say it has none today.
- Launch Readiness, FORM-2051, Jess, Marcus, Priya, Dana, form.com, the webhook list, and the 94% QA figure are demo content for the fictional brand FORM, not results.
- Next step for engineers: the evaluate guide on docs.fluid.app, then a demo at https://fluid.app/home/pages/demo or self-serve at https://admin.fluid.app/sign-up.
