Prop Firm Software Buyer Data Dictionary
Vendor comparisons break when identical-looking terms mean different things. This dictionary defines the fields Prop Firm Vendors uses to normalize commercial and technical research, while preserving vendor-specific definitions where they affect cost.
Commercial units
- Setup fee
- One-time charge associated with onboarding/implementation. Inclusion and refundability must be recorded separately.
- Monthly base
- Recurring software/platform fee before usage, third-party or percentage charges.
- Active trader
- A vendor-specific billing/capacity term. Never assume it equals unique customer without the vendor's definition.
- Account
- A trading/evaluation account; one customer may hold multiple accounts.
- Funded trader/account
- A trader/account that has reached the provider's funded stage; relevant to credit/usage models such as PropSim.
- Credit
- A vendor-defined consumption unit. Record what event consumes it and whether it expires.
Percentage economics
- Revenue share
- Percentage of a contractually defined revenue base. Record gross/net definition, deductions, floor and tier.
- Net-profit share
- Percentage of defined profit after specified deductions. Not interchangeable with revenue share.
- Minimum
- Fixed floor payable even if the percentage calculation is lower.
Capacity and reliability
- Unlimited
- A vendor claim that must be tagged as billing, plan or technical scope; it should not automatically be interpreted as infinite capacity.
- Uptime claim
- Published availability statement without assuming contractual enforceability.
- SLA
- Service commitment whose measured service, period, exclusions and remedies should be recorded.
Integration terms
- Native integration
- Capability built/maintained as part of the product; exact responsibility still needs verification.
- Partner integration
- Connection involving a third-party relationship or intermediary.
- Custom integration
- Connection requiring bespoke development or professional services.
- API/webhook
- Programmatic interface/event mechanism; record tier, operations, limits and documentation status.
Migration and ownership
- Migration included/free
- Vendor does not charge some stated migration fee; does not imply zero internal, overlap or third-party cost.
- Zero downtime
- Provider-stated continuity objective/claim; should be validated against architecture and rollback.
- Data ownership
- Contractual rights over records; track export, use, retention and deletion separately.
- Source-code ownership
- Rights over underlying software; separate from data, branding and configuration.
Why this improves SEO and buyer value
Normalization lets our comparison pages explain genuine differences rather than mechanically repeating provider terminology. It also prevents false claims such as treating “no per-account fee” as unlimited technical capacity or a security roadmap as current certification.
Use the definitions with our public pricing dataset and technology benchmark.
Methodology note
When a provider supplies its own explicit definition, that definition takes precedence for calculations involving that provider. This dictionary exists to make differences visible, not erase them.