How is this different from a Big-4 firm pitching AI?+
Big-4 sells decks. We ship running systems. Our principal has been in your operations center, has run real enterprise networks, and demos working agents live on the Cisco DevNet podcast. You won't get a 200-page deliverable; you'll get a deployed pilot.
What does a pilot cost?+
We don't publish numbers because every environment is different — integrations, data access, success metrics, and team size all change scope. We can give you a budget range in the first 15 minutes of the discovery call.
Why a network engineer building AI consulting?+
Because most "AI in networking" projects fail at the integration layer — CMDB, telemetry, change management, SIEM. A senior network architect understands that layer. An AI engineer who's never touched OSPF doesn't. The credibility cost of selling unsound network advice is too high to fake.
Will agents have write access to production?+
Not without explicit per-action approval until your team votes to remove the gate. Even then, every action is logged, every change is reversible, and every workflow has a verification loop. We build guardrails before we build autonomy.
Do you work with non-Cisco environments?+
Yes. Our agents support multi-vendor environments (Juniper, Arista, Palo Alto, Fortinet, Check Point, and more). Cisco is overrepresented in our public demos because that's where we have the deepest expertise — not a requirement.
Where is data stored? Are you GDPR-compliant?+
vExpertAI GmbH is a German company under full GDPR — built in the EU, for EU operational reality. By default no operational data leaves your environment: agents run in your cloud or on-prem, and the specialist models can be fine-tuned on your network and served on your own infrastructure — no shared cloud brain. If you choose a hosted LLM, it's under your contracts (Azure OpenAI, AWS Bedrock) or explicit DPA addenda, with EU-hosted options at every layer. And because every agent action is human-approved and logged with the evidence behind it, the deployment produces the change-rationale trail your DORA and NIS2 processes already require — as a by-product of normal operations.
Can this support our DORA / NIS2 obligations?+
It's designed to. DORA and NIS2 both push you to document why each change to a critical system happened and what evidence justified it. Our agents diagnose against live device state and a deterministic rule set, then surface a recommended action for a human to approve — and every step (trigger, evidence gathered, the rule that matched, who approved it, when) is written to an audit trail. You get that decision-rationale record without adding 45 minutes to every change ticket. We're a consultancy, not your compliance officer — but the system is built to feed those evidence requirements, and we map it to your control framework in the pilot.
What happens after the pilot?+
Your team owns the system. We hand over the runbook, observability dashboards, and retraining playbook. Continued support is optional, retainer-free, billed per engagement. Most clients add a quarterly review and a follow-on training cohort — but neither is required.