Pricing

Pricing should be easy to understand before data starts moving.

PumaMesh uses a node-based model instead of charging by every gigabyte, connection, or user. Buyers can plan around the systems they deploy, not the volume they hope to move.

That keeps the pricing story aligned with the product story: one platform for secure modern data movement, not a meter attached to every workflow.

How Pricing Works

Move more data without creating a new billing event.

The model is intentionally simple: count the PumaMesh systems you run and the roles they play. The movement across those systems is not separately metered.

Not Charged

Data transferred

Move as much data as your link supports — throughput is not a line item.

Not Charged

Number of connections

Open as many peer paths as your topology needs. No per-connection meter.

Not Charged

Number of users

Operators, analysts, and end users all work under a single node footprint.

No per-GB fees. No connector licensing. No hidden scaling penalties.

What Is a Node

What counts as a node

A PumaMesh node is any system running the PumaMesh runtime. Each node type is licensed based on its role, scale, and operational requirements.

Agent

Runs on endpoints, edge systems, and data sources.

Relay

Optimizes routing and movement across networks and trust boundaries.

Hub

Coordinates discovery, policy, and orchestration across the mesh.

Why This Model Exists

Why we don't charge for data movement

Usage-based pricing makes teams ration the exact workflows the platform is supposed to enable. PumaMesh licenses the runtime instead of the activity, so growth in transfer volume does not create a new pricing problem.

Your architecture should define your system — not your pricing model.

Deployment Tiers

Start where you are. Scale as needed.

Every tier runs the same binary. What changes is the scope of topology, architecture support, and assurance features each environment requires.

Starter Deployment

For pilots and controlled environments

Limited node count
Core Agent deployment
Secure data movement + encryption
Basic policy enforcement

Best for: initial validation, small environments, innovation teams.

Enterprise Deployment

For production environments

Scaled node deployment
Full mesh architecture (Agent + Relay + Hub)
Advanced policy enforcement (ABAC)
Multi-environment operation

Best for: enterprise data workflows, multi-site deployments, secure partner exchange.

Mission / Federal Deployment

For high-assurance environments

Distributed and disconnected deployments
Support for constrained networks
Post-quantum cryptography options
Custom architecture guidance

Best for: defense and federal, edge and tactical systems, sensitive and regulated environments.

What You Replace

Replace usage-based pricing with a fixed platform model

PumaMesh replaces multiple systems that typically charge based on usage. With PumaMesh, those functions are built into the platform — without incremental cost per operation.

File Transfer

Per-GB transfer fees

MFT platforms that charge by data volume moved.

Encryption

Per-user / per-dataset fees

Encryption tools billed by user count or data set.

DSPM

Per-scan / per-volume fees

Data posture tools that meter scans or scanned volume.

Integration

Per-connector fees

Integration platforms billed per connector or endpoint.

One license model. One platform. No compounding costs.

What Drives Price

What impacts your pricing

Pricing is determined by a small number of factors — not a dozen hidden meters.

Node Count

Total systems running PumaMesh

The primary input. Count the systems you want to enroll in the fabric.

Node Type

Agent, Relay, Hub

Each role has a different operational profile and licensing profile.

Deployment Scale

Geography and complexity

Geographic distribution, network conditions, and environment complexity.

Security Requirements

Advanced policy + crypto

Advanced policy enforcement and cryptographic requirements.

Support & Architecture

Onboarding and mission support

Level of onboarding, customization, and mission support.

Term & Commitment

Annual or multi-year

Longer commitments unlock better unit economics and lock predictable pricing in place.

ROI

Predictable costs at scale

Because PumaMesh is not usage-based, costs remain stable even as data movement grows. Scale data movement without cost spikes. Avoid unpredictable billing tied to usage. Eliminate multiple licensing layers. Reduce operational overhead.

Move more data without paying more to move it.

Proof

Performance without penalty

1 TB / ~6 min

PumaMesh moved 1 terabyte of data in approximately 6 minutes in benchmark testing. Because pricing is not tied to throughput or volume, customers can take full advantage of that performance without incurring additional cost.

FAQ

Frequently asked questions

Data Volume

Do you charge based on data volume?

No. PumaMesh is not priced per GB or per transfer.

Connectors

Do you charge for connectors or integrations?

No. There is no connector-based licensing.

Cost Drivers

What determines cost?

Cost is based on node count, node type, and deployment requirements.

Unlimited Movement

Can I move unlimited data?

Yes. Once deployed, you can move data without usage-based fees.

Pilot & Scale

Can I start small and scale?

Yes. PumaMesh supports pilot deployments and scales by adding nodes.

Air-Gapped

Can I deploy disconnected or offline?

Yes. PumaMesh supports air-gapped and disconnected deployments with the same licensing model.

Deploy Without Limits

Tell us about your environment

We'll help you design a PumaMesh deployment that fits your needs — with clear, predictable pricing.