Changelog

The Phase Console now natively integrates with Vercel, allowing you to sync secrets and environment variables to your Vercel projects. You can sync secrets to specific environments (Production, Preview, Development) or all environments at once.

Access control across the Phase platform has been reworked from the ground up to be more granular and completely customizable. We've added a whole new modular permissions framework, with 3 managed roles and full support for custom roles.

We've shipped several UX updates this month to streamline workflows around the Console and reduce developer fritch including a new command palette, updated UX for editing secrets and a more detailed apps overview screen.

We're excited to announce the release of native Golang and Python SDKs for Phase. These SDKs allow you to programmatically manage your application secrets with end-to-end encryption straight from your code.

Custom Environment support is now live! You can create, delete, rename and reorder environments to match your team's preferred workflow and tailor your own secret management setup.

You can now sync secrets and environment variables to your Projects and Services on Railway. We've also added support for managing personal overrides from the Phase CLI, along with bug fixes and optimizations for self-hosted users.

The Phase Console now natively integrates with GitLab CI, allowing you to sync secrets and variables to your GitLab CI pipelines and jobs. You can sync secrets to both groups and projects. We've also added the ability to use self-hosted GitLab instances to authenticate with the Phase Console.

The Phase Console now natively integrates with Hashicorp Nomad, allowing you to sync secrets to Nomad variables and use them with your Nomad Jobs. We've also shipped several quality of life improvements, new features and bugfixes to the Console and API.

You can now manage your application secrets programmatically via a public REST API. The API is availalable on all pricing tiers for both Phase Cloud and Phase Self-hosted users, and allows you to create, fetch, update and delete secrets.

The Console now automatically detects boolean values and adds a toggle switch to easily flip between true and false states.

You can now securely share secrets with users outside of your team with Phase Console's Secret Sharing feature: Lockbox. Secrets shared with Lockbox are encrypted with zero-trust encryption, and can only be accessed and views using the link. You can set a custom expiry policy for the link based on either number of views or a fixed expiry time.

We've revamped the UX for unlocking the user keyring with your sudo password to be significantly less disruptive to your workflow. We've also added the option to skip entering your password entirely on trusted browsers and devices.

Secrets can now be managed within folders, and will keep track of the path that they are stored under. This makes it much easier to use Phase for monorepo projects or multi-tennant use-cases. All existing secrets are given the root / path by default.

The Phase Console now has native integration with Hashicorp Vault, allowing you to keep your existing Vault setup in-place while using Phase for development or staging environments. The integration works for self-hosted instances of Vault as well as Hashicorp Cloud Platform.

The Phase Console now has native integration with GitHub Actions, allowing you to use Phase to inject secrets into your Workflows. Phase will make sure your CI runs, build pipelines and test environments use up-to-date secrets without any manual intervention required.

The Phase Console now has native integration with AWS Secrets Manager, allowing you to use Phase as a single source of truth for all secrets in your AWS Stack.

Third party integrations are now live in the Phase Console. This allows native integrations with a host of third party providers to keep your secrets automatically in-sync.

You can now override the value of Secret with a Personal Secret. This lets you supply a one-off value for a given secret that is specific to your local development environment, without having to modify the secret for the rest of your team.

Running phase auth in the CLI now opens up a new tab in your default web browser and redirects you to the Phase Console for authentication. This is a seamless process that allows users to authenticate with their existing accounts without needing to manually generate, copy and paste personal access tokens.