Great when the job is getting to a working flow quickly.
Visual agent builders are strong for composition, prompting, and iteration. They are not always the place teams want to manage production review and operational accountability.
Production control for AI workflows
Build fast. Ship carefully. Operate AI workflows like production software.
Mermaduckle is the operating layer for AI workflows that touch customers, revenue, or internal systems. Build visual flows, route high-impact actions through human approval, manage agents and secrets, keep an audit trail for every run, and deploy the same Rust service in your own environment or with rollout support.
This domain includes a public sandbox at /app. Customer production
deployments can run as separate self-hosted or supported environments.
Why it exists
Mermaduckle sits between workflow prototyping and production operations.
Most teams start with a tool that is optimized either for visual flow design or for broad automation across external services. The gap appears later, when an AI workflow needs review gates, auditability, runtime ownership, and a deployment model the infrastructure team can live with.
Great when the job is moving data across many services.
Automation platforms win on connector breadth and event plumbing. They are a less natural fit when the core requirement is governed AI workflow execution.
Built for the moment AI automation becomes operational software.
The product centers on workflow runtime, approval, audit, agent operations, and a deployment model that can move from evaluation into customer-owned environments.
Competitive position
A clearer fit than generic "AI automation" positioning.
Public competitor positioning points to three dominant patterns in the market: connector-heavy automation, visual agent composition, and developer-first event orchestration. Mermaduckle is strongest in the operating layer those products usually leave to custom process.
Platform
What it is optimized for
Where Mermaduckle is different
n8n
automation platform
Broad automation, connector coverage, and code-plus-visual workflow assembly.
Mermaduckle is the tighter fit when approval gates, audit history, and AI workflow ownership are the first-order requirement.
Langflow / Flowise
visual AI builders
Rapid composition of agents, chains, prompts, RAG flows, and experiments.
Mermaduckle is the better operational fit when teams need review, reporting, runtime visibility, and a product built around governed execution.
Pipedream
developer automation
API-first event automation, integrations, and fast developer workflows.
Mermaduckle is more focused when the problem is running AI workflows safely rather than maximizing integration and event breadth.
Mermaduckle
production AI operations
Workflow studio, approval queue, audit trail, agent operations, secrets, integrations, and deployment in one product surface.
Use it when the workflow itself is part of the product, the process, or the risk surface.
Platform depth
The app already covers the surfaces operators actually need.
The live product is not a shell around one builder screen. It already includes the workflow, agent, approval, audit, settings, and deployment-adjacent surfaces teams use once workflows stay in production.
Workflow studio
Create, edit, import, export, debug, and run workflows from one visual canvas.
AI architect
Generate a draft workflow from a prompt, then refine it as an operator.
Approval queue
Route high-impact steps through explicit human review before continuing the run.
Audit and reports
Inspect historical events, export audit output, and keep a durable run record.
Agent and runtime control
Manage agent configs, test prompts, store secrets, issue API keys, and review health.
Webhooks, schedules, integrations
Trigger from external systems, run on cadence, and connect the workflow to the rest of the stack.
Deployment model
A simple story: public sandbox here, customer environments there.
One of the current points of confusion was treating the public app on this domain and the self-hosted product as if they were different things. They are not. This site hosts a sandbox. The same service can be deployed separately for a customer-owned or supported environment.
Use this domain to evaluate the product.
Open /app to inspect the current workflow, approval, agent, and audit
surfaces without having to deploy your own environment first.
Deploy the same service in your own infrastructure.
The repository includes the Fly deploy path, Dockerfile, and runtime configuration you need to launch a separate customer-owned instance.
Use Mermaduckle with implementation help.
Teams that want faster adoption can use a supported rollout for the first workflow, the first production environment, and the first operating handoff.
Routes on this domain
/company and product overview/applive sandbox of the current product/docsdeployment guide for self-hosted rollout/api/healthservice readiness endpoint
Self-hosted deploy
Open the guide
flyctl deploy -a <app-name> --remote-only --config fly.tomlThe repo includes a multi-stage Dockerfile, GitHub Actions workflow, and PowerShell helper for customer-owned Fly deployments.
How teams buy
Start with the software. Add rollout and support when the workflow matters.
Mermaduckle is easiest to adopt when the buying model matches the product model: start in a self-hosted environment, then add help where production ownership becomes expensive. The point is not feature gating. The point is faster rollout, better operating discipline, and clearer support once workflows matter.
Start with the software.
Use the open-source product for evaluation, internal pilots, and customer-owned deployments that your team wants to run directly.
- Builder, approvals, audit, agents, and settings in one app
- Runs in the same Rust service you can inspect in the repo
- Best for teams that want full infrastructure ownership
Pay for faster time to production.
Bring Mermaduckle into production with implementation help, operating guidance, and a faster path through the first governed workflow.
- Initial workflow implementation and environment setup
- Operator onboarding, deployment support, and launch reviews
- Best for teams that want speed without giving up deployment choice
Keep production ownership clear.
Once the workflow matters to the business, the relationship shifts toward response commitments, environment reviews, upgrades, and operational support.
- Priority issue response and rollout advisory
- Environment reviews and production operating support
- Best for customer-owned or supported long-lived deployments
Pricing principle: the product should be sold around deployment and
operating ownership, not on per-step gimmicks or vague AI credits.
Get started