The Stack That Doesn’t Need Stitching

Over the last seven articles, I’ve examined what happens when enterprises assemble AI capabilities one vendor at a time:

  1. The Frankenstein Stack emerges — five categories, five vendors, five governance stories, nobody governing the seams.
  2. Bolt-on governance monitors AI but doesn’t do any work — expensive observation.
  3. RPA automates structured tasks but is brittle, unintelligent, and increasingly obsolete.
  4. AI assistants are locked to their vendor’s ecosystem with no cross-system orchestration.
  5. Automation platforms are connector catalogs with “AI” bolted on — they move data, they don’t make decisions.
  6. Autonomous agents do the work but have no governance guardrails — full autonomy or nothing.
  7. The seams between these systems are where risk lives — context loss, silent failures, accountability gaps.

Every one of these layers exists because it solved a real problem. And every one created new problems by operating in isolation.

The pattern is the same one that cost the data quality industry trillions: build capability first, bolt on governance second, spend years managing the gaps between point solutions.

We built something different.

What AICtrlNet and HitLai Actually Do

AICtrlNet is a governed AI orchestration platform. HitLai is the commercial product built on it.

Instead of stitching together five vendors, it’s one platform that handles multiple layers of the stack — with governance built into the execution path, not bolted on from outside.

Here’s what that means in practice:

It does the work. This isn’t a governance tool that monitors other systems. AICtrlNet’s AI agents execute workflows, process documents, interact with external services, make decisions, and take actions. The work gets done inside the platform — not in five separate tools with custom integrations between them.

It governs inline. Every action the AI takes is evaluated before it executes. Allow, deny, or escalate — resolved in the execution path, not flagged by an external monitor after the fact. The same platform that does the work also governs it. No seams between the “doing” layer and the “governing” layer because they’re the same layer.

It gives you the AI Dial. Not a switch between “manual” and “full auto.” Per-workflow, per-agent, per-department autonomy levels that adjust over time based on demonstrated performance. Your support team at full autonomy for Tier 1. Your legal team at human-approval-required. Your finance team at supervised-with-escalation. All running simultaneously, all governed through the same policy engine.

Prof. Mohanbir Sawhney at Kellogg School of Management (Northwestern) observed in a public exchange that orchestration without governance that adapts as AI maturity grows is essential for agents to be trusted. He referred to this concept as Governed AI Orchestration — and we agree. We colloquially call it the AI Dial: the infrastructure that lets you set, adjust, and evolve how much autonomy your AI has, with the governance built into every position.

How It Replaces the Frankenstein Stack

Frankenstein Layer What It Does What AICtrlNet Does Instead
AI Governance (SurePathAI, etc.) Monitors AI from outside Governance is inline — every action evaluated before execution
RPA (UiPath, etc.) Brittle scripts for structured tasks AI-driven browser automation + workflow agents — intelligent, self-healing
AI Assistants (Copilot, etc.) AI inside one vendor’s ecosystem AI agents that work across any system, any channel, any API
Automation (Zapier, etc.) Connector catalog AI-native orchestration with governance on every step
Autonomous Agents (OpenClaw, etc.) Full autonomy, no governance Graduated autonomy — the AI Dial per agent, per task

One platform. One audit trail. One AI Dial. No seams.

What This Looks Like in Production

The insurance company from Part 1 — the one with the five-vendor stack — could replace it with:

  • AI agents that triage claims (replacing the RPA + automation platform handoff)
  • Browser automation that pulls data from legacy systems (replacing the RPA bot)
  • Inline governance that evaluates each claim decision before it executes (replacing the bolt-on governance tool)
  • The AI Dial set to: auto-adjudicate simple claims, route complex claims to adjusters with AI-generated summaries, flag ambiguous claims for senior review
  • One audit trail that shows the complete decision chain from document intake to claim resolution

No seams. No context loss at handoff points. No silent failures between systems. When something goes wrong, the full decision chain — data considered, rules applied, autonomy level, outcome — is in one log, not five.

The bank from Part 7 — the one with the governance gap at the seams — could replace their stack with:

  • AI agents handling customer interactions across any channel (replacing Copilot’s ecosystem lock-in)
  • Workflow orchestration with per-department AI Dial settings (replacing the automation platform)
  • RPA-equivalent capability through browser automation (replacing legacy RPA scripts)
  • Governance that evaluates every action — AI decisions, document processing, external API calls, browser actions — through the same policy engine (replacing the bolt-on governance tool)

The compliance team gets one dashboard. The CISO gets one audit trail. The business line leaders get AI that actually does the work. And the integration team? They’re not stitching five vendors together anymore.

The Three Layers of Reach

The integration objection — “but do you connect to X?” — is what drives enterprises to the connector catalog model (Zapier, n8n) in the first place. If you can’t connect to the tools people use, none of the governance architecture matters.

So we designed for universal reach:

Established ecosystems. Connections through major automation platforms unlock thousands of integrations without building each one individually.

Any API. AI agents that can discover, evaluate, and connect to new services on the fly. Not a roadmap item. Not a future release. In the conversation where you need it.

Any web application. Browser automation that navigates any system a human can use — legacy apps, internal tools, government portals. If it has a URL, the AI can reach it.

Every layer has the same governance. The same AI Dial. The same audit trail. Whether the AI is calling an established API, generating a new integration at runtime, or navigating a legacy web application through a browser.

What We Didn’t Build

We didn’t build a governance layer. There’s no separate “governance product.” The governance is the system. You don’t buy airbags separately from the car.

We didn’t build another automation tool. We built an orchestration platform where AI is the collaborator — making decisions, processing documents, taking actions within the boundaries you set.

We didn’t build for one autonomy level. Different tasks, different teams, different stages of trust require different positions on the AI Dial. Simultaneously. Adjustable over time.

We didn’t build a closed ecosystem. Three layers of reach — established integrations, self-extending agents, browser automation — mean the answer to “do you connect to X?” is always yes.

The Choice

Enterprise AI leaders face a real decision:

Path A: The Frankenstein Stack. Five vendors, five contracts, five governance stories. Each evaluated in its own category. Each good at its job. Together: a complex, fragile system where risk lives in the seams and nobody owns the gaps. Integration tax that grows every quarter. Audit trails that don’t correlate. Governance that monitors but doesn’t prevent.

Path B: Governed AI Orchestration. One platform that does the work and governs it. The AI Dial set per task, per team, per workflow. One audit trail. No seams. Universal reach. Governance that’s built into every action, not bolted on from outside.

The data quality industry spent 20 years proving that bolt-on quality doesn’t work. The AI governance industry is at year 2 of the same cycle.

You don’t have to repeat the pattern.

Where to Start

AICtrlNet Community Edition is free and open source. Standard Docker infrastructure, local AI model support, the full AI Dial. No credit card, no sales call, no lock-in.

HitLai is the commercial product — additional capabilities, expert setup assistance, and enterprise features for organizations that want to move faster.

The Frankenstein stack assembled itself because each tool solved the problem in front of it. But the system-level problem — governed AI orchestration — requires a system-level solution.

That’s what we built.

This is Part 8 of 8 in The Frankenstein Stack series. Read the full series starting with The Frankenstein Stack: How Enterprises Are Assembling AI Wrong.

About the author: Bobby Koritala is the founder of AICtrlNet and HitLai. Previously, he led product development at Infogix (now part of Precisely), building enterprise data integrity platforms for financial services and healthcare. He has spent 9+ years building AI systems, including several patented ones.