Your Secrets, Secured.

Organization and project roles are separate. The organization owner has full control of the org and implicit owner access to every project in it, even when someone else is the project owner. Project owners manage day-to-day project settings and membership. Admins can invite and manage members and, at the project level, manage secrets, but they can't change organization settings. Members can access data for the organization and its projects, but can't modify settings, secrets, or manage other users.

Service tokens let you access secrets programmatically, without a user session. This allows you to automate secret management in your applications and CI/CD pipelines. Each token is scoped to one or more environments (Development, Staging, or Production) and can optionally be set to expire after a chosen number of days.

Audit logs record sensitive actions across your organization, like secret changes, role updates, and service token creation, capturing who did it, when, and relevant metadata. They're visible to the organization Owner and Admins, providing a clear operational history for security and compliance purposes.

The WindKeep CLI allows you to interact with secrets and projects directly from your terminal, eliminating the need for hardcoded .env files and making it easy to integrate secrets into scripts and automated workflows. Whether you're retrieving secrets, updating them, or managing project/organizations, the CLI provides a secure and developer-friendly experience.