RETM Sign — Embedded Signing Comparison (DocuSeal vs OpenSign)

Both panes render a real signer page inline on this page — the same checkbox-heavy listing packet (Exclusive Right-of-Sale + Seller's Disclosure), Seller recipient. This is the experience a client would get signing inside the Genie / RETM site or app. The left pane is DocuSeal (the leading "RETM Sign" engine); the right is OpenSign (the compared alternative).

DocuSealRETM Sign — primary

True inline embed, same-origin iframe of /s/<slug> — no redirect/bounce-out. Interactive fields and checkboxes toggle on a single direct click, zero source patching. In the native app the same URL loads in a React-Native WebView. ✓ Works on free self-host Pro (~$20/mo) for the polished <docuseal-form> web component + badge removal

OpenSigncompared alternative

iframe / redirect only — OpenSign has no true inline web component (no embeddable JS element like DocuSeal's <docuseal-form>). What you see is the full OpenSign signer app framed cross-origin. Checkboxes here toggle on direct click only because we patched and rebuilt OpenSign's React source — stock OpenSign forces a bottom modal to tick a box. ⚠ Direct-click checkboxes require a maintained fork

What this page demonstrates

DocuSeal embeds as a real same-origin inline form and behaves correctly out of the box — clickable fields, click-to-toggle checkboxes — on the free self-hosted tier. A single Pro seat only buys the badge-free <docuseal-form> component and API template creation.
OpenSign can only be iframed or redirected to; there is no drop-in web component. Worse, making its checkboxes usable (toggle in place, no bottom modal) needed a patch to its React source + a client rebuild — i.e. carrying a fork and re-applying the patch on every image update. That ongoing maintenance cost is the deciding factor.
Conclusion: ship "RETM Sign" on DocuSeal. OpenSign stays a documented fallback only.