vectorize — licensing

Copyright 2026 Siarhei Dudko

One licence covers everything here: the libraries, the container images, and the
web application served from vectorize.dudko.dev. Free for noncommercial use;
commercial use is paid.

## The grant

Everything in this repository, and every artefact built from it — the npm
packages `@dudko.dev/vectorize-core` and `@dudko.dev/vectorize-cli`, the
container images `vectorize` and `vectorize-api`, and the web application and
WebAssembly modules delivered to a browser by the hosted site — is offered
under:

- **PolyForm Noncommercial License 1.0.0** — `LICENSES/PolyForm-Noncommercial-1.0.0.md`,
  SPDX `PolyForm-Noncommercial-1.0.0`. Any noncommercial purpose is permitted:
  personal study, research, experiment, hobby projects and amateur pursuits,
  plus use by any charitable organization, educational institution, public
  research organization, public safety or health organization, environmental
  protection organization, or government institution — the last group
  regardless of the source of its funding. Free, with no time limit.

- **PolyForm Free Trial License 1.0.0** — `LICENSES/PolyForm-Free-Trial-1.0.0.md`,
  SPDX `PolyForm-Free-Trial-1.0.0`, granted in addition to the above. It permits
  evaluating whether the software suits a particular application for less than
  32 consecutive days on behalf of you or your company. It does not permit
  redistribution: it is for trying, not for shipping.

## Commercial use

Neither licence above permits commercial use beyond that 32-day evaluation.
Commercial use means anything done for commercial advantage or monetary
compensation — including embedding the software in a product or service offered
to third parties for a fee, whether or not raster-to-vector conversion is the
part being charged for, and including a company's own internal business use.

There are two ways to obtain it, depending on where the software runs:

- **You run it** — self-hosting an image, embedding a package, or using the CLI
  in a business. This needs a separate written licence from the copyright
  holder. Ask: sergey@dudko.dev

- **We run it** — the hosted service at vectorize.dudko.dev and its API. Paid
  accounts are not open yet. When they are, buying an account will carry
  commercial permission to use that service, on the terms presented to and
  accepted by the buyer at the time of purchase. It will not grant the right to
  run the software yourself; that is the first door.

## Nothing on the web grants a licence

Rights under this licence come from this file, and from a written agreement
signed by the copyright holder. They do not come from a web page.

No document published at any address — vectorize.dudko.dev included — grants,
widens or varies any right in this file, and no such document is incorporated
into it by reference. Where a hosted service has terms, those terms govern that
service for the person who accepted them; they say nothing about the software,
and they cannot be relied on by anyone else.

This is deliberate. A licence that took its terms from whatever is published at
a URL would be a licence whose terms could be changed by whoever holds that
domain, and a licensee could not know at the moment of accepting it what they
had accepted. Neither should be true of a licence.

## The licensor

The copyright holder is **Siarhei Dudko**, reachable at **sergey@dudko.dev**.

The address and the website are conveniences for reaching that person; they are
not the identity, and a message going undelivered neither grants a licence nor
removes the need for one.

## Why the service will need its own terms

A licence governs software someone receives. Terms of service govern a service
someone uses. The hosted site is both — it delivers the web application and the
WebAssembly modules to the browser, and it provides a conversion service — so
the service half needs its own document: what the free tier includes, what a
paid account grants, what happens to uploaded images, and the limits of
liability. Where the two touch, this file governs the software and those terms
govern the service.

## Third-party code

The wasm modules statically link third-party Rust crates — among them VTracer
and visioncortex, and the image codecs `image`, `png`, `zune-jpeg` and
`miniz_oxide` — under permissive terms (MIT, Apache-2.0, BSD, Zlib, Unlicense,
Unicode-3.0). None of them restrict the terms above, and each keeps its own
notice requirements. Those notices are reproduced in
`packages/core/THIRD-PARTY-NOTICES.md`, which travels with the npm package and
with both container images; regenerate it with `pnpm notices` whenever the
dependencies change.