<!-- Generated from the canonical HTML page. Do not edit separately. -->
# Move from Argo CD or Flux - Ankra Use Cases

Canonical: https://ankra.ai/use-cases/migrate-from-argocd-flux

Move delivery into Ankra’s native GitOps engine while keeping standard Helm releases and Kubernetes configuration.

[All use cases](https://ankra.ai/use-cases)

Move from Argo CD or Flux

# Keep Git at the centre. Bring operations around it.

Move delivery into Ankra’s native GitOps engine while keeping standard Helm releases and Kubernetes configuration.

[Start with Ankra](https://platform.ankra.app/auth/signup)  [Read the guide](https://docs.ankra.ai/concepts/deployment-engines)

For teams maintaining a gitops toolchain

The work to take off your team

## The delivery controller is one piece. Your team still needs the operational platform around it.

Ankra combines configuration, reconciliation, cluster visibility, application delivery and agents. Plan a staged migration of add-ons and manifests, inspect ownership and verify the result before retiring the old controller.

With Ankra

### GitOps connected to the rest of application operations.

Inventory what runs  Prepare Ankra stacks  Migrate in stages  Verify and retire

A practical path

## How this works with Ankra.

1. 01

  ### Inventory what runs

  Identify the applications, Helm releases, manifests and controller-specific behaviour in use.
2. 02

  ### Prepare Ankra stacks

  Express the desired state, values and dependencies in the connected GitOps repository.
3. 03

  ### Migrate in stages

  Review release adoption and resource ownership one part of the platform at a time.
4. 04

  ### Verify and retire

  Check the running workloads and sync behaviour before removing the previous controller.

 [Follow the product guide](https://docs.ankra.ai/concepts/deployment-engines)

The platform behind the workflow

## The pieces, already connected.

[### Native GitOps Keep configuration in your repository and let Ankra reconcile it to the cluster. See the intended and running state together.](https://ankra.ai/features#gitops)

[### Stacks & visual builder Compose applications, Helm add-ons and manifests into a platform, with variables and dependency order.](https://ankra.ai/features#stacks)

[### Metrics, logs & health Understand the application and the cluster underneath it, with resource views, metrics and logging integrations.](https://ankra.ai/features#observability)

What comes next?

## Keep building from here.

[Grow & move ### Multi-cloud & private infrastructure Use one operational platform across public clouds, managed Kubernetes and private servers.](https://ankra.ai/use-cases/multi-cloud)

[Operate & protect ### Self-service with control Give developers and agents useful access while retaining ownership of permissions, configuration and changes.](https://ankra.ai/use-cases/team-governance)

[Operate & protect ### An AI platform engineer Agents that read live cluster state, fix what breaks and wait for your approval. Use Ankra's AI team, or connect Claude, Cursor or your own agent over MCP.](https://ankra.ai/use-cases/ai-platform-engineer)

Your next chapter

## You built it.
*Let’s get it live.*

Give your application a path to production.
 Give your team a simpler way to run it.

[Get your app live](https://platform.ankra.app/auth/signup)  [Try a playground](https://ankra.ai/playground)

First 30 vCPU of platform usage included.
Try it without a card; a card unlocks full access and €59 of credit.

From something you built
to something people use.

- Deploy from your repository
- Run on infrastructure you choose
- Operate with your team and agents