SECURE / Vault

One place for credentials.Connected to your work.

Keep secrets encrypted, reference them across the workspace, and give other systems access through scoped service keys.

Vault showing protected secrets with version labels and hidden values — Secret names, protection and version history remain visible while values stay hidden.View original capture ↗

BUILT FOR THE WORK

What you can do with Vault.

Reference instead of repeating

Use a Vault entry in app variables, model settings, pipeline steps, or deployment environments. Change the stored secret without editing each reference.

Keep a change history

See previous values and restore a version. Reveals and changes are recorded in the team’s Activity.

Protect live credentials

Mark sensitive keys as Protected. Admin and owner permissions control their use and management.

Use Vault outside Zelyq

Create service keys with permissions, name patterns, optional IP restrictions, and expiry. The API and CLI connect your other systems.

A CLEAR PATH THROUGH

From setup
to your next step.

Follow the guide for configuration details and the complete workflow.

Open the documentation

01Add a credential or import an existing .env
02Reference its name from an app or pipeline
03Scope access for an external system
04Review versions, usage and activity

A SMALL EXAMPLE

A pipeline references a secret by name

This example uses a secret already stored in Vault. The value is resolved when the step runs.

Vault reference

env:
  DATABASE_URL: vault://DATABASE_URL

stages:
  - name: Test
    steps:
      - run: npm test

BEFORE YOU BEGIN

A few useful details.

Is Vault required for every credential?+

No. Supported credential fields can accept a value directly or a reference from Vault. Vault is useful for sharing, versioning, and external access.

What happens when a secret changes?+

References use the new value when it is next resolved. App variables take the change on restart; running services need the appropriate restart or deployment.

Can a browser application keep a secret?+

Anything sent to a browser is public. Credentials belong in server-side code; Zelyq does not send app secret variables into a plain React frontend.

MAKE IT YOUR WORKSPACE

Start with the work in front of you.

Run Zelyq yourself and connect the parts your team needs.

Get started