Agentic Driven Compute Solutions
Sign In
Security

Per-system kill switches and access rules.

Firewall is VP3's per-system access-control surface. Block external IPs, throttle abusive nodes, restrict which subdomains can talk to which apps, force MFA on specific surfaces. Defaults are sensible; tighten anything.

Per-system access-control — IP blocks, rate limits, inter-app rules, MFA requirements.
What it does

Firewall at a glance.

Per-system rules
Apply rules to specific subdomains, specific apps, or globally. 'Block this IP from all my domains' or 'Throttle this node to 10 req/min on the storefront' both work.
Energy-aware quarantine
The energy grid auto-quarantines abusive nodes (excessive 5xx, excessive auth failures). Firewall surfaces the quarantines so you can review + permanent-ban if warranted.
MFA enforcement
Require MFA on admin-style surfaces (admin console, payments config, key management). Per-system so non-sensitive ops stay frictionless.
Default-on
Sensible defaults out of the box — rate limits, CORS, CSRF, login throttling. You only see Firewall when you want to tighten something.

Add Firewall to your agent.

Every VP3 plan unlocks the full c:// drive catalog. Pick a plan, install the home server, flip the app on.

Choose Your Plan