Signing is free.

Every signed PDF comes back sealed, with a certificate of who signed, when and from where. Say who signs and each person gets their own link. They need no account. There is no cap on signatures.

Free, unlimited

Every e-mail signature, however many, for as long as you like. The sealed PDF, the certificate and the event trail come with it, by e-mail.

Everyone gets the signed PDF by e-mail the moment the last person signs. It stays here for download for 30 days. Archive, from NOK 99 a month, keeps it here longer.

What is free, and what is not
Six jobs

VAMOSIGN does one thing. It gets documents signed.

Six ways people actually need it done. All of them are in the product from day one.

01

“Get this contract signed.”

Upload one file or several, or write the three sentences straight in. Enter who should sign, choose an order or let everyone sign at once.

  • Sequential
  • Parallel
  • End date
Free, on every plan.Step by step
02

“Get the same document signed by 200 people.”

Everyone on the list gets their own copy and signs it. You see who is missing and remind them all in one press. Every copy carries its own reference.

  • Bulk
  • A reference per copy
  • Remind everyone
With Team · NOK 199 a month, ex VATStep by step
03

“Let anyone sign our public documents.”

Publish a template as a form. It is a page with your own words, at a link you share. Whoever comes gets their own copy, confirms their e-mail with a code, and signs. You send nothing.

  • Form
  • Self-signing
  • Public link
With Business · NOK 499 a month, ex VATStep by step
04

“Get the same document signed every X months.”

Sign on a schedule. When you upload a new version, we ask for a new signature. When an agreement is about to expire, the request goes out a set number of days before.

  • Schedule
  • New version
  • Before expiry
With Business · NOK 499 a month, ex VATStep by step
05

“Get everyone who signed v1 to sign v2.”

Upload the new version and we find everybody standing on an older one. They get the new one to sign; the old signature stays its own proof of what they agreed to then.

  • New version
  • Finds the outdated
  • The old proof stands
With Team · NOK 199 a month, ex VATStep by step
06

“Let signing happen inside our own system.”

An MCP server and an API. Your assistant, your case management system or a script sends the request. Signing happens where the work already takes place.

  • MCP
  • API
  • Webhooks
Free, on every plan.Step by step
MCP and API

Give your personal AI the power to sign documents.

Connect the MCP server to your assistant, or call the same functions over REST. No SDK to install, no envelope model to learn. You describe what needs signing, by whom, and when it should happen again.

Tools your assistant gets
  • send_for_signature
  • bulk_send
  • create_self_sign_link
  • check_status
  • request_new_version
Triggers
  • At a fixed interval, in months
  • When a new version is uploaded
  • A set number of days before expiry
What you get back
  • Sealed PDF with SHA-256
  • Signing certificate per signer
  • Full event log
  • A webhook on every event
// mcp: VAMOSIGN
send_for_signature({
  title: "Framework agreement 2026",
  document_base64: "JVBERi0xLjcK…",
  signers: [{ email: "anna@example.com" }, { email: "ben@example.com" }],
  order: "sequential",
  expires_on: "2027-03-31"
})
→ 2 requests sent · sealed PDF in return

Send your first document today.

Sign up with your e-mail and upload. The people signing need nothing: they get a link, open the document and sign.

Send your first document