Keyrua

Development teams and agencies typically pass around .env files to configure applications across local, test, staging and production environments. This makes it hard to control who can see sensitive values like database URLs and API keys, and there is no shared record of who changed what or who has access to which client project. Teams managing multiple applications or multiple clients end up chasing scattered configuration files with no central access model, change history, or role separation between admins and editors.

Keyrua provides a dashboard and CLI where teams organize environment variables into projects, each with five fixed environments (local, test, development, staging, production). Sensitive values are encrypted with Google Cloud KMS before storage and decrypted only for authorized reveal or export requests. Project access is controlled per project through Admin and Editor roles, invited from an organization's members list, and the system logs secret activity and project access history (though not secret values read or prior values). Users can import an existing .env file, export one back out, or use the public npm CLI (keyrua run, init, login) to inject variables directly into a process without writing a file to disk.