Twice a year, Itential holds what we call Product Celebration Week — a dedicated five days where the whole company comes together around the product. For me, this February was my first PCW, and I’ll be honest: I didn’t know what to expect. What I found was an entire organization — engineering, product, and beyond — deeply invested in where this platform is going and excited to push it forward together. This edition added a new dimension to that energy: an AI Agent Hackathon.
But we didn’t just talk about agents.
We built them.
In one week, teams from across the company designed, shipped, and demonstrated 17 working AI agents, spanning infrastructure automation, compliance, DNS, vulnerability management, lifecycle onboarding, real-time observability, checkpoint recovery, and multi-system incident correlation.
This wasn’t experimentation in a sandbox. These were real product extensions. Real integrations. Real road map contributions.
This week wasn’t about theory. It was about operationalizing AI inside Itential.
A creative CLI-driven compliance extension that goes beyond Golden Config. It executes arbitrary CLI commands across inventory, parses operational state, evaluates compliance thresholds, and generates structured audit reports — covering real-time operational posture, not just config drift.
This agent correlates live device software versions with Cisco’s OpenVuln advisories. It pulls current advisories, collects real running versions from devices, cross-references affected releases, and produces severity-ranked remediation recommendations. Manual CVE spreadsheet cross-referencing? Eliminated.
This agent fetches Cisco PSIRT advisories by CVE, logs into devices to verify running software and enabled features, and produces a severity-ranked vulnerability report. What sets it apart: a dedicated Comms sub-agent handles all notifications, keeping tooling clean and the orchestration pattern reusable across teams.
One of the most important automation gaps in the industry is brownfield onboarding. This agent retrieves live configurations, identifies structured service patterns (starting with L3 sub-interfaces), constructs JSON models, and registers them in Lifecycle Manager — without reprovisioning.
Provisioning is easy. Discovering what already exists at scale is hard. This agent solves that.
A fully idempotent synchronization agent that keeps Itential inventory aligned with an external source of truth. It was validated against NetBox but architected to extend to any REST-based CMDB.
A hands-on exploration of Agent Builder capabilities that:
It even gracefully handled a failed GitLab retrieval and continued execution with fallback payloads — making it both a practical tool and a learning blueprint for FlowAI newcomers.
A cross-platform reasoning agent integrating ServiceNow and Cisco Meraki. It retrieves active P1 incidents, pulls live infrastructure state, correlates symptoms with device health, and identifies:
When silent failures are found, it auto-creates P2 incidents and sends a structured executive-ready triage report.
This replaces hours of manual context switching between ITSM and monitoring systems.
Built as a strict ReAct-style goal agent enforcing a four-phase lifecycle:
No blind writes. No duplicate records. No unsafe state transitions.
This is how DNS automation should behave in regulated environments.
Agents previously ran in the dark. You saw results only after completion.
Mission Control introduced:
The infrastructure for SSE streaming is already built – pending routing updates.
This was not just a feature demo, it’s a foundational observability layer for agent execution.
Long-running agents are risky without recovery controls.
The checkpointing contribution introduced:
This fundamentally changes how production agents can be trusted.
Agents hallucinate when they lack authoritative context.
The Knowledge Base feature allows:
No redeployments. No prompt editing. No brittle system-message hacks.
Agents now reason from enterprise truth, not just training data.
Automation shouldn’t stop at dashboards.
A Twilio-powered agent enables FlowAI to place phone calls – escalating incidents to NOC or on-call engineers directly.
When an agent detects something critical, it doesn’t just log it. It calls.
Across all 17 agents, five patterns became unmistakably clear:
Many agents were built entirely on deterministic workflows. The LLM orchestrated them — but execution was grounded in structured tasks.
Explicit ordering of tool calls dramatically improved reliability.
The best agents reasoned before writing – pre-checks, validation steps, rollback logic.
Mission Control and checkpointing show that production agents need live visibility, interruptibility, state recovery, and auditable history.
Four hackathon submissions directly contribute to the product road map. This was not a side project week, it was forward motion.
31 tool bindings across 17 agents signals something important:
FlowAI is not a chatbot wrapper.
It is a reasoning layer over:
The agents built during this week weren’t toy demos — they interacted with real systems and executed meaningful actions.
Most importantly: the team didn’t just experiment with AI. They operationalized it.
The hackathon surfaced a clear direction:
The foundation is there.
In one week:
Real-time observability. Checkpoint recovery. Knowledge-grounded reasoning.
This wasn’t just a Product Celebration Week.
It was proof that Itential isn’t just talking about AI agents.
We’re building them – safely, visibly, and in ways that extend the platform in production-ready directions.
And this is just the beginning.
Learn more about Itential FlowAI →
Learn more about Itential MCP →
Interested in seeing the agents in action? Ankit and I walk through the standout submissions in the video below. 👇
See how Itential connects AI reasoning to governed execution across your entire infrastructure.