Number of Seats/Users: Probely offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Probely that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Probely. Probely reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Probely offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Probely. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Probely often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Probely delivers strong value for teams that want practical, automated application security without heavy overhead.

From what Spendbase clients share with us, a few themes stand out:

1) Overall satisfaction and value
– Most clients rate Probely very highly on value for money.
– It’s often described as “intuitive” and “straightforward,” which reduces onboarding and training time.
– Several teams mention that, compared to competitors, pricing feels fair for the feature set.

2) Strengths our clients highlight
– Automation & CI/CD fit
– Easy integration into CI/CD pipelines (including “lightning” scans).
– Good for ongoing DevSecOps workflows rather than one-off scans.
– Developer‑friendly output
– Clear, evidence‑based findings.
– Fix instructions are detailed and written in a way developers can act on quickly.
– Compliance reports (e.g., PCI) are appreciated by security and audit teams.
– API-first approach
– The API mirrors almost all web UI features, which makes automation and data extraction simple.
– Multi‑environment targets (staging + prod under one “target”) are seen as a cost saver.
– Support quality
– Clients repeatedly mention fast, hands‑on support.
– Bugs and issues tend to be resolved quickly, which reduces downtime and internal frustration.

3) Common friction points
Our internal feedback also shows a few recurring limitations:
– Target flexibility
– Some clients struggle with scanning ephemeral or frequently changing targets (e.g., short‑lived containers).
– Auth setup
– Logging in to authenticated areas (user/password config) can be confusing at first.
– API depth & ecosystem
– While the API is strong, advanced controls and documentation could be richer.
– Missing or delayed integrations (like Jira) are noted by several clients.
– Scanning experience
– Limited visibility into scan progress (e.g., no clear ETA) can be frustrating.
– Scope limits
– Focus is excellent for web apps and APIs, but not for broader server or infrastructure patching.

4) Spendbase takeaway for buyers
If your team values:
– CI/CD automation
– Developer‑ready security findings
– Strong support
then Probely tends to deliver solid ROI. Just be aware of its focus on web and API layers and plan for separate tooling if you need deeper infrastructure coverage or very dynamic, short‑lived environments.