# Compared with other signing apps

> SignPlus beside Digital Signature for Confluence and eSign Signatures for Confluence, one capability per row, with where each one is documented.
>
> Documentation for Oktul SignPlus for Confluence, for Confluence Cloud, by Oktul: https://oktul.com/docs/plugins/signplus/compare/

SignPlus beside other signing apps for Confluence Cloud. A tick means everything in the row's
definition; a partial cell names what is missing. Each app links to the Marketplace listing it was
checked against.

| Capability | [Oktul SignPlus for Confluence](https://marketplace.atlassian.com/1166020382) (Oktul) | [Digital Signature for Confluence](https://marketplace.atlassian.com/apps/1217404/digital-signature-for-confluence) (Matthias Cullmann) | [eSign Signatures for Confluence](https://marketplace.atlassian.com/apps/1224071/esign-signatures-for-confluence) (Digital Rose) |
| --- | --- | --- | --- |
| Qualified electronic signature | Yes | No | No |
| Signers outside your site | Yes | No | No |
| Signature tied to the page version | Yes | Partly: Tied to the macro's text, not the page | Yes |
| Signed file attached to the page | Yes | No | Yes |
| Page locked while it is signed | Yes | No | Partly: From the first signature |
| Groups as signers | Yes | Partly: Limits signing to a group | No |
| Started from a rule or the REST API | Yes | No | Partly: Webhooks only |

Checked on 21.10.2026 against each product's published documentation and its Marketplace listing. A dash means the feature is in neither. If a row no longer matches what an app does, write to hello@oktul.com and we will check it again.

## What each row means

Each definition links to the page that documents it.

- **Qualified electronic signature:** Each signer signs with a qualified eID, such as Smart-ID or an ID card, through a qualified trust service provider. eIDAS gives such a signature the legal effect of a handwritten one. How SignPlus does it: https://oktul.com/docs/plugins/signplus/#a-qualified-signature-through-dokobit
- **Signers outside your site:** A person with no Atlassian account can sign, from an email invitation. How SignPlus does it: https://oktul.com/docs/plugins/signplus/for-signers/#the-invitation
- **Signature tied to the page version:** The signature records exactly which version of the page was signed. How SignPlus does it: https://oktul.com/docs/plugins/signplus/after-signing/#what-the-byline-says
- **Signed file attached to the page:** When signing finishes, the signed document is attached to the page it was signed from. How SignPlus does it: https://oktul.com/docs/plugins/signplus/after-signing/#where-the-signed-file-is
- **Page locked while it is signed:** The app can stop people editing the page as soon as signing starts, so the text cannot change under the signers. How SignPlus does it: https://oktul.com/docs/plugins/signplus/configure/#the-page-while-it-is-signed
- **Groups as signers:** A Confluence group can be added as signers, and every member is invited. How SignPlus does it: https://oktul.com/docs/plugins/signplus/sign-a-page/#who-can-sign
- **Started from a rule or the REST API:** A Jira automation rule or another system can start a signing, through an action or a REST API. How SignPlus does it: https://oktul.com/docs/plugins/signplus/automation/

## Related

- [Sign a page](../sign-a-page/)
- [After signing: check, download, cancel](../after-signing/)
- [Automation and webhooks](../automation/)
- [Electronic signature terms](../signing-terms/)

---

A problem or a question? Write to [support@oktul.com](mailto:support@oktul.com) or open a request in the [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals). Both open a request with a reference and an SLA.
