VICTOR Platform - PCA Technology Inc.

01 :: why_victor_exists

Why VICTOR Exists

Enterprise MSPs charge $125–$225/user/mo to cover account managers, SDR teams, and helpdesk queues. That model can't serve a solo freelancer or a 3-person law office.

Daniel has been running Houston IT since 2017. 130+ environments. Patching, monitoring, onboarding, M365 audits, backup verification, MFA rollouts, ticket triage — all of it. In 2026 he codified that into VICTOR. VICTOR handles the repetitive 80%. Daniel handles the hard 20%. That's why $99/month works.

9 years experience codified

11 named operator agents

80% tasks automated

$99 entry price / mo

# The math that makes VICTOR necessary
enterprise_msps: $125-$225 # /user/mo
overhead: ["account mgrs", "SDR teams",
  "Tier1 queue", "quarterly MBRs"]
viable_minimum: ~25 users

# VICTOR's model
automation_rate: 0.80  # repetitive ops
human_rate: 0.20     # hard decisions
entry_price: $99      # 1-3 endpoints
        

02 :: roi_calculator

What Does VICTOR Cost vs. What You're Paying?

Enter seat count and current monthly IT spend. Get the right tier and estimated savings.

savings calculator

number of users / seats

current monthly IT spend ($)

Flat-rate tiers. Your IT cost doesn't grow when you hire. The calculator routes your seat count to the closest tier vs. the typical Houston MSP rate of $150/user/mo.

Every tier includes VICTOR monitoring, patch management, and escalation to Daniel.

see full tier breakdown

03 :: platform_architecture

Platform Architecture

VICTOR runs on AIHost (Ubuntu, in Daniel's office) with 15 Docker containers coordinated through OpenClaw. Every tenant is isolated at the database layer via PostgreSQL RLS.

~/victor/status.sh

live output

$ victor --status

Runtime: OpenClaw (proprietary agent orchestration)

Gateway: Victor Gateway (Node.js, WebSocket + REST)

Dashboard: ORACLE (React / Next.js)

Reasoning: VICTOR-grade models (fast / standard / extended)

Sub-agents: PLAN-ORCH / RUN-ORCH / PLAN-DES / PLAN-CHAL

RESEARCH-SCOUT / TASK-EXEC / PLAN-GUARD / VAL-LEAD

Isolation: PostgreSQL Row-Level Security (per-tenant)

Infrastructure: AIHost (Ubuntu) + Docker Compose (15 containers)

Tunnels: Cloudflared (zero inbound firewall holes)

Recovery: recovery-watcher (1 min) + metadata-writer (15 min)

Backup: QNAP NAS + scheduled Docker volume exports

Deployment: Production @ PCA + pilot tenants (PMG, others)

> STATUS: OPERATIONAL | BATTLE-TESTED ACROSS 130+ ENVIRONMENTS

// agent topology

When PLAN-GUARD determines a task is not certain-to-succeed, it escalates to Daniel rather than automating a mistake at scale.

04 :: agents

The VICTOR Agent Layers

Two layers: 11 named operator agents (VICTOR, AXIS, NOVA, CODEX, ARIES, NEXUS, ORACLE, AURUM, JANUS, LUMEN, ARBITER) at the client level, and 8 orchestration sub-agents inside OpenClaw. No shared state between tenants.

# victor/agents/manifest.yaml -- sub-agent roster (internal orchestration layer)
agents:
  - id: PLAN-ORCH      # orchestrates planning sessions end-to-end
  - id: RUN-ORCH       # coordinates task execution across all agents
  - id: PLAN-DES       # designs plans, timelines, resource allocation
  - id: PLAN-CHAL      # challenges plans for gaps and risk before commit
  - id: RESEARCH-SCOUT  # gathers external and internal context for plans
  - id: TASK-EXEC      # executes approved tasks autonomously
  - id: PLAN-GUARD     # validates every action before execution fires
  - id: VAL-LEAD       # validates outcomes post-execution, closes the loop

reasoning: VICTOR-grade models  # fast / standard / extended tiers
isolation: postgres-rls          # enforced at DB role level, not app layer

# Customer-facing operator agents (11 named agents across all deployments):
# VICTOR, AXIS, NOVA, CODEX, ARIES, NEXUS, ORACLE, AURUM, JANUS, LUMEN, ARBITER
    

05 :: frameworks

10 Frameworks Behind Every Deployment

VICTOR is the runtime. These frameworks run inside it.

VICTOR

AI operations platform

Multi-agent autonomous ops. Built 2026. The runtime all other frameworks run inside.

ARBITER

governance + legal

Texas SHIELD Act compliance, MSA/NDA templates, contract review automation.

AURUM

financial model

Revenue projections, ROI modeling, tier economics. Knows what our margins actually are.

CODEX

SOPs + playbooks

Operational bible. Deployment procedures. Onboarding checklists. Runbooks as code.

CHALLENGER

QA + security review

Finds deviations from spec. Runs compliance passes. Challenges plans before they ship.

OPUS

deployment planning

Timelines, resource allocation, post-deploy verification. Owns the rollout calendar.

NOVA

lead pipeline

WordPress mu-plugin. Captures and tracks leads. Feeds CRM automatically.

NEXUS

analytics + reporting

WP-CLI integrated business metrics. Real numbers, not dashboards that feel good.

ORACLE

command dashboard

React / Next.js live ops center. FORTRESS and VANGUARD clients see every VICTOR action in real time.

OpenClaw

agent runtime

Tool integration, agent state, persistence. The layer between models and the real world.

06 :: customer_access

How Customers Consume VICTOR

VICTOR runs on PCA's infrastructure. Customers get access through their tier.

# tier access matrix
GUARDIAN_MICRO: $99/mo
  victor_delivery: true  # automated delivery
  oracle_dashboard: false # no direct access

NEXUS_PROTECT: $45/user/mo
  victor_delivery: true
  oracle_dashboard: false

FORTRESS: $2,500/mo flat
  victor_delivery: true
  oracle_dashboard: true  # full audit trail
  users: 10-25

VANGUARD: custom
  victor_delivery: true
  oracle_dashboard: true
  scope: multi-entity
        

oracle://fortress-client/warroom

$ oracle --watch live

[PLAN-ORCH] task assigned: patch cycle Q2

[TASK-EXEC] patching 14 endpoints... done

[VAL-LEAD] validated: 14/14 success

[PLAN-GUARD] flagged: endpoint 7 offline

[PLAN-GUARD] escalating to daniel...

every action logged with timestamp + agent id

> audit trail: 100% complete

07 :: risk_reversal

No Lock-In. No Gotchas.

VICTOR comes with every managed IT tier. Not a premium add-on.

commitment

Month-to-month contracts

All tiers except VANGUARD are month-to-month. Cancel with 30 days notice. No penalty.

transparency

Every action logged

FORTRESS and VANGUARD clients get ORACLE dashboard access. Every VICTOR action has a timestamp, agent ID, and outcome.

escalation

PLAN-GUARD + Daniel

When VICTOR is uncertain, it escalates to Daniel before acting. The escape hatch is built into the platform.

08 :: honest_faq

Honest FAQ

Do I have to use VICTOR if I just want managed IT?

No. VICTOR runs silently on all flat-rate tiers — faster patching, 24/7 monitoring, auto-resolved alerts. You don't have to interact with it. GUARDIAN MICRO gets VICTOR-automated delivery; FORTRESS and VANGUARD get full ORACLE dashboard access.

Where does the data go?

Your data stays in your tenant. VICTOR runs in your Microsoft 365 environment or on AEGIS hardware in your office. PostgreSQL row-level security enforces isolation at the database layer — cross-tenant reads are impossible at the DB level. Your data never leaves your tenant except on your explicit instruction.

What if VICTOR makes a wrong call?

All agent actions are logged with timestamp and agent ID. PLAN-GUARD validates tasks before TASK-EXEC fires — when certainty falls below threshold, it escalates to Daniel instead of proceeding. ORACLE (FORTRESS/VANGUARD) shows every action; any tier can request a log export.

Is VICTOR "production-hardened"?

VICTOR is running in production at PCA and pilot tenants. The operational expertise it codifies is 9 years deep — 130+ customer environments since 2017. It runs alongside human oversight, not instead of it.

What happens when VICTOR fails?

Every agent has a PLAN-GUARD validator. When a task isn't certain-to-succeed, it escalates to Daniel. Better to hand off than to automate a mistake at scale.

Can I see VICTOR run my account?

Yes. FORTRESS and VANGUARD clients get ORACLE dashboard access to see every VICTOR action in real time. Full audit trail on every agent decision.

Is my data isolated from other clients?

Yes. PostgreSQL Row-Level Security is enforced at the database role level. Cross-tenant reads are impossible at the DB layer — not just at the application layer. Plus per-tenant Docker containers.

Do you pool my data into AI training models?

No. We use AI APIs with no-training-on-data commitments. Your data goes to the model per-query and is discarded after the response. No data is shared across tenants or used to improve the underlying models.

The VICTOR Platform