Deterministic decisions
No model chooses what to deploy or when. Rules, scope and safeguards remain readable.
Security and trust
Decisions you can inspect. Data movement you can control.
Parallax operates close to sensitive infrastructure. Its security posture begins with explicit authority, local-first data and evidence that preserves provenance.
Local by default
Operations, telemetry and reports remain inside the deployment unless an operator configures an export.
Explicit changes
Deployment plans declare the intended action and can require approval by a second identity.
Traceable action
Automatic decisions, refusals and human actions keep separate, attributable records.
Protected credentials
Recoverable secrets are encrypted at rest; deployment credentials can use external Vault custody.
Verifiable evidence
Evidence archives include a SHA-256 manifest and measured outcomes can reference their source events.
Control model
The operator remains the authority.
Automation is bounded by rules of engagement, capability scope and cascade limits. A rejected action is recorded with a typed reason instead of silently disappearing.
PROPOSERule matches an event
CHECKRoE + scope + cascade
APPROVEHuman gate when required
RECORDAction or rejection
Current boundaries
Claims tied to what has been validated.
Parallax distinguishes implemented contracts and automated tests from external infrastructure validation.
Validated in the product
Authorisation defaults, OIDC validation, encrypted storage, audit integrity, deployment planning, API scopes, idempotency and evidence manifests.
Pilot gate remains
Representative external validation for multi-DC Active Directory or WEC, production Vault policies and real SMB shares.
Declared architecture limit
The current supported Community-style deployment is a single process. Enterprise scale and HA are separate capabilities.
Security review
What we can discuss with your team.
Where does telemetry live?
Local persistence is the default. Optional exports send selected records only to configured HTTPS destinations.
Does an LLM control deployments?
No. BUDA can use an LLM to generate content, but deployment decisions remain deterministic and rule-controlled.
How is access authorised?
Endpoints use a deny-by-default allowlist. Community-style access includes fixed roles and teams; Enterprise extends the policy model.
How do we report a vulnerability?
Contact BASE4 Security through the evaluation form and mark the message as a security disclosure. We will move the conversation to an appropriate private channel.
Evaluation
Start the review