<!-- Generated from the canonical HTML page. Do not edit separately. -->
# Operate an edge fleet - Ankra Use Cases

Canonical: https://ankra.ai/use-cases/edge-computing

Manage Kubernetes at remote sites with shared stacks, site-specific inputs and central operational visibility.

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

Operate an edge fleet

# Many locations. A platform you can repeat.

Manage Kubernetes at remote sites with shared stacks, site-specific inputs and central operational visibility.

[Start with Ankra](https://platform.ankra.app/auth/signup)  [Read the guide](https://docs.ankra.ai/guides/import-cluster)

For teams running software at remote or private sites

The work to take off your team

## Each new site should not become a new collection of scripts and manual fixes.

Connect the clusters you run at stores, factories, offices or other remote locations. Reuse a platform profile while keeping local domains, credentials and resource settings specific to each site.

With Ankra

### A consistent fleet with room for each location’s needs.

Connect the sites  Define the shared stack  Bind local inputs  Operate from one place

A practical path

## How this works with Ankra.

1. 01

  ### Connect the sites

  Import each Kubernetes cluster through Ankra’s outbound-connected agent.
2. 02

  ### Define the shared stack

  Version the add-ons, manifests and application configuration that each location needs.
3. 03

  ### Bind local inputs

  Apply a profile with site-specific variables, sizing and secret references.
4. 04

  ### Operate from one place

  Inspect cluster health, route alerts and investigate issues with the permissions your team grants.

 [Follow the product guide](https://docs.ankra.ai/guides/import-cluster)

The platform behind the workflow

## The pieces, already connected.

[### Clusters on your infrastructure Import existing Kubernetes or provision a cluster in your cloud account, on private servers or with a managed provider.](https://ankra.ai/features#clusters)

[### Reusable stack profiles Turn a working stack into a versioned template. Apply it to another cluster with the right inputs for that environment.](https://ankra.ai/features#profiles)

[### Alerts & notification routing Send the right platform events to the right team, filtered by cluster, severity and notification kind.](https://ankra.ai/features#alerts)

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 ### Investigate production incidents Give your team and its agents the logs, events and resource state needed to investigate a running application.](https://ankra.ai/use-cases/incident-response)

[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)

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