AIS Runner
Azure Integration Services — local development desktop
Run and test Azure Logic Apps locally without pushing to Azure. One-click Azurite + func start, live run history, workflow analysis bar, Service Bus queue counts, CI/CD DevOps view, Liquid template tester, and workflow chain graph — all in one desktop app.
Free for personal, educational and non-profit use. Commercial use — including a solo consultant on client work — requires a licence. Every build is produced by release CI and served from mayorana.ch.
The macOS build is signed with an Apple Developer ID and notarized, so it opens with a normal double-click.
Overview
Developing Azure Logic Apps Standard normally means a slow loop: change a workflow, deploy it, trigger it, dig through the Azure portal to find out what happened, repeat. AIS Runner collapses that loop onto your own machine.
It starts the local stack for you — Azurite for storage emulation, Azure Functions Core Tools to host the workflow runtime — and then gives you the views the portal makes you hunt for: run history as it happens, how your workflows chain together, and what is sitting in your Service Bus queues.
It is a native desktop app written in Rust with Dioxus, so it starts instantly and stays out of the way of the rest of your toolchain.
What it does
Local stack from the toolbar
Azurite, the Service Bus Docker emulator, func start for Node.js workflows and mvn azure-functions:run for Java apps, each a button. func start runs pre-flight fixes first: package.json, connections.json ARM syntax, and stubs for missing settings.
Mock APIs
Scans every workflow.json, builds a contract of the outbound HTTP calls from adjacent Parse_JSON schemas, serves stubbed responses locally, and repoints the URL app settings at them. Stopping restores local.settings.json.
Record and replay tests
Capture a multi-step scenario — create a container, send a message, trigger a workflow — as plain JSON committed next to the workflows, then replay it with a live pass/fail per step, including waiting on a triggered run and asserting its outcome.
Live run history
Trigger any workflow with an auto-generated payload and watch the action timeline update in real time, with app logs filtered to just the workflow you selected.
Workflow analysis bar
Per workflow: trigger type, the Service Bus queues it reads and writes, blob containers, outbound HTTP calls and Liquid maps — so a workflow that silently never fires is visible rather than assumed working.
Connections and Liquid maps
Service Bus queues with message and dead-letter counts plus test sends, Cosmos DB, SQL, SFTP and blob browsing, and a maps tab that tests .liquid and .xslt templates against auto-suggested input on either DotLiquid or Liquid.
Azure DevOps view
Build pipelines grouped by folder, and a grid of build runs against release environments showing what is deployed where — queue a build from any branch, or click through to re-deploy a superseded run.
Requirements
- macOS on Apple Silicon, Windows, or Linux x86_64
- The installers handle the runtime dependencies: setup-linux.sh installs WebKitGTK, Node.js 20, Azure CLI, Azurite and Functions Core Tools on Debian/Ubuntu, Fedora and Arch; the Windows wizard offers the same in one step
- Azure CLI signed in (az login) for the subscription-backed panels
- A Logic Apps Standard project on disk, with a logic_apps/ folder
- Docker, if you want the Service Bus emulator
Built with
Rust · Dioxus · Azure CLI · Azurite · Azure Functions
Licence
Source-available under the PolyForm Noncommercial License 1.0.0: free for personal use, learning, research and hobby projects, and for charities, schools, universities and government institutions. Companies using it for work buy a licence.
Source
The source is public and readable. Fork it and rebrand it — the name and logo are trademarks and are not covered by the licence.
View on GitHubQuestions
Does it need an Azure subscription?
Not for local running — Azurite, the Service Bus emulator and Functions Core Tools cover that offline. The Connections and DevOps panels do read a real subscription through the Azure CLI, so those need az login.
Does it change my workflow files?
It reads and runs your Logic Apps Standard project. Two things it does write: starting Mock APIs rewrites the URL-shaped values in local.settings.json to point at the local mocks and restores the file on stop, and MSI connections are patched to local connection-string auth on every func start.
How is this different from running func start myself?
You can run func start yourself. What a terminal does not give you is the run history, the analysis bar, queue counts, the Liquid tester, the mock server and replayable scenarios in one place, refreshing as runs land.
Can I verify what I downloaded?
Yes. Each GitHub release carries a latest.json with the sha256 of every artifact.
Need this adapted to your stack?
These tools came out of real Azure integration work. If yours needs a variant — a different data source, your own conventions, an on-prem build — that is the kind of work we take on.
Get in touch