Four ways to reach an answer. Pick the one that matches what you need.
Guides, the REST reference, and the Python SDK. Fastest route for anything about integrating.
Browse the docsOther add-on developers and the maintainers. Best for questions where a conversation is quicker than a ticket.
Join the serverarrow_outwardBugs and feature requests, tracked in the open against the repository.
Open an issuearrow_outwardAccount problems, ownership disputes, and anything you would rather not discuss in public.
Contact the teamYes. There are no tiers, rate limits, or premium plans. Update checking is infrastructure, and charging per seat for it would defeat the point.
Create an account, open the dashboard, and choose Register add-on. The ID has to match the one in your blender_manifest.toml. You get an API key immediately.
Submit an ownership dispute from the registration page with evidence — GitHub history, a marketplace listing, prior releases. It goes to review rather than to whoever registered first.
No. LEUC tells users a new version exists and links to it. You keep hosting and distributing the files yourself, on Gumroad, GitHub, Superhive Market, or anywhere else.
Drop the Python module into your add-on folder, import it, and call it with your API key and current version. The integration guide in the docs walks through it.
An optional Blender add-on that checks every installed add-on at once in a single request. It is what end users install; you do not need it to publish.