Question 1

How is Xorviex different from n8n, Make, or Zapier?

Accepted Answer

Those tools require you to manually define every node, connection, and trigger. Xorviex takes a plain objective and automatically architects the entire execution layer — agents, APIs, and sequencing — from scratch. There is nothing to build.

Question 2

What is an Operation Unit (OU)?

Accepted Answer

One OU represents one atomic task executed by an autonomous agent — a scrape, a write, an API call, a validation pass. Complex missions consume many OUs in parallel. Unused OUs roll over monthly on Growth and Sovereign plans.

Question 3

How does the Supervisor Layer prevent hallucinations?

Accepted Answer

Every agent output — text, data, API payload — is routed through an independent Supervisor model before it reaches any external system. The Supervisor has no access to execution context, so it audits outputs objectively. If it detects brand DNA mismatches, factual anomalies, or policy violations, it rejects the output and queues a regeneration cycle.

Question 4

Does Xorviex monitor my production environment?

Accepted Answer

Yes. The Self-Healing Engine continuously watches logs, error rates, and uptime across connected services. When it detects a regression, it isolates the failing component, generates a patch, runs it through the Supervisor, and ships the fix — then reports exactly what changed.

Question 5

Can I bring my own LLM or API keys?

Accepted Answer

Yes. Sovereign plan users can route agent computation through their own model providers and API credentials. The Meta-Agent orchestration layer and Supervisor remain Xorviex-managed.

Question 6

Is my data used to train your models?

Accepted Answer

No. All mission data, document DNA uploads, and agent outputs are isolated per workspace and are never used for model training. Enterprise customers receive full data processing agreements.

Sign in