AXERA
Segment

Least-privilege segmentation, written from real traffic.

Axera Segment writes the policy your workloads actually need, from what they actually do. Then it gives you the lifecycle, governance and mesh support to run that policy in production without outages.

Schematic of a policy diff: allowed sources and ports added, an over-broad rule removedpolicy / payments-db v3 → v4 kind: NetworkPolicy spec:- ingress: [ from: any ]+ ingress:+ from: ns/payments+ ports: 5432/TCP policyTypes: [Ingress]
Policy as a reviewable change: what gets allowed, what gets removed, who approved it.
What you get

Policy you can trust in production.

  • Generate policy from observed traffic

    Axera writes least-privilege Kubernetes NetworkPolicy (the cluster's built-in firewall rules) from real connections. No hand-written YAML, no guessing at ports.

  • Roll back a bad policy in one click

    Every policy is drafted, deployed and versioned. Deleted policies are kept for a retention window, so a removal is recoverable.

  • Write rules the way a firewall team thinks

    Source, destination, port, protocol. Axera compiles the rule into correct NetworkPolicy, so the network team never touches YAML.

  • Cover the service mesh from the same map

    Generate Istio AuthorizationPolicy for ambient and sidecar meshes alongside network-layer policy. One graph, both layers.

  • Catch a bad policy in the pull request

    Scan Git repositories and recommend policy before the workload goes live, so segmentation is a code review, not a post-incident scramble.

  • Govern many clusters from one place

    Approval gates, multi-cluster fan-out and GitOps delivery keep enforcement auditable and consistent.

Lifecycle

Every policy has a history you can undo.

  1. Draft

    Axera proposes policy from observed traffic. Edit it, or write firewall-style rules and let Axera compile them.

  2. Deploy

    Ship on approval, to one cluster or a group, directly or through Git. Nothing is enforced until you say so.

  3. Version

    Every change is recorded with who made it and when, so auditors get a history and engineers get a diff.

  4. Roll back

    Production complains? Restore the previous version in one click. Soft-deleted policies stay recoverable for the retention window.

The promise

Least-privilege policy written from what your workloads actually do, deployed on your approval and rolled back in one click.

Next: NDR catches what policy lets through

See Axera on your own clusters.

A 20-minute lab walkthrough with an engineer, or a proof of concept on clusters you control. The PoC runs entirely inside your perimeter.