Open source · Pre-release
Send a PDF, collect signatures in the order you choose and get back one sealed file with an audit trail anyone can check. Embed the TypeScript packages in your product, or run the service with Docker.
Four steps, from the first invitation to a file you can prove.
Upload a PDF, add the people who need to sign and place their fields. Each person gets a private link that expires.
Signers act one after another, or all at once. Each can confirm a one-time code by email or SMS before signing.
After the last signature, the values are drawn onto the pages, a certificate page is added and the file is sealed with your certificate.
Anyone with the file can check the seal and the audit trail offline, without asking the server that produced it.
Small packages with clear jobs. Use the whole service, or only the parts you need.
Sequential or parallel routing. People with the same order sign together. Reminders and expiry are built in.
Email or SMS codes: six digits, valid for ten minutes, locked after five wrong tries and rate limited.
Every action is appended to a log chained with SHA-256. The chain head is printed on the certificate page.
The final PDF carries a PAdES signature made with your certificate. Any later edit shows up in Adobe Reader.
For documents that need a statutory signature in India, through your own account with a licensed provider.
A signature pad, a signing view and field placement. Unstyled, and themed with CSS variables.
One image configured with environment variables, PostgreSQL and your mail server. Documents stay with you.
Apache-2.0 libraries you can use in any product, and an AGPL-3.0 server and app you can self-host for free. Read every line, no usage limits.
Start the server inside your own Node app, then create and send envelopes over its HTTP API with an API key.
Pre-release Not on npm yet; build it from the repository. The API may change before 0.1.
Read the Node guideimport { readFile } from 'node:fs/promises';
import { startSignServer } from '@codevibe_technology/sign-server';
const sign = await startSignServer({
databaseUrl: process.env.DATABASE_URL!,
filesDir: './data/files',
smtp: {
host: 'smtp.example.com',
port: 587,
secure: false,
user: 'sign',
pass: process.env.SMTP_PASS!,
from: 'Sign <sign@example.com>',
},
seal: { p12: await readFile('./seal.p12'), passphrase: process.env.SEAL_P12_PASSPHRASE! },
apiKeys: [process.env.SIGN_API_KEY!],
publicUrl: 'https://sign.example.com',
});
await sign.listen(3000);How the law in India sees each one, in short.
The built-in flow. An agreement made by electronic means is valid and enforceable (IT Act 2000, s.10A, with the Indian Contract Act). The audit trail and the sealed file show who agreed and when. It suits offer letters, policies, NDAs and most business documents.
An electronic signature under IT Act s.3A, issued through a licensed eSign Service Provider after the signer confirms with Aadhaar. Use it, or a DSC, where a law asks for a document to be signed in that statutory sense.
Some documents cannot be signed electronically at all, such as wills, powers of attorney and property sale deeds. This is not legal advice. Read the legal notes.
Yes. The libraries are Apache-2.0 and the server and app are AGPL-3.0, free to self-host. You pay only for what you run it on: your server, your mail and SMS delivery, and eSign credits with your provider if you use Aadhaar eSign.
Not yet. Every package works end to end and is tested, but nothing is published to npm and the APIs may change before 0.1. Try it now and wait for 0.1 before you rely on it.
No. You run the service, so documents, keys and personal data stay in your infrastructure. The one exception is Aadhaar eSign, where the document goes to the eSign provider you chose.
In India, an agreement signed electronically is generally enforceable, and the audit trail is the evidence. Some documents need a statutory electronic signature such as Aadhaar eSign, and a few cannot be signed electronically at all. See the legal page, and take your own advice.
A PKCS#12 file with a certificate and key. It identifies you as the operator, not the signer. A self-signed certificate works for testing; for files other people will open in Adobe Reader, use one from a trusted issuer.
No. You open an account with a provider such as Leegality, buy credits from them and give the package your API keys. Each eSign is billed to you by the provider.
Yes. The licence allows it. The licence does not cover the Codevibe names and logos, so please do not call your product or hosted service "Codevibe Sign".
Node 20 or later and PostgreSQL for the server. Your own backend can be in any language, since it talks to the server over HTTP. The UI components are for React.
Start with the concepts, or go straight to sending your first envelope.