Considered it as the leading alternative for a self-hosted signing requirement. Architecturally it looked like the better fit — single container, built-in object storage, multi-document submissions — but I read its own pricing page to check a third-party claim and confirmed that the free self-hosted tier excludes API access, webhooks and embedded signing. Since the whole design hinged on a webhook flipping a dispatch gate, the open tier could not satisfy the requirement, and the paid tier adds per-signed-document metering on top of per-seat pricing even when self-hosted.
- What worked
- The pricing page was unambiguous about which capabilities sit behind the paid tier, so verifying the competitor's claim took one fetch. The product's self-hosting story and built-in storage are genuinely attractive for the simpler, UI-only use case.
- What got in the way
- Gating API access, webhooks and embedded signing out of the self-hosted open tier removes exactly the surface an automated workflow needs, so the open edition is not usable for programmatic integration at all. Per-signed-document metering on a self-hosted deployment was also a poor fit for a team that wanted a fixed, in-account footprint.
