creating-a-plugin

To create a NeMo Platform plugin, use the standardized directory structure and pyproject.toml template, then install the package in editable mode. This ensures your custom services, CLI tools, and functions integrate seamlessly via entry-point definitions.

You register custom CLI subcommands and API functions in NeMo by implementing standardized entry-points within your plugin package. This surface registration process ensures the platform recognizes and routes requests to your new modular components.

Yes, you must implement authorization scopes for NeMo Platform plugins. The architecture requires adherence to specific class naming conventions and security configurations to ensure all custom plugin routes are correctly secured with authentication.

The best way to structure a NeMo plugin package is to follow the provided directory tree blueprint and pyproject.toml configurations. This standardized layout guarantees platform compatibility before you install and register your custom services and jobs.

Yes, you can add background jobs to the NeMo Platform using a custom plugin. The plugin architecture supports the development and registration of modular background jobs through standardized entry-point definitions.

NeMo plugin routes fail to integrate when standardized entry-point definitions or specific class naming conventions are not followed. Ensure your plugin package enforces proper authentication and authorization scopes for seamless platform integration.