> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enkryptify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Syncs overview

> Push secrets from Enkryptify to your cloud providers and CI/CD platforms.

## What are syncs?

Enkryptify syncs keep your secrets up to date across platforms by propagating them from Enkryptify to external providers. Syncs are currently one-way: changes in Enkryptify are pushed to the destination provider, never the other way around. This ensures a single source of truth and prevents accidental overwrites.

<Note>
  Only admins can create and manage syncs. Syncs always use shared secret
  values, [personal overrides](/platform/personal-overrides) are not synced.
</Note>

### How do syncs work?

1. You create a sync in the Enkryptify dashboard.
2. You authenticate with the destination provider and select scope (different for each provider).
3. You map Enkryptify environments (e.g., `production`, `staging`) to provider environments.
4. Enkryptify pushes secrets on creation, update or manual re-run.

### Environment mapping

When setting up a sync, you map each Enkryptify environment to a corresponding environment on the destination provider. For example, your Enkryptify "production" environment might map to Vercel's "Production" environment or a specific GitHub Actions environment.

Only mapped environments are synced, unmapped environments are ignored. If you need to sync multiple environments, you can create multiple syncs.

### Re-running syncs

You can manually re-run a sync from the project's syncs page to force-push all current secret values to the provider. This is useful after bulk changes or to recover from a provider-side issue.

## Supported integrations

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/sync/native/github">
    Sync to GitHub Actions secrets and environments.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/sync/native/gitlab">
    Sync to GitLab CI/CD variables.
  </Card>

  <Card title="Bitbucket" icon="bitbucket" href="/sync/native/bitbucket">
    Sync to Bitbucket Pipeline Variables.
  </Card>

  <Card title="Vercel" icon="triangle" href="/sync/native/vercel">
    Sync to Vercel project environment variables.
  </Card>

  <Card title="AWS Secrets Manager" icon="aws" href="/sync/native/aws-secrets-manager">
    Sync to AWS Secrets Manager.
  </Card>

  <Card title="AWS Amplify" icon="aws" href="/sync/native/aws-amplify">
    Sync to AWS Amplify environment variables.
  </Card>

  <Card title="Azure Key Vault" icon="key-round" href="/sync/native/azure-key-vault">
    Sync to Azure Key Vault secrets.
  </Card>

  <Card title="GCP Secret Manager" icon="google" href="/sync/native/gcp">
    Sync to Google Cloud Secret Manager.
  </Card>

  <Card title="1Password" icon="key-round" href="/sync/native/1password">
    Sync to 1Password vault items or Secure Notes.
  </Card>

  <Card title="Fly.io" icon="fly" href="/sync/native/flyio">
    Sync to Fly.io app secrets.
  </Card>

  <Card title="Coolify" icon="server" href="/sync/native/coolify">
    Sync to Coolify application and service environment variables.
  </Card>
</CardGroup>

## Framework guides

Enkryptify is framework- and language-agnostic, but we offer framework-specific guides for popular stacks. If you don't see your stack here, you can still use the [CLI](/cli/quickstart) to inject secrets into your application.