Number of Seats/Users: Buddy 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 Buddy 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 Buddy. Buddy reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Buddy 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 Buddy. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Buddy 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 Buddy is seen as a very strong CI/CD choice, especially for teams that value ease of use and fast setup, but cost and resource limits are a recurring concern.

Key positives our Spendbase clients highlight:

• Very intuitive, “pleasant to use” UI
• Extremely easy pipeline setup (often in minutes)
• Hybrid GUI + YAML approach that fits both non‑DevOps people and advanced engineers
• Large library of ready‑made actions and integrations (Docker, K8s, SFTP/FTP, mobile builds, notifications, etc.)
• Reliable automation for web, mobile, and mixed stacks (Vue, Laravel, WordPress, Node, Android)
• Strong impact on:
• Time saved on deployments
• Fewer failed or “invisible” deploys
• Easier onboarding to CI/CD for teams with little DevOps background
• Generally praised, responsive support in most accounts

Main pain points our internal data surfaces:

• Pricing:
• Cloud plans perceived as expensive vs VPS cost
• User‑based pricing and worker/concurrency limits feel restrictive
• On‑prem/enterprise jump in cost at user thresholds is painful
• Performance and limits:
• Resource caps (CPU/RAM) can be too low for heavy builds, especially Android
• Queueing and concurrency limits can slow down large or fork-heavy setups
• Occasional cache issues and timeouts on long‑running tasks
• Product gaps:
• Desire for cheaper, “CD‑only” or per‑project plans
• Some advanced features locked behind higher tiers
• Smaller community compared to big CI/CD players
• Missing dark theme and some UI instability due to frequent changes
• Need for clearer examples for automated tests (e.g., Jest)

How this maps to optimization opportunities for Spendbase clients:

• Many could:
• Downscale to a more targeted plan (e.g., CD‑only, fewer users but more workers)
• Negotiate better pricing around:
  • Concurrency/worker limits
  • On‑prem user thresholds
  • Long‑term or volume commitments
• Rebalance workloads so memory‑heavy builds run on cheaper infrastructure, while Buddy handles orchestration

In short, our clients love Buddy’s usability and power, but they often overpay for users and hit resource ceilings. That’s exactly where Spendbase can step in to restructure contracts and usage so teams keep the good parts of Buddy while cutting unnecessary spend.