1. The problem can be addressed with a shared database, audit logging, and signed events without the operational and governance overhead of a Fabric-based network.
2. The trust model requires public-chain guarantees such as censorship resistance and open participation; a permissioned ledger is not appropriate for those requirements.
3. Procurement requires abundant third-party user validation and a large body of independent peer reviews; OBP has a smaller set of public peer reviews in the sources reviewed.
4. The organization cannot accept potential operational uncertainty associated with the managed cloud provider (for example, cloud account management or support limitations identified in community discussions), and prefers providers with different operational models.
5. The priority is rapid, low-cost pilots with fully transparent, line-item pricing available publicly without sales engagement.
Vendor-acknowledged issues
Vendor-known-issues documentation identifies practical limitations and developer-facing problems, including REST proxy timeout behavior, payload handling in tooling, chaincode upgrade constraints, debugging token issues on specific platforms, runtime compatibility constraints across chaincode environments, and occasional sample application failures.