Enterprise deployment

Install it where the internet does not reach

An air gap fails on something ordinary — a licence check, a usage ping, an update that assumes a package repository. Wraft has none of them. An instance with no route out is a normal deployment here, not an exception you negotiate for.

Book a call Read the source

AGPLv3 · Air-gapped installations · Commercial licence available

AGPLv3 · No licence server · No telemetry · Your database, your bucket

Read the source

The boundary

Nothing leaves, because there is nothing to leave for

Isolation that depends on a firewall rule is isolation someone can misconfigure. This is the other kind: the software has no outbound dependency to block, so a disconnected install is not a hardened configuration of a connected product — it is the same product, with nothing to disable.

No licence server Nothing validates your right to run it, because AGPLv3 already granted that. There is no key to renew, and no call that fails at 2am on a network with no route out.
No telemetry A self-hosted instance makes no outbound call to us — no usage reporting, no crash upload, no version check. Read that in the source, or block egress and watch nothing break.
Your database, your bucket Metadata in a Postgres you run, files in an S3-compatible store you own — MinIO on your own hardware where the deployment never touches a cloud. Both stay readable with or without Wraft running.

Book a call Who secures what

One boundary. Drafting, signature and archive all inside it, on storage you own.

Inside the boundary

Create. Automate. Sign. Store.

Most organisations buy these four from four vendors, and every handoff leaves another copy of the agreement on infrastructure nobody chose deliberately. Here the document never crosses the boundary at any stage of its life.

Create Authoring

Documents assembled from structured templates and an approved clause library. Legal owns the language, the template owns the layout, and neither is edited to produce a document.

Automate Generation

Records from a system you already run become finished documents over an API call. Hundreds in one job, with per-record errors and a re-run for only the ones that failed.

Sign Approval

Approval routing and e-signature inside the same system that drafted the document, with every approval bound to the exact revision it approved.

Store Archive

A queryable archive rather than a folder of PDFs — extraction, full-text and field search, retention policy, and legal hold that overrides it.

The licence

Two sets of terms, one build

Wraft is dual licensed, and which one you need is a question about obligation rather than capability. The software is identical under both — no feature is unlocked by paying, and if that ever changes it will be a different company.

AGPLv3

Recommended

Free

Forever, for everyone

The complete platform on your own infrastructure, including disconnected. Most enterprises never need anything beyond this — including large ones running Wraft for thousands of staff.

Every feature, no user or document limits
Run it internally, forever, at any scale
Air-gapped installation supported
Read, modify and audit every line
Community support on GitHub and Discord

Read the licence

No account, no licence key, no sales call.

Commercial

Talk to us

Priced per engagement

The same software under different terms, for organisations that cannot accept copyleft — because they ship Wraft inside a product, or because their legal function will not approve AGPL at any price.

Identical software — nothing extra is unlocked
Embed and redistribute without copyleft reaching your code
Keep your own modifications private
Written warranty and IP indemnity
Contracted support and a named escalation path

Book a call

We will tell you if you do not need this. It happens often.

Which one applies

Most enterprises never need the commercial licence

Including large ones running Wraft for thousands of staff. AGPLv3's obligations are triggered by giving Wraft to others, not by using it.

Running it for your own organisation, at any headcount AGPLv3 Internal use is not distribution. Nothing is triggered and nothing is owed.
Shipping Wraft inside software you sell or install for clients Commercial Your product becomes a derivative work, and AGPLv3 would require you to release it on the same terms.
Your legal function will not approve AGPL, whatever the use Commercial A common and entirely reasonable policy. The licence is the blocker, not the software.

The full decision table

A plain reading of the licence, not legal advice. If your architecture sits near the line, describe it on the call and you will get a straight answer — including the answer that you do not need to buy anything.

The engagement

What an enterprise agreement actually buys

Not features. Every capability on this page is in the AGPLv3 core and stays there. What you are buying is people, obligations, and time you would otherwise spend.

Air-gapped installation

The deployment work in a disconnected environment: the offline artifact set, the dependency mirror, the runbook your operators will actually hold, and an upgrade path that does not assume a package repository on the other side of the boundary.

Support with names on it

Contracted response times and a named escalation path, so an incident is a person you can reach rather than a GitHub issue competing with everyone else's. What the times are is a conversation, not a number we publish.

Deployment and migration engineering

Paid engineering time against your environment — install design, migration off an incumbent, template architecture. Work your team could do themselves; the question is whether you want them spending the quarter on it.

Compared honestly

Where we win, and the row where we do not

Written against how an enterprise actually scores a document platform. One row goes the other way, and it is the row a procurement team will check first.

Dimension Wraft, self-hosted Typical enterprise CLM

Dimension Where the agreements physically sit Wraft, self-hosted Infrastructure you own, including hardware with no route to the internet. Typical enterprise CLM The vendor's cloud, with a region setting inside an account they control.

Dimension Running disconnected Wraft, self-hosted Supported. No licence check, no telemetry, no outbound dependency to block. Typical enterprise CLM Generally not offered — the product assumes connectivity to operate.

Dimension Reading the code that handles your contracts Wraft, self-hosted Public under AGPLv3. Your architects review the source itself. Typical enterprise CLM Under NDA at best, and usually a certification offered in place of it.

Dimension Certifications Wraft, self-hosted None held. We are not SOC 2 or ISO 27001 certified. Typical enterprise CLM Usually SOC 2 Type II and ISO 27001, sometimes more.

Dimension What scales the bill Wraft, self-hosted Volume and support level, if you buy either. Adding a reviewer costs nothing. Typical enterprise CLM Seats, typically re-priced at renewal.

Dimension Deciding to stop paying Wraft, self-hosted Keep running it. Nothing switches off, and the published release cannot be withdrawn. Typical enterprise CLM Access ends at term. Export first.

Dimension If the vendor goes away Wraft, self-hosted The source is public and the data is already yours. Worst case, you maintain it. Typical enterprise CLM A wind-down clause and an export window.

Dimension Your exit Wraft, self-hosted Your Postgres and your bucket, in open formats. There is nothing to migrate out of. Typical enterprise CLM An export process, in their formats, on their timetable.

'Typical' is a composite drawn from public vendor documentation and standard enterprise contract terms, not any single product. Where a specific vendor differs, hold us to the specific one.

Where we are

What we do not have

We are not SOC 2 or ISO 27001 certified. Any vendor telling you their software is SOC 2 certified is describing it inaccurately — the audit covers an operating organisation, not a codebase — but the distinction does not help you if your procurement requires a certificate. Say so on the first call and we will tell you where we are instead of spending a quarter of your time.

We have no public customer references yet. That is why this page has no logo wall. We would rather hand you the licence and the source than a row of names we cannot stand behind.

We do not operate Wraft inside your cloud account. It runs in your environment, but your team runs it. There are two arrangements and no third: you host it, or we host it on infrastructure we operate. An enterprise engagement is help doing the first — not one where we hold credentials into your environment.

Wraft is young. Every capability described on this page exists and is in use, but the platform is early, and you should weigh that against a fifteen-year-old vendor honestly rather than let us frame it as an advantage.

What we do have is the part that cannot be revoked. The whole system is under AGPLv3, running on infrastructure you control, with your agreements in your own database and your own storage in open formats. The published release cannot be withdrawn from anyone who already holds it. Everything above is a reason to ask harder questions on the call — which is what the call is for.

How it starts

The order the work happens in

Nobody installs a document platform into an isolated network on a Tuesday afternoon. This is the sequence, and the exit exists from the first stage rather than the last.

First call
Constraints before capabilities

What the boundary is, what your operators already run, what your change process requires, and whether AGPLv3 is acceptable to your legal function. A good half of this call is us working out which parts you do not need to buy.

You end up with A straight answer on whether this fits, including no.
Technical review
Your team reads the code

The source is already public, so review starts before any agreement exists and without anyone signing an NDA to begin it. We answer your security questionnaire, and where the honest answer is 'not yet', that is the answer you get.

You end up with Your architects' sign-off, or a specific list of what blocks it.
Pilot
One agreement type, end to end

A single document type all the way through on your infrastructure — template, data source, approval path, archive. Run it disconnected from the first day if that is where it is going to live, rather than discovering the difference later.

You end up with A working installation and a real cost figure.
Production
The rest of the paper, and the terms

Remaining document types, the operator runbook, an upgrade procedure written for a disconnected environment, and whichever licence and support agreement the pilot showed you actually need — which is sometimes neither.

You end up with An installation your team can run without us. That is the point.

Book a call

A shape, not a schedule. Your change-control process sets the pace, and we would rather match it than quote a timeline we cannot hold.

Before the first call

What security and procurement ask

Can it genuinely run with no internet connection?

Yes. There is no licence server to reach and no telemetry endpoint, which is what makes it viable — nothing degrades when egress is blocked, because nothing was reaching out to begin with. You do not have to take that from us. The source is public, and the fastest check is to run it with the network cut and watch what fails.

How do updates work in a disconnected environment?

The same way the rest of your disconnected estate is updated: artifacts cross your boundary by whatever transfer process you already operate, then get applied. There is no auto-update assuming a package repository and no phone-home step that has to succeed first. Writing that procedure with your operators, for your specific transfer process, is part of an air-gapped engagement rather than a generic document we hand over.

Does running Wraft oblige us to publish anything under AGPLv3?

Not for internal use, at any scale. AGPLv3's obligations are triggered by giving Wraft to others — distributing it, or letting outside users interact with a modified version over a network. An organisation running it for its own staff never reaches them, whether that is ten people or ten thousand. This is a plain reading of the licence and not legal advice; /licensing sets out the cases in full.

Our legal function will not approve AGPL under any circumstances.

A common policy and a defensible one. That is what the commercial licence is for: the same software under terms that do not carry copyleft, with a written warranty and IP indemnity attached. The blocker in that case is the licence rather than the deployment, which usually makes it the shortest conversation on the list.

Are you SOC 2 or ISO 27001 certified?

No. And any vendor telling you their software is SOC 2 certified is describing it inaccurately — SOC 2 audits an operating organisation's controls, not a codebase. In a self-hosted deployment the controls in scope are yours, running on your infrastructure, and Wraft is a component inside your own audit boundary rather than a separate one you have to trust. If a certificate is a hard procurement gate, tell us on the first call.

Can we get a penetration test report?

Tell us what your review requires and we will be straight about what exists today versus what we would need to commission. We would rather say 'not yet' than send a document that does not answer your question, because you will read it and find out.

Does it support our identity provider?

Single sign-on is in the AGPLv3 core, not an enterprise add-on you unlock. Which providers are supported is a specific question with a specific answer — bring yours to the deployment conversation rather than take a blanket claim that we support all of them.

Do you need access to our environment to support us?

No, and in an air-gapped installation you could not grant it even if we asked. Support works from logs and artifacts you choose to share. That is slower than a vendor with a console into your system, and it is the trade you are making deliberately — you cannot have both the isolation and the convenience of someone else being able to look.

What happens to us if Wraft the company goes away?

You keep running it. The AGPLv3 release cannot be withdrawn from anyone who already holds it — no version we have published can be un-published — and a perpetual commercial licence survives us. Your agreements are already in your own database and your own object storage, in open formats. The worst case is that you maintain it yourself, not that it stops. For a procurement team pricing vendor risk, that is the entire argument for open source in one sentence.