Skip to content
Zelyq/Platform/SECURITY & CONTROL
SECURITY & CONTROL

Understand the boundaries.Choose how you run.

Security depends on the product controls and the environment you operate. Zelyq makes its source and runtime model available for inspection.

Credentials and references

Vault encrypts stored secrets and lets apps, settings, pipelines, and deployments reference them. Protected secrets and scoped service keys help limit who can use them.

Team access and activity

Viewer, editor, admin, and owner roles apply across modules. Activity records supported sensitive actions, including secret reveals and changes.

Execution boundaries

Local runtime mode is for trusted use and is not a sandbox. Container execution separates project workloads; outbound network restrictions require operator configuration.

Model data flow

The configured model receives the context the agent sends, including files and command output it reads. Self-hosting Zelyq does not make a remote model provider local.

OPERATING RESPONSIBILITIES

Control needs
configuration.

Review the threat model for the version you deploy. Choose the runtime and access rules for your users and workloads.

  1. 01Decide what may be sent to your model provider
  2. 02Isolate untrusted project execution
  3. 03Configure HTTPS, access, and outbound networking
  4. 04Keep backups, updates, and recovery procedures