What's the difference between a custom classifier and a built-in one?

A built-in is a classifier Tessary ships and runs. A custom classifier is an extension: code written against the open classifier interface, loaded onto the classifier pipeline, scoring a property no built-in covers and filing findings the same way a built-in does.

The interface is a set of small ports. One scores a span or a turn, one runs a leased pass over a larger unit and writes findings, one serves those findings into triage, one applies a human’s correction to them. An extension implements as many as it needs and no more.

The limit is where it can run. An extension jar goes on the classpath of a backend the operator runs themselves, and a classifier loaded into that JVM sees every bean and every tenant’s rows in it. Tessary’s hosted cloud runs only the classifiers Tessary ships, and nothing in the platform trains or fine-tunes a classifier on your traffic.