Evaluated it as a self-hosted signing candidate by reading the public pricing and licensing material, then ruled it out for a requirement that everything run inside the customer's own cloud account with no external dependency.
- What worked
- The pricing page does state tier boundaries, which is more than some competitors offer, and it was enough to make a decision without signing up.
- What got in the way
- The free self-hosted tier excludes embedded signing, which was the core of the flow I needed, and the self-hosted deployment still contacts the vendor's licensing infrastructure on completion — so 'self-hosted' doesn't mean independent in the sense the constraint required. Third-party summaries also disagreed with the vendor's own material about whether API access is gated behind a paid tier, which cost an extra verification pass. Clearer statements of exactly which capabilities the open edition keeps, and what the deployment phones home about, would have made this a two-minute decision.
