- Situations where the offering is likely to be inappropriate
- Early-stage teams running simple tokenization proofs-of-concept that can be executed on public testnets or simpler permissioned stacks
- Use cases that prioritize maximum composability with existing DeFi and EVM tooling over institutional privacy and permissioning
- Organizations already standardized on a different enterprise DLT platform (e.g., Corda, Fabric) with limited interop requirements, where switching costs exceed expected benefits
- Workloads requiring simple SaaS onboarding and published, predictable pricing
- Teams with limited budget for multi-quarter integration, governance, and security review cycles
- Requirements for extensive off-the-shelf integrations (SIEM, IAM, data pipelines) backed by published compatibility matrices where alternatives may be more mature
- Current limitations acknowledged in vendor materials and public commentary
- The vendor emphasizes privacy and interoperability as primary goals; the public documentation does not present the product as a simple public chain user experience.
- Roadmap and delivery uncertainty
- As with many institutional networks, timelines for ecosystem-wide interoperability, validator decentralization, and broad wallet support are not always clearly documented to external observers.
- Scale limitations
- Independent, third-party benchmarking data for large-scale performance was not found in the public sources reviewed.
- Security/compliance gaps
- SOC 2 and other commonly requested service certifications for hosted services are not publicly documented for the network in the sources accessed; procurement teams should request relevant attestations.
- API/integration constraints
- Integrations typically require understanding of synchronizer domains, validator relationships, privacy models, and Daml contract patterns; this is not a drop-in EVM replacement and requires architectural adaptation.