Developer Terms & Conditions

1. Acceptance

By submitting a developer application, publishing a plugin, or otherwise using the CableKnit developer tools (including the CLI, MCP server, developer portal, and sandbox), you agree to these terms. If you do not agree, do not use the platform.

2. Developer Accounts

Developer access requires an approved application. Upon approval, you receive a publisher account, a sandbox environment for testing, and access to the CableKnit CLI. You are responsible for maintaining the security of your account credentials and API tokens.

CableKnit may deny or revoke developer access at any time, with or without cause. If your account is revoked, your published plugins will be removed from the marketplace and existing subscribers will be notified.

3. Plugins & Submissions

All plugins must comply with the App Guidelines. Every plugin submission is reviewed before it appears on the marketplace. CableKnit reserves the right to reject any submission for any reason, including but not limited to: empty or stub plugins, misleading descriptions, missing documentation, prompt injection or attempts to manipulate the AI runtime, duplicates of existing plugins with no differentiation, and pricing below the platform cost floor.

Submissions are reviewed for security, reliability, performance, and policy compliance. When you push a new bundle version to an approved plugin, it re-enters draft status and requires a new review before going live again.

You retain ownership of the plugin content you create. By publishing on CableKnit, you grant CableKnit a non-exclusive, worldwide license to host, run, display, distribute, and make available your plugin to subscribers on the platform. Subscribers receive a non-exclusive license to use your plugin for the duration of their subscription.

4. Plugin Execution & Runtime

Plugins run on CableKnit's runtime infrastructure within isolated, tenant-scoped environments. Your plugin's automations execute within the subscribing company's tenant context. You do not have direct access to subscriber company data — all data access is mediated through platform tools and connectors that the subscriber has explicitly authorized.

Each plugin may store up to 500 keys and 1 MB of data per subscribing company via the platform data store. Data store entries may include optional expiration times and are automatically cleaned up when expired.

CableKnit does not guarantee uptime or availability of the runtime. We will make reasonable efforts to maintain service, but automations may be delayed, interrupted, or fail due to infrastructure issues, third-party API outages, or other factors beyond our control.

5. Resource Limits & Fair Use

Plugins must operate within the platform's resource limits. You are responsible for ensuring your automations do not create runaway loops, consume excessive AI tokens, or make excessive API calls to connectors or external services. Automations should complete within reasonable execution times and avoid unbounded recursion.

CableKnit may, without prior notice:

• Pause or throttle a plugin that is consuming disproportionate resources
• Limit execution frequency or duration for automations that exceed fair use thresholds
• Suspend a plugin that is degrading platform performance for other users

You will be notified after any enforcement action and given the opportunity to address the issue.

6. Pricing & Cost Floor

You set the monthly subscription price for your plugin. All plugins must meet the platform cost floor, which is calculated based on the AI resources your automations consume. The cost floor accounts for token usage, a margin multiplier, and estimated monthly run volume. Plugins with no AI actions have a minimum cost floor of $3.00/month.

CableKnit reserves the right to adjust the cost floor calculation as infrastructure costs change. You will be notified of any changes that affect your plugin's pricing requirements.

7. Revenue Share & Payouts

You receive 80% of the subscription revenue from your plugins. CableKnit retains 20% as a platform fee. Revenue share is calculated on the gross subscription amount before payment processing fees. The platform fee percentage may change with 30 days' written notice to active developers.

Payouts are processed via Stripe Connect. You must connect a valid Stripe account before publishing paid plugins. Transfers are initiated automatically when subscriber invoice payments are received — Stripe processes these transfers on a rolling basis, typically every 2-3 business days depending on your Stripe account's payout schedule.

CableKnit is not responsible for delays caused by Stripe, your bank, or other payment intermediaries. You are responsible for all taxes and reporting obligations related to your earnings.

8. Refunds & Chargebacks

CableKnit may issue refunds to subscribers at its discretion — for example, if a plugin fails to function as described, is removed from the marketplace, or a subscriber disputes a charge. When a refund is issued, the corresponding developer payout will be deducted or recovered from future payouts.

If a subscriber initiates a chargeback through their payment provider, the chargeback amount plus any fees imposed by Stripe will be deducted from your future payouts. Plugins with excessive chargeback rates may be suspended or removed from the marketplace.

9. Versioning, Rollback & Compatibility

CableKnit retains the last 10 versions of each plugin bundle. Older versions are automatically pruned and their bundle files deleted. You may roll back to any retained version at any time. Rollbacks re-validate and re-ingest the bundle. Your plugin's approval status is preserved during rollback — a live plugin stays live.

You should maintain backward compatibility when updating plugins wherever possible. Breaking changes that disrupt active subscriber workflows may result in negative reviews, increased support burden, or plugin suspension. If a breaking change is necessary, document it clearly in your version notes.

10. Logging & Monitoring

Plugin execution logs (tool calls, errors, automation events, bundle operations) are retained for 90 days and then automatically deleted. Logs are scoped to your plugin and do not expose subscriber company data. You may access logs via the CLI or developer portal.

11. Sandbox

Your sandbox is a simulated company environment for testing. It bypasses billing checks and is always active. Plugin bundles are automatically installed into your sandbox when pushed. Sandbox data is isolated from production and may be reset at any time. Do not store production or customer data in your sandbox.

12. Plugin Removal by Developer

You may remove your plugin from the marketplace at any time. However, to protect subscribers who depend on your automations:

• You must provide at least 30 days' notice before removal whenever possible
• Existing subscribers may continue using the installed version until the end of their current billing period
• CableKnit may freeze the last published version to provide continuity for active subscribers
• CableKnit may continue running the frozen version on its runtime for a reasonable transition period

Removing a plugin does not affect payouts already earned. No new subscriptions will be accepted after removal.

13. Abandoned Plugins

If a developer becomes inactive or unresponsive, and their plugin is actively used by subscribers, CableKnit may take the following actions to protect subscribers:

• Freeze the plugin at its last published version
• Apply security patches or critical fixes to the plugin
• Fork the plugin to maintain it under CableKnit's stewardship
• Transfer maintenance to another developer with appropriate notice

A plugin may be considered abandoned when:

• The developer has not responded to CableKnit communications for 60 or more days
• The plugin is causing failures in subscriber production workflows
• A security vulnerability has been identified and the developer has not responded

CableKnit will make reasonable efforts to contact the developer before taking any of these actions. Revenue share for an abandoned plugin will continue to be paid to the original developer's Stripe account for as long as the plugin remains in its original form. If the plugin is forked or substantially modified by CableKnit, revenue share terms may be renegotiated.

14. Suspension & Removal by CableKnit

CableKnit may suspend or remove a plugin after approval if it violates these terms or the App Guidelines, receives consistent negative feedback, or exhibits behavior not described in its listing. You will be notified with an explanation and given the opportunity to fix the issue and resubmit.

If a plugin is removed, existing subscribers will be notified and their subscriptions canceled. Any outstanding payouts for completed billing periods will still be processed.

15. Developer Suspension

CableKnit may suspend or terminate a developer account for:

• Publishing malicious plugins or plugins that compromise platform security
• Repeated policy violations after prior warnings
• Abuse of the platform, runtime, or sandbox environments
• Fraudulent activity, including manipulation of reviews, metrics, or billing

When a developer account is suspended, all plugins by that developer are removed from the marketplace. Existing subscribers are notified and subscriptions canceled. Earned payouts for completed billing periods will still be processed unless the suspension is due to fraud.

16. Security Requirements

Developers must:

• Prevent prompt injection and other attacks against the AI runtime
• Prevent data exfiltration or unauthorized access to subscriber data
• Use only approved platform tools, connectors, and APIs
• Respect tenant isolation — plugins must not attempt to access data belonging to other companies or plugins
• Not store sensitive subscriber data (credentials, payment information, personal data) outside the platform's data store
• Comply with the platform's data retention policies

CableKnit may audit plugin behavior at any time. Plugins found to violate security requirements will be immediately suspended pending investigation.

17. Prohibited Plugins

The following types of plugins are prohibited on CableKnit:

• Plugins that scrape, harvest, or collect data without explicit subscriber consent
• Plugins designed to send spam, unsolicited communications, or bulk marketing without opt-in
• Plugins that harvest, store, or transmit credentials or authentication tokens
• Plugins that contain or distribute malware, ransomware, or destructive code
• Plugins that attempt to bypass platform security controls or tenant isolation
• Plugins that facilitate illegal activity or violate applicable laws
• Plugins that impersonate other developers, companies, or plugins

18. Marketplace Ranking & Placement

CableKnit controls search ranking, featured placement, and category placement on the marketplace at its sole discretion. Ranking may be influenced by factors including install count, reviews, plugin quality, recency, and editorial selection. CableKnit may promote, feature, or de-emphasize any plugin without notice. Developers may not attempt to manipulate rankings through fake reviews, artificial installs, or other deceptive practices.

19. Intellectual Property

You retain all intellectual property rights to the plugin content you create. By publishing on CableKnit, you grant:

• To CableKnit: A non-exclusive, worldwide, royalty-free license to host, run, display, distribute, and make available your plugin on the platform, and to use your plugin name, description, and icon for marketing and promotional purposes
• To subscribers: A non-exclusive, non-transferable license to use your plugin for the duration of their active subscription

You represent that you have the right to grant these licenses and that your plugin does not infringe on the intellectual property rights of any third party. CableKnit's name, logo, and platform are trademarks of CableKnit and may not be used without permission.

20. Limitation of Liability

CableKnit is provided "as is" without warranties of any kind. CableKnit is not liable for lost revenue, data loss, or any damages arising from your use of the platform, interruptions to the runtime, or actions taken by subscribers. Your total remedy is limited to the fees paid to you through the platform in the preceding 12 months.