Skip to main content
You wrote your plugin and you keep the rights to it. The registry is one distribution channel among several and does not change who owns or licenses what. How you sell, support or license your plugin is between you and your users.

​
Declare a licence

Declare the licence in the manifest with an SPDX identifier or expression:
For SPDX ids see spdx.org/licenses. For a custom licence use the LicenseRef-<your-id> form and ship the full text in the archive as LICENSE.txt. The agent does not gate installs by licence; operators see the declared string in the install review.

​
The SDKs are GPL

The agent is GPL-3.0-or-later and Mission Control is GPL-3.0-only. The plugin SDKs are GPL-3.0-or-later too, and that matters more than the process boundary:
  • A GCS bundle built with @altnautica/plugin-sdk contains SDK code.
  • A Rust agent half statically links the ados-sdk crate.
  • A Python agent half imports ados.sdk inside the agent’s GPL plugin runner.
The agent runs every agent half as its own subprocess over a defined IPC surface, and Mission Control runs plugins in a sandboxed iframe that talks over postMessage. No plugin runs in-process. Even so, get legal advice before shipping a plugin that uses the SDKs under a licence that is not GPL-compatible. Altnautica is not your lawyer. A proprietary vendor library loaded by your plugin runs inside your plugin’s process. You are responsible for whether its licence allows distribution with your plugin; see Vendor binaries.

​
Distribution channels

Every registry submission is reviewed. OSS-licensed, clean-scanning submissions are marked ready for review; everything else is queued for closer review. See Catalog and registry.

​
Vendored binaries

Declare vendor binaries on the agent half with contains_vendor_binary and vendor_attribution (full schema on Vendor binaries):
  • Each attribution entry carries its own required license. Ship the full licence text in the archive too.
  • Your plugin’s own license is independent of the vendor’s.
  • ados plugin lint does not inspect vendor binaries; you are responsible for what you ship.
  • Operators see the attribution in the install review.
If a vendor licence forbids redistribution, the registry cannot host the plugin.

​
Trademarks

The names “ADOS” and “Altnautica” and the Altnautica, Mission Control and Drone Agent logos are reserved. Do not use them in a plugin name, description or icon. You may state compatibility (“Works with the ADOS Drone Agent”, “for ADOS Mission Control”), link to the docs, and declare compatibility.ados_version in your manifest. Your reverse-DNS plugin id (com.your-name.something) makes namespace ownership explicit.

​
The registry’s role

The registry redistributes signed archives that publishers upload and does not modify their bytes. Its submission scan is a defense-in-depth measure, not a quality endorsement or a security audit. A plugin’s runtime behavior is its publisher’s responsibility.

​
No warranty

The agent (GPL-3.0-or-later) and Mission Control (GPL-3.0-only) carry no warranty. Plugins distributed through the registry come with no warranty from Altnautica; your plugin’s licence governs what you warrant. Verified-publisher status is set by the registry operator and is not a warranty. The catalog is served from the Convex backend; a self-hosted backend serves its own catalog. No availability terms are published for the hosted registry. Security reporting is on Revocation and incidents. Give your own users a private reporting channel in your plugin’s README.

​
Next steps

Publish to ADOSExtensions

Contribute a plugin to the first-party repo.

Revocation and incidents

Report a security issue.
Last modified on October 11, 2026