Deploy deception through the workflow your team already operates.

One NeroPot runtime, five software deployment methods.

Move from configuration to a running sensor with generated workflows for Linux hosts and Kubernetes clusters.

Start a Free Trial Explore Templates
Deployment panelDeploy NeroPot
Standalone Compose systemd Kubernetes Helm
Selected methodHelm release

Generated prerequisites and deployment-specific install command.

amd64 / arm64
# Add the NeroSwarm chart repositoryhelm repo add neroswarm   https://neroswarm.github.io/chartshelm repo update neroswarm
Deployment methods

Match delivery to operational ownership.

Each method deploys the same NeroPot capability. The difference is how the target environment is managed.

Standalone logo01
Fast host rollout

Standalone

Run the generated installation command on a compatible Linux host for the shortest path from configuration to a running NeroPot.

Generated install command
Docker Compose logo02
Container operations

Docker Compose

Use a generated Compose definition when your team prefers an explicit, portable container lifecycle.

Compose configuration
systemd logo03
Persistent Linux service

systemd

Install the container as a managed Linux service with generated environment and unit configuration.

Environment and service unit
Kubernetes logo04
Manifest-driven clusters

Kubernetes

Apply generated Kubernetes resources when platform teams manage deployments directly with cluster manifests.

Generated manifests
Helm logo05
Repeatable cluster releases

Helm

Install and manage NeroPot as a Helm release using the public NeroSwarm chart and deployment-specific commands.

Chart and release commands
Operational fit

Choose based on lifecycle, not fashion.

A fast pilot and a production cluster do not need the same delivery mechanism. Match the generated output to the team that owns updates and recovery.

Environment needRecommendedOwnerLifecycle
One Linux hostStandaloneSecurity or infrastructureGenerated command
Explicit container configurationDocker ComposeContainer operationsCompose workflow
OS-managed servicesystemdLinux operationssystemctl
Existing Kubernetes workflowKubernetesPlatform engineeringkubectl
Versioned cluster releaseHelmPlatform engineeringhelm upgrade
charts/neropot PUBLIC CHART
# Add the chart repository
helm repo add neroswarm \
  https://neroswarm.github.io/charts \
  --force-update

helm repo update neroswarm

# Continue with the authenticated commands
# generated by the deployment panel.
Helm deployment

A first-class release workflow for Kubernetes.

The public NeroSwarm chart provides a familiar installation and upgrade path. The console supplies deployment-specific prerequisites without embedding registry credentials or licenses in public files.

Versioned releases Standard Helm lifecycle commands
Multi-architecture amd64 and arm64 images
Runtime requirements Generated with the required networking and capabilities
Before deployment

Prepare the target, then generate the workflow.

Host readiness

Use a supported Linux host with Docker available and keep the selected honeypot ports free.

Network reachability

Allow access to the NeroSwarm API and registry while exposing only the intended decoy services.

Cluster permissions

Kubernetes deployments use host networking and the capabilities required to emulate configured services.

Physical deployment

Extend deception to branches and isolated networks.

Hardware NeroPot is a separate sensor path for locations where maintaining a host or cluster workload is not the right operational choice.

Discuss Hardware Deployment
Deployment flow

From configuration to monitored decoy in four steps.

  1. 01

    Configure

    Choose the template or manual service surface and define alert recipients.

  2. 02

    Generate

    Open the deployment panel and select the method that fits the target.

  3. 03

    Launch

    Run the generated command or apply the generated cluster resources.

  4. 04

    Operate

    Monitor status and interactions centrally from the NeroSwarm console.

Ready when your environment is

Configure once. Deploy through the workflow your team trusts.

Choose the operational model that fits the target without changing the deception capability.

Start Deploying