Run it in your environment
The repo, docs, Dockerfile, and Fly configuration are there so teams can deploy their own instance and keep operational ownership.
Mermaduckle is software you can run in your own environment. The /app
route on this site is our hosted evaluation instance so teams can inspect the control
plane before deploying it themselves. Commercially, we make money on managed pilots,
hosted operations, and annual self-hosted support.
/app
Managed rollout available
One Rust service from local dev to Fly
Human reviewer required before posting the external action.
Captured actor, status, and timing metadata.
Produce a readable artifact after execution closes.
Bring the run back with context instead of starting blind.
flyctl deploy --remote-only --config fly.toml
The public /app route is our live hosted instance for evaluation.
The same Rust service can be deployed in your own Fly app or infrastructure.
We can host, tune, and support the first production workflow when speed matters.
This should be obvious when you land here: Mermaduckle is built to run in the customer's environment, but we also host a live evaluation instance on this domain and offer a managed commercial path for teams that want help getting to production.
The repo, docs, Dockerfile, and Fly configuration are there so teams can deploy their own instance and keep operational ownership.
The /app route on this site is our hosted control plane so buyers can see the
workflow, approval, and audit surfaces immediately.
If a team wants outcomes before they want infrastructure ownership, we can host, integrate, and support the production rollout as a paid engagement.
Public positioning from Langflow and Flowise centers on visual AI building. n8n and Pipedream emphasize broad automation and integrations. Mermaduckle is strongest in the space between those two camps: the governed operating layer for AI workflows in a system your team can actually host, inspect, and ship.
Tools like Langflow and Flowise are optimized for designing chains, prompts, and agent logic quickly.
Tools like n8n and Pipedream are optimized for connector breadth and event-driven automations across many apps.
When a workflow needs approval, auditability, secrets, recovery, and a production deploy path, Mermaduckle keeps those concerns in the same control plane.
The goal is not to race n8n, Flowise, or Langflow to the lowest self-serve plan. The money is in getting important workflows live, keeping them governed, and backing teams that either want a hosted operator or need support for self-hosted rollout.
Use Mermaduckle to launch the first production workflow with hands-on delivery.
Run the control plane for customers that want outcomes without owning infra from day one.
/app instance is the clearest proof this mode existsSell commercial terms to teams that want control over data, deployment, and operations.
The app already exposes a pending approvals queue, audit events, reporting endpoints, retry and recovery flows, and the settings surface needed to manage keys, secrets, and integrations around the workflow itself.
Pause at pending_approval, hold risk, and resume only with an explicit action.
Track workflow, approval, and agent activity with event types, actors, and timing.
Use logs and context to patch a run and retry without discarding the operating record.
Enter from external events or timed execution.
Use the workflow engine while secrets and integrations stay centralized.
Keep the decision record, the run data, and the report endpoint available.
This is not speculative roadmap copy. These are the product surfaces already present in the app and server: workflow building, agent operations, governance controls, runtime settings, reporting, and deployment infrastructure.
Create, edit, import, export, debug, and run flows on a visual canvas.
Turn plain-language workflow requirements into a generated starting graph.
Configure agents, inspect recent runs, and chat directly inside the control plane.
Manage API keys, environment secrets, integrations, notifications, and webhook endpoints.
Run flows on cadence or trigger them from external systems in production.
Expose dashboard metrics, audit timelines, workflow reports, and system status in one app.
The repo already ships with a Fly Dockerfile, a working fly.toml,
GitHub Actions deployment workflow, and a PowerShell helper script. The same Rust
service can power the hosted eval here or a customer-owned deployment elsewhere.
flyctl deploy -a mermaduckle --remote-only --config fly.toml
Push to main for GitHub-driven deploys, or run the included helper
script from your machine when you want to cut a release directly.
deploy/Dockerfile.fly for multi-stage Rust buildsfly.toml with HTTP/TLS ports and health checks.github/workflows/fly-deploy.yml for push-to-main deploymenttools/deploy_fly.ps1 for local production releases/api/health for verification after deploy