Nativify hosted builds

Nativify protects eligible Java methods by compiling them to native code for the targets you request. A hosted build is an asynchronous, paid operation: package and test an unsigned JAR or ZIP, smoke-test that exact input, submit it, wait for SUCCESS, smoke-test the protected artifact on every release target, then sign, attest, and publish those protected bytes.

The hosted API defaults to disable-annotation-check only when no explicit features, owned processor preset, or project defaults resolve a feature list. That fallback attempts every eligible method; it is not a promise that every method can be compiled. Constructors (<init>) and class initializers (<clinit>) are protected through generated static native helpers, while abstract methods remain ineligible. Test real application paths before release.

Every build receives a private hosted path, including builds that do not supply hostingPath. The default is artifacts/{taskId}/native.jar; hostingPath customizes the route address but never changes its authorization. Authenticate with a dashboard JWT or an nfy_ key carrying artifact:read; the server also authorizes the exact task and its owner/resource boundary. The response is a private, non-cacheable attachment.

This guide describes the human integration contract. Swagger UI and /v3/api-docs are useful discovery surfaces, but do not generate a production client from the raw OpenAPI document without independently validating it against the running service.