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

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

Early Renewal or Prepayment: Miruni 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 Miruni (BugReplay) is especially valuable for teams that care about speed, clarity, and cutting down back-and-forth with engineering.

Based on feedback from Spendbase clients, we see a few strong patterns:

1. Biggest value drivers

• Massive time savings for dev & QA
• Clients consistently say they spend far less time recreating bugs.

• One-click recording plus automatic capture of console logs, network traffic, and environment details replaces long remote sessions with developers.

• Clearer communication across teams

• Bug reports come with full context: screen recording, network tab, logs, and comments.

• This greatly reduces misunderstandings between QA, product, support, and engineering.

• Better reproducibility and diagnosis

• Network tab capture is called out as “best on the market.”

• Engineers get enough data to understand what was happening for users without chasing extra info.

• Ease of use and adoption

• Simple workflow: click, record, add details, send.
• Works well alongside tools like LogRocket or FullStory.
• Pricing is often mentioned as affordable for the value provided.

2. Common use cases we see

• Testing new public-facing products before launch
• Daily QA bug submissions into dev backlogs
• Support teams recording customer issues with full technical context

3. Frictions and gaps

Our internal data also highlights a few recurring pain points:

• Access & authentication

• Lack of SSO/Okta support is a blocker for some larger orgs with strict identity management.

• Performance & recording delays

• Some clients experience:

  • Recordings taking a while to appear
  • Occasional issues where a recording fails to register
  • Minor slowdowns when the bug isn’t being recorded

• Workflow speed

• Creating a snippet can feel a bit slow (processing time and clicks).

4. How this affects your Spendbase savings strategy

When we model stack efficiency for our customers:

• Miruni tends to reduce time-to-fix and cut dev/QA coordination overhead, which indirectly lowers engineering cost per issue.
• It can replace or reduce the need for more manual logging/reporting tools.
• The main tradeoff we flag is around SSO needs and acceptable latency for recordings.

If your team struggles with bug reproduction and unclear reports, the cost-to-value ratio in our data is very favorable, especially once workflows are standardized around Miruni recordings as the default bug report format.