Put the whole PDF layer
inside your product.
This site is twelve PDF tools that run entirely in the browser tab. The same code can run inside yours. Signing, merging, splitting, rendering, local OCR — no document ever leaves the user's machine, so your infrastructure carries none of it and your security review has nothing to scope.
Sold as a written licence, not a checkout. There is no package to install today — a licence transfers source.
- servers touched per document
- 0
- tools in the suite
- 12
- runtime dependency: a browser
- 1
The first number is the reason a licence is worth anything: your marginal cost per document is zero, and so is ours.
Four modules, all of them already in production.
Not a roadmap. Every item below is what this site runs on right now, which is the only reason it can be licensed.
Signing and placement
Draw, type or upload a signature, place it by dragging on the rendered page, up to four signers per document, plus a Certificate of Execution page carrying a SHA-256 manifest of the output.
Document operations
Merge, split, organise, rotate, crop, number and watermark. All of it against bytes already in the tab, using pdf-lib. No queue, no worker, no polling.
Rendering
Page rendering and text extraction through pdf.js, so a host product can show a real preview and build its own overlays on top of the same canvas.
Local OCR and conversion
Scanned pages are read locally with a bundled Tesseract build, and photographs become a PDF without a server round trip. The slow part stays on the user's machine, which is why it costs us nothing.
What you get.
- The browser-side modules as readable source, not an obfuscated bundle.
- The right to embed them in one named product, under your brand and your domain.
- Updates to those modules for the term of the licence.
- An integration call with the person who wrote them.
- A named contact at the address on this page, for the term.
An embed licence is a written agreement between XVILAN LLC and your company. It is not a purchase on this site, and nothing here is charged online.
What it is not
Not an npm package
There is no published package, no CDN bundle and no versioned public API. Today a licence transfers source that you vendor into your build. An installable package is a product decision, not a line in a contract.
No licence key or seat enforcement
Nothing in the code phones home, so nothing can count seats. Enforcement is the contract and the source transfer, not a runtime check. If you need metered licensing, this is not it yet.
No documentation site or changelog
The code carries its reasoning in comments, which is not the same as docs. Expect to read it, and expect to ask questions during integration.
No SLA
A hosted service can promise an uptime number. This cannot, because there is no service to be up. What can be promised is a response time on the integration contact, and that belongs in the order form.
The AI scan is not part of the engine
The contract-scanning feature on /analyse sends extracted text to a model provider. It is deliberately excluded from an embed licence: it is the one part of this product that leaves the browser, and it would make a no-upload claim false in your product too.
Not a qualified signature
Exports carry a manifest and a certificate page. They are not qualified electronic signatures under eIDAS, and a licence does not change that. Do not put your name on a claim like that.
Three shapes, quoted in writing.
These are opening asks, not market data — no licence has been sold yet. They are stated here so a first conversation starts at a number instead of at “what is your budget”.
- Component
- One module — signing, or rendering — inside one product.
- $10k–15k / year
- Suite
- Every browser-side tool, embedded in one product.
- $20k–35k / year
- White-label
- The suite under your brand and domain, for one product line.
- $40k–50k / year
Opening ask · confidence: low · annual, invoiced
Say what you are building.
The reply is specific to your product: which modules fit, what you would have to write yourself, and where the boundary of the licence would sit.
If the answer is that you should build it yourself, that is also a legitimate reply, and it is cheaper for both of us to say so early.
Prefer plain email? Write to support@xvilan.com.