Building a paid Amplenote plugin

Amplenote has built infrastructure that allows a plugin to charge a monthly fee for use, like Agent Pro (our AI plugin) does. This document describes how a developer can build a plugin to be monetized through Amplenote's plugin directory.


linkCode requirements for paid plugins

In order to preserve Amplenote's core values of transparency & security, we require any potential plugin to be audited on the following prior to being released as a paid plugin.


linkRequirements

To be eligible as a paid plugin, the following requirements must be met.


link1. Code visible

Read access to the source Github repos must be granted to the amplenote-team user on Github.


link2. AI audited

Copy the code from the following Copy/pasteable review prompt, and run it from the root of the plugin’s source repository using a code-capable AI agent that can inspect every file. The exact executable artifact submitted to Amplenote must also be present in the repository or identified to the agent.


Commit both generated files without deleting findings or changing their conclusions:

AMPLENOTE_PLUGIN_SECURITY_REVIEW_[month]_[year].md

amplenote-plugin-data-practices-[month]-[year].json

You may add developer responses beneath findings, but you may not remove the original finding. Resolve all Blocker findings before submission. The review must be regenerated for every month that a new published plugin version is released.


Amplenote may independently regenerate the review, compare it with your submitted review, and reject a plugin whose source, built artifact, disclosures, or review do not agree.

link3. Elective work

The more ideas you have to help users believe that their data is going to be private, the higher your conversion rate is going to be among users. We suggest you think about other safeguards you can show to prove to customers that they can trust you with their data.


linkOther requirements for paid plugins

In addition to code requirements, there are a few auxiliary expectations to be met.


link4. Refund rate below 5%

Amplenote does not have a streamlined process to handle refunds for paid plugins, so we need to work with plugins that can clearly set expectations for their users, such that they are not inclined to contact our support to request a refund.


link5. Offer an evaluation version

During this beta phase of development, it is not possible to offer a single plugin that works initially before allowing the user to consummate a purchase. Thus, we request that authors release a free version of their plugin that customers can use to evaluate the functionality and substantiate that they will be satisfied with their purchase.


linkRevenue share

We offer 70% of the revenue Amplenote collects for a plugin back to the developer. It will be paid net 60 days, after we have handled any refunds or chargebacks that may originate from the payment processing.


We encourage developers to propose the price for their plugin to us at hello@amplenote.com, where we will collaborate to choose a final price that can maximize user purchases.