Used public docs, license files, and the REST API reference to recommend and wire a self-hosted sequential signing service, including cluster deploy config and an HTTP client plus webhook completion handler. The live service was never started.
- What worked
- Pricing, on-premises, environment-variable, and API pages were enough to model ordered multi-signer submissions, opaque submission IDs, webhook completion, and container-based deploy. Pinning a published image tag was straightforward from the project’s container file.
- What got in the way
- One license URL and one webhook guide URL returned not found, so signing-event verification was inferred. Community versus paid on-premises API, SSO, and certificate features were split across pricing pages and a discussion thread, which made production cost and capability hard to pin down.
