Encrypted credentials
A dedicated place for sensitive project values such as service tokens and API keys.
Share credentials with the people who need them
Byblos AI Secrets Manager is where founders and technical leads keep project API keys, database passwords and service tokens, encrypted. Grant access one person at a time; values stay hidden until opened, and every reveal is recorded. Give a contractor the test key and not the production one, without pasting either into a chat.
Included on Launch, Grow and Byblos AI Pro. Secret values are excluded from AI assistants and Workspace MCP.
Launch: $39 a month · Beta · self-serve checkout
Last updated
How Secrets Manager works
Step 1
Store the credential
Name the secret and optionally label its environment. Keep descriptions useful without putting sensitive values into them.
Step 2
Grant individual access
Choose the people who need the value. Sharing a project alone does not grant access to its secrets.
Step 3
Review access activity
Values are hidden by default, and reveals are recorded so credential access can be reviewed.
Who can open a secret
Who can open a secret in Byblos AI Secrets Manager
A secret value is stored encrypted, only the people granted access can open it, every reveal is recorded, and AI assistants, agents, automations and Workspace MCP are excluded.
What you work with
Per-person sharing
Grant access to individual people rather than making a credential visible to the whole project.
Reveal records
Recorded value access supports review of who opened a credential.
Secrets Manager questions
Can I keep test and production values apart?
Yes. The same secret name can be stored once per environment, such as PROD, TEST or STAGING, and each copy is a separate secret with its own value and access list. You can give a developer the test credential and not the production one, and a test value is never copied into production automatically.
Can an AI assistant read my secret values?
No. Secret values are excluded from Byblos AI assistants, agents and automations, and the Secrets Manager is excluded from Workspace MCP. Use the dedicated secrets workflow to share a credential with an authorized person. Do not paste secret values into chat prompts, document descriptions or other general project material.
Do project administrators automatically see the values?
No. A person must be explicitly granted access to a secret’s value, and opening it is recorded. Project membership or an administrative role does not by itself reveal the credential. Assign access to the specific people who need it, and review that access as responsibilities change.
Continue exploring
Choose your next step
Launch: $39 a month · Beta · self-serve checkout