Pick your workspace, and sign a document in minutes.

Pick your door above. Create a company account if you will prepare and send documents; a personal account if you only sign and keep your own. A company account asks for the company name, its country and your name and email (the tax ID and the legal name are optional); a personal account, for your name, country and email. A robot check comes with the form. Then you get a confirmation link, and you finish setting up your sign-in when you open it.

A working installation of Signing Flows with every capability marked Available in the catalogue, within the limits each line states, and test data only. Your own account, a test certificate provider, and resets from time to time. The account you create here is a demonstration account: it sees test providers, marked “(test)”, and carries test data only.

Company, if you will send documents to others and want colleagues working with you. Personal, if you mostly sign what others send and want your copies in one place. You can have both, with different emails.

No. They are the cast of the live demonstration, and their access is not public. You get your own account, separate from theirs and from everyone else’s.

The sandbox’s default plan for your kind of account, personal or company, set by the operator of this installation. It is a test subscription: no payment, no commitment, and the limits the sandbox sets. Real plans are on the Plans page.

In a company account you create, you are its administrator: you set it up, give access to colleagues with a role (administrator, sender or reader), and send documents. In a personal account you sign and keep your documents.

Yes. From Users you give them access with a role; they confirm by email. Your account stays yours: nobody outside it sees your documents.

No. Open the personal link in your invitation and sign there. Create a personal account later only if you want your signed documents kept in one place.

A PDF as you have it. Place the fields people fill in and the places where they sign, or leave each signer to place their own. Templates make repeatable documents faster; a spreadsheet lets you invite many signers at once.

People who sign, approve, review, or only receive a copy. In order, all at once, or by quorum, where N of M signatures are enough. Each role leaves its own event in the evidence.

Yes, as a dossier: one notice, one entry, one signature per document. Each document keeps its own evidence and report, naming the dossier.

By email, with a personal link. By SMS where the sandbox has it enabled. If a notice does not arrive, the sender can hand the link over directly.

By consent, with their identification recorded; or with a certificate from the test provider, which every account in the sandbox has. No real identity services, unless you connect your own.

The signer proves who they are with a code, reads the document, and agrees to sign. The platform applies the signature with that identification and a timestamp recorded in the evidence.

In the sandbox, one from the test provider, issued for the test in the signer’s name. In a real installation, the providers configured for it, including a certificate the signer already owns.

Yes. The personal link opens in the phone’s browser; there is nothing to install. The document fills the screen and you go one step at a time.

Entering with a digital identity wallet is in the catalogue as on request. The sandbox has no real identity service, so here it is not switched on unless you bring your own.

The signed PDF, the completion report, and the evidence record: every step, in order, chained so that nothing can be altered without showing. Each PDF stands on its own.

Yes. The public verification page reads the file itself, and so does any validator that understands PDF signatures. No account, no request to us.

Because the test provider is not in any trust list. The signature is intact and the signer is identified; what the validator cannot confirm is the provider’s standing, and the report says exactly that.

A signed PDF carries its own proof. Keeping it verifiable for years, with timestamps renewed over time, depends on a timestamp service being enabled for the installation; the catalogue line says so.

No. Test data only, with no legal effect. The certificate provider is a test one, so a validator may say Indeterminate about the trust of a signature, and the report says why.

The people you gave access to in your account, and each person you sent a document to, for that document. Accounts are isolated from one another.

As a deployment option, yes: the document is processed inside your network and only the workflow, the evidence and the fingerprints reach the cloud. Not in the sandbox; write to us.

From time to time, without notice. Everything goes, your account included. Download what you want to keep; the signed PDF and its report stay verifiable on their own.

Yes. Create your account, then create a token under Integrations. If you would rather start from a workspace with sample documents and people, ask for an evaluation account. Take the Developers door: the API reference, the integration guide and the API demo.

Yes. Each step of a document reports an event, from created to completed, with its name and its data; the API reference lists them.

The Connectors page lists what is available today, what is on request and what is in the roadmap. Anything with an API can be joined through your own code or through n8n.

The providers: real identity, signing and timestamp services, configured for that installation. The country of each signing act and its legal framework. And a plan, with its limits.

Each signing act carries the framework of its own country, and an installation can serve several. Learn explains what each country accepts; the catalogue says what is built.

Yes: in the cloud, in your data region, or inside your own network. Plans explains the options; the rest is a conversation.

Write to us from the About page. Questions about the product, about this site, or about an evaluation.