Source: Vibe Coding Verkada Automations with Serval
Source: serval.com/updates/ai-agents-for-it-vibe-coding-verkada-automations-with-serval
What It Covers
Customer-story-as-product-narrative: how Verkada (the founders’ former employer) uses Serval. Most explicit articulation of “vibe coding for IT” as a category term — Serval’s name for the natural-language-to-deterministic-code paradigm.
Key Claims
- “Vibe coding for IT” = describe an automation in plain English → Serval Builder agent generates TypeScript code with tests → IT admin reviews / edits / approves → automation becomes a callable tool for the help-desk agent. (extracted)
- Code-as-contract: automations are versioned, code-reviewable, modifiable in plain English or directly in code. “Git workflows” and “code review” are explicit framings. (extracted)
- Deterministic execution: the help-desk AI agent calls these tools — it does not freeform-generate API calls at runtime. The non-determinism is bounded to which tool and what arguments; the what happens is determined by code. (inferred from product behavior)
- Verkada use cases mentioned: access provisioning, hardware/MDM operations, knowledge-base lookups, employee onboarding flows.
- Repeated mantra: “Faster to automate forever than to do manually once.”
Notable Phrasing
- “Vibe coding for IT” (the category term Serval is trying to own)
- “TypeScript with tests”
- “Git workflows for IT automations”
- “Deterministic tools, agentic invocation”
Strategic Implications
- Serval is explicitly trying to import software-engineering primitives (code review, version control, tests, type safety) into the ITSM admin role. If this lands culturally with IT, Serval’s moat compounds — the IT-admin job becomes a “vibe-coder” job, with Serval as the IDE.
- Sets up a sharp contrast with Console’s policy-blocks-as-natural-language approach: Console hides the code; Serval surfaces it. Both can coexist as design choices.
- Verkada as proof point matters strategically: Verkada is enterprise-grade (security/physical-security org), security-paranoid, and MDM-heavy — exactly the kind of customer that historically forced IT teams to live in legacy ITSM hell.
Limitations
- TypeScript-as-output is a strong opinion — for IT teams without engineering chops, this might be a barrier despite the natural-language wrapper.
- No mention of multi-tenant governance for the Builder agent (e.g., who is allowed to vibe-code which automations).