Pricing that matches your team and rollout needs
PTTHex pricing is scoped around the way your teams operate: users, approved devices, channels, branches, departments, deployment model, onboarding, integrations, and support requirements.
Starter Team
Growing Operations
Enterprise Rollout
Choose a plan by scope, not a fixed public price
These plan paths help frame the conversation. Final pricing depends on the rollout plan, license entitlement, approved users and devices, deployment model, onboarding, integrations, and support needs.
Starter Team
- Best fit: Pilot or small team
- Users and devices: Approval scope reviewed
- Channels and departments: Focused setup
- Deployment model: Standard rollout path
- Onboarding: Guided start
- Integrations: Discovery first
- Support planning: Launch guidance
Growing Operations
- Best fit: Multiple teams or sites
- Users and devices: Multi-team approval scope
- Channels and departments: Structured rollout
- Deployment model: Operational rollout plan
- Onboarding: Team training plan
- Integrations: Workflow review
- Support planning: Adoption support
Enterprise Rollout
- Best fit: Complex or private rollout
- Users and devices: Reviewed at scale with policy needs
- Channels and departments: Branch and department planning
- Deployment model: Customer-controlled review
- Onboarding: Role-based rollout support
- Integrations: Approved integration planning
- Support planning: Commercial review
What your plan actually covers
A PTTHex plan is a licensed set of capacity and features for your own deployment. Instead of a fixed public price, a plan is sized to the numbers below, so you pay for the scope you run.
Users and devices
The number of user accounts and approved devices, including how many devices can be active at once. Every device is approved before it counts against the plan.
Channels and structure
How many channels, branches, and departments your organization needs, so communication can be grouped the way your teams actually work.
Live voice capacity
How many people can speak at the same time and how many live voice sessions can run at once, sized to the pace of your operation.
Client platforms
Which apps your field users can sign in from: Android, iOS, Windows desktop, and Web. Enable the platforms your teams carry.
Feature entitlements
Which capabilities are turned on, such as the live dispatch map and zones, monitoring, and self-hosted translation and captions. Turn on what your rollout needs.
Deployment and support
Your deployment model, from a single server to a larger setup, plus onboarding and support. Capacity can grow later without moving to a new product.
Your plan is issued as a signed license tied to your own server. Local admins can narrow what is allowed, but never grant more than the license covers, so capacity stays predictable.
Questions teams ask before choosing a plan
A short pricing conversation is the best way to match scope, rollout needs, and commercial terms.
Request pricing guidanceRollouts vary by users, devices, channels, branches, departments, approved users and devices, deployment model, onboarding, integrations, and support expectations. A reviewed quote keeps pricing aligned with the actual setup.
Team size, operating locations, device mix, channel structure, branch or department needs, location or monitoring expectations, integration goals, onboarding timeline, and support expectations help shape the recommendation.
Yes. Smaller teams can use the Starter Team path to validate workflows before expanding to more users, devices, departments, or sites.
Implementation planning, onboarding, training, deployment guidance, and integration consulting can affect scope. The Services page explains those workstreams in more detail.
You can review the Privacy Policy and Terms and Conditions. Any customer-specific commercial or deployment terms should be confirmed during review.
Yes. PTTHex is self-hosted on your own server, and a plan is a licensed set of capacity and features for that deployment, covering users, devices, channels, live voice capacity, client platforms, and the features you turn on. Capacity can grow later without changing products.
Use the contact page to share your rollout goals. If you are still comparing options, the Blog can help with field communication planning topics.