Pricing
Trade pricing is structured around a core subscription, scoped add-ons, and rollout complexity.
This repo does not prove a locked public rate card, so the pricing page focuses on honest package structure: Trade Core, Export License Lifecycle, Controlled Data Delivery (beta — internal secure-portal pickup live, external connectors roadmap), and Enterprise Connect implementation scope.
Scoped subscription
The operational foundation for export transaction screening, analyst review, evidence generation, and audit support.
Add to Trade Core
Adds export authorization tracking, drawdown control, transaction linkage, and in-product alerts.
Add to Trade Core
Beta add-on module for controlled technical data request, approval, sealed packaging, and internal secure-portal pickup with audit-ready proof. External connectors (SharePoint, SFTP, Cryptshare, FAA SharePoint) are roadmap.
Implementation scoped
Scoping layer for rollout, system mapping, connector setup, and enterprise operating model alignment.
Direct answer
How is SecurePoint Trade priced?
Trade is presented as a package model, not a fake precision rate card. Buyers start with Trade Core, add Export License Lifecycle where authorization control is needed, evaluate Controlled Data Delivery as a beta module (internal secure-portal pickup live; external connectors roadmap), and buy Enterprise Connect as implementation work aligned to the existing environment.
- Clear base subscription plus add-ons
- No invented per-seat claims where repo evidence does not exist
- Pricing conversation anchored to workflow and rollout scope
Package matrix
A pricing structure buyers can understand before the first call.
The goal is to make scope visible: what is live now, what is an add-on, what is planned, and where implementation work begins.
| Package | Trade Core | License Lifecycle | Controlled Data Delivery | Enterprise Connect |
|---|---|---|---|---|
| Best fit | Teams replacing spreadsheet-based transaction review | Teams that need drawdown, linkage, and license balance control | Teams planning governed technical-data release workflows | Teams with rollout, mapping, and integration complexity |
| Status | Available now | Available now | Beta — internal secure-portal pickup live; external connectors roadmap | Scoped implementation |
| Typical scope drivers | Transaction volume, analyst throughput, evidence and approval depth | Authorization count, line structure, drawdown complexity, rollout pace | Program sensitivity, approval design, packaging and delivery requirements | ERP landscape, secure exchange posture, mapping and deployment effort |
| What to expect | Subscription-led package | Add-on to Trade Core | Roadmap-aligned planning conversation | Custom implementation package |
Scope notes
What buyers should expect during packaging and onboarding.
Trade is strongest when the implementation conversation matches reality: core workflow first, license control where needed, rollout planning where the environment is more complex.
Onboarding
Expect onboarding to cover intake method, queue design, approval posture, evidence expectations, and the launch path into the SecurePoint workspace.
Integration
Current repo evidence supports API keys, connector management, API/SFTP posture, and Oracle EBS mapping cues. Broader SAP or SharePoint rollout should be scoped as implementation work, not assumed as a turnkey checkbox.
Roadmap
Controlled Data Delivery is in beta and enabled per tenant. Internal secure-portal pickup with sealed packaging and audit-ready proof is live; external connectors (SharePoint, SFTP, Cryptshare, FAA SharePoint) are roadmap and should not be sold as live byte transport.
Pricing FAQ
Answer-first guidance for common buying questions.
The page keeps answers concise so buyers and AI search tools can pull the commercial structure quickly.
No. The repo supports a clear package structure, but it does not prove a locked public rate card. Pricing is better represented here as a scoped subscription plus add-ons and implementation work.
Pricing scope is typically driven by transaction volume, operator count, license-lifecycle needs, rollout complexity, and the depth of implementation work required for upstream systems.
It is represented here as a separate add-on so buyers can understand the base platform separately from authorization management and drawdown control.
As custom implementation scope. The repo supports connector and API-key posture, but broader ERP mapping and secure exchange rollout depend on the customer environment.
It is priced as a beta add-on module to Trade Core, enabled per tenant. CDD is secure-portal only today — internal secure-portal pickup with sealed packaging and audit-ready proof is live. External delivery connectors (SharePoint, Cryptshare, FAA SharePoint, SFTP) are not shipped and are refused at dispatch in customer tenants.
Next step
Use the pricing structure to scope the right Trade rollout.
Start with Trade Core, add the workflows you need, and keep planned modules clearly separated from what ships today.