Enterprise Edition

Deploy A-Packets On-Premise

Private PCAP analytics for teams that cannot send sensitive PCAPs to third-party SaaS. Join the waiting list and share your deployment requirements and traffic profile.

Kubernetes (k8s) Native

PCAP stays inside your environment
Air-gapped and isolated networks
Search, dashboards, and exports on your side
Share Deployment Requirements

No newsletter. No generic sales drip. We use this form to follow up when availability changes.

Why teams ask for this Enterprise Workflow Deployment Signals

Benefits

Why teams ask for on-prem

The main constraint is usually not feature count. It is where packet captures, credentials, and evidence are allowed to go.

Keep PCAP inside your boundary

Use on-prem when packet captures, credentials, or incident evidence cannot leave your infrastructure.

Built for isolated networks

Air-gapped and tightly controlled environments need local analysis, not a SaaS dependency chain.

Reduce analyst busywork

Search, dashboards, and exports should speed up DFIR and reporting without another manual workflow.

Air-gapped friendly
Helm-based deployment
LDAP or local auth
API and JSON export

Enterprise workflow

The workflow is designed for teams that need private PCAP analysis inside their own environment.

1

Ingest PCAP locally

Upload PCAP or PCAPng directly, or push captures from internal workflows with apackets upload.

2

Analyze and store in your infra

Decoded traffic, metadata, and artifacts stay on infrastructure you control, with output available as clean JSON.

3

Search and inspect faster

Analysts need dashboards, drill-down views, and search that reduce triage time during a security incident.

4

Export findings and evidence

DFIR and compliance teams still need exports, reporting, and handoff artifacts without rebuilding the data pipeline manually.

Deployment signals we are collecting now

These are the constraints that affect packaging, rollout, and pricing for on-prem deployments.

Helm-based deployment for Kubernetes environments

MinIO or S3-compatible object storage for PCAP retention

LDAP or local auth, depending on internal policy

Expected monthly PCAP volume helps us size packaging and pricing

REST API and exports for existing IR workflows

Share your on-prem requirements

We use these responses to understand deployment constraints, estimate traffic tiers, and build the pricing model.

No spam. No newsletter. We only use this to contact you about on-prem packaging, pricing, and availability. Your answers stay internal and help us estimate deployment tiers.