Security Model
Security here means defaults you can reason about, not a list of logos. This page describes the posture ProxyScout designs to and is honest about what is still in preview.
Local-first where possible
Where the work allows, execution and data stay inside your boundary rather than routing through someone else's cloud. The public diagnostic tools run in your browser and do not require an account.
Least-privilege permissions
Workflows grant each step only the reads and writes it needs, declared up front in ProxyLang. Broad, default access is the thing this is meant to avoid.
Provider-direct execution
When a workflow calls a model provider, it does so directly with your keys and configuration. We aim to sit in the path as little as possible.
Minimal retention
The goal is to keep what is needed to operate and audit a system, and no more. Retention should be a deliberate choice, not an accident of logging everything forever.
Auditability by design
Workflows can log their decisions so you can reconstruct what happened. This is a first-class goal of the runtime rather than an add-on — though, as noted below, coverage is still expanding.
What this is not — yet
This is a description of design intent and current behavior, not a compliance certification or an audited guarantee. We do not claim ProxyCore is "tamper-proof" or fully isolated for multi-tenant use today — that work is in progress. If you have a specific security or compliance requirement, tell us and we will be precise about what holds today.