| Name | Accessed | Updated |
|---|
Each environment is a set of runtime variables for an application.
You can create separate environments for dev/test/production and for different applications.
# Access these environments using the client
> npm install -g keys-cli
# Run command and select environment
> keys [your command] # vars loaded
# Alternatively, pass the environment name
> keys -e [env-name] [your command]
# You can create environments from the shell, too
> cat .env | keys --import -e "My Env"
> echo 'A=1\nB=2' | keys -i -e "Anotha One"
There are other ways to access environments from within your code;
client libraries are available for many platforms.
Click variable names and values to edit. Use the keys client to load this
environment for your software at runtime.
| Name | Environment | Enabled | Created | Accessed |
|---|
| Name |
|---|
Modified
Access tokens provide asynchronous access
Other Actions
| Name | 2FA | Last Login |
|---|
alternate_email
| Name | Accessed | Updated | Access |
|---|
| Name | Environment | Enabled | Created | Accessed |
|---|
Access Tokens are shared alternate passwords for a single environment. They can be supplied as a command line argument to the client, so you don't have to enter credentials interactively to fetch environments.
Use of access tokens is less secure than other runtime authentication methods. However, some additional measures are taken to prevent unauthorized use.
None
- Delete My Account
Solo
- All Features for a Single Developer
- Free
Teams
- Invite Users to Your Organization
- Create Teams & Manage Access
- Point-in-Time Recovery
- $5/user/month
Self-Hosted
- Install on Your Network
- Multi-Organization
- Full Control
- Contract Required
| Organization Name | ||
| Plan |
