Developer agreement

Terms for publishing tools on Routines.

Draft — not legal advice

This page describes how the platform is built to behave. It has not been reviewed by a lawyer and must be replaced with counsel-drafted terms before taking real payments.

Ownership

You keep all rights in your tool. Publishing grants Routines the right to host, package, protect, distribute and market it as part of the platform, and to execute it on behalf of licensed customers.

Commission

Routines retains 30% of each transaction unless a different rate is agreed in writing. The rate applied is recorded on every order as charged. Payment-processing fees come out of the platform share.

Packaging and protection

Routines may transform your submission for execution: wrapping it in an integration layer, generating a manifest, obfuscating assemblies, encrypting the package, and normalising paths and error reporting. Routines does not modify your business logic.

Review

Publication requires passing review. Review checks function, contract, compatibility, security and documentation against a published checklist. A rejection states its reason and can be appealed.

Your obligations

Declare compatibility honestly; unverified versions must be marked as such.
Do not collect user or model data beyond what the tool needs to function, and declare what you do collect.
Respond to support within your declared support level.
Do not attempt to move customers off-platform.

Termination

Either side may end the arrangement. Existing subscriptions run to the end of their current period so that customer workflows are not broken mid-project.