Partner Guide

For module authors who publish their own modules to RAD and earn a revenue share when others deploy them. New to RAD? Start with Using RAD.

A Partner is always also a User, so everything in Using RAD — signing in, navigating, deploying, managing deployments, and credits — applies to you too. This guide covers the extra things only Partners can do.

The Partner role is assigned manually by an administrator. Subscribing to a plan grants credits but does not make you a Partner. If you need Partner access, ask an administrator.

What you can do

• Connect your own GitHub repository so RAD can read your modules.
• Sync your modules into the catalog from your repository.
• Deploy your own modules for free, alongside platform modules and other partners' public modules.
• Earn a partner revenue share when others deploy your modules, and see each payout Finance records for you.

After you sign in you land on Solutions, on Build Solution with AI, whatever your balance. Your top navigation shows: Credits, Sync, Deployments, Solutions, Pricing, Help. The module catalog lives on Solutions → Solution Catalog → RAD modules; it no longer has its own menu entry. Sync appears only once you have selected a module repository in your profile — until then it is hidden from the menu.

Connecting your GitHub repository

Before you can sync anything, connect the repository that holds your modules. Open the profile dropdown (top-right) and go to Profile. There are two steps, and the second is easy to miss:

1. Under RAD Module Sync App, click Install App and install the RAD Module Sync GitHub App on the repository (or organization) that holds your modules. The App grants RAD read access — no personal access token is needed.
2. Under Partner Settings, choose that repository from the GitHub Repository dropdown and click Update Repo.

Until the second step is done, RAD does not know which repository is yours: Sync stays hidden from your navigation and Solutions → Solution Catalog → RAD modules shows no Partner tab. Note that leaving the dropdown on Use platform default and saving clears your repository rather than setting one.

Deploying your modules needs one step from an administrator. The GitHub App lets RAD read your modules so they can be synced and listed. Building a deployment of one of your modules — by you or by anyone else — additionally needs deployment access to your repository, which an administrator sets up for each partner. Until they have, a deployment of your module stops before it starts with "Deployment repository credentials are not configured". Ask an administrator to enable deployments for your repository when you are ready for your modules to be deployed.

Syncing your modules

Go to the Sync page to bring your modules into the catalog. The page is a read-only sync console:

• It lists the valid modules found in your connected repository.
• Click Sync Now to refresh the catalog from your repository. Synced modules appear in the catalog for users to deploy.
• To update a module, change it in your repository and run Sync Now again — modules are managed in GitHub, not edited in RAD.
• Removing a module from your repository and re-syncing removes it from the catalog. You can only affect your own modules — never another partner's or a platform module.

If a repository can't be read — the GitHub App isn't installed on it, or it holds more module directories than the platform allows — the Sync page names the repository and explains why. Problems inside an individual module are quieter: a module whose variables.tf can't be parsed is skipped and left exactly as it was, and a directory that declares no public_access variable is treated as a helper and never listed. A module whose name already belongs to another partner or to a platform module is not synced either, so it can never take over someone else's catalog entry. None of these is reported back to you, so if a module you expected doesn't appear after a sync, check its variables.tf and its name in your repository.

How your modules appear to users

On Solutions → Solution Catalog → RAD modules you see two sub-tabs:

• Partner modules — the modules you've published from your own repository. This is your workspace for testing and iterating.
• Platform modules — modules published by RAD, plus other partners' public modules.

Everyone else sees a single combined catalog of public modules. Each module card shows the description, a documentation link, an average star rating, how many times it's been deployed, and its price: the module fee (or Free module when there is none) plus an estimate of the build.

Deploying your own module waives the module fee — the module's own credit cost isn't charged when you deploy it yourself. The build cost is still metered after the build and deducted from your balance exactly as it is for everyone else, so a self-deploy isn't entirely free.

Earning revenue

You earn a partner revenue share when other users deploy your modules. The share is calculated on the module's own credit cost only — build cost is excluded — and only on the part of that cost a user paid for with purchased credits, so a deployment settled entirely from awarded credits earns you nothing. Where the customer is charged VAT, your share is worked out on the fee before VAT. A deployment a subscriber makes for their client through Client Projects is paid from a wallet funded with purchased credits, so it earns you your share in full.

Track it on the Credits page, on the Module Revenue tab. There is no separate Revenue page any more, and no referral tab for partners — partners earn on their modules, not on referrals. The dates open on the last 7 days and the table loads on its own; change them if you need to, and use the refresh button to reload. You see only your own modules — there is no partner picker. Export to CSV downloads the whole filtered set, not just the page on screen. Finance also has an org-wide view on Billing → Module Revenue.

The revenue shown there is worked out at the current revenue-share rate. Once Finance has paid you for a period, that payment is recorded with the rate and amount as they were when you were paid, so a later change to the rate never changes what you have already been paid.

Payouts

Finance pays partners outside RAD, then records each payment in RAD. Below the revenue table on Module Revenue, the Payouts section lists every payment recorded for you: the period it covers, the module revenue and any setup-request earnings in it, the rate used, the payment reference, and the date it was paid. If a period you expected is missing, contact Finance through Help → Send Message.

Setup requests

If Finance assigns you as the engineer on a customer's setup request, you earn a share of the revenue from that request when it is completed: 75% by default, with the platform keeping 25% (Finance can set a different platform share). Your completed setup earnings appear in the Setup support earnings table beneath Payouts and are included when Finance records a payout. There is no partner screen for working setup requests themselves — Finance and administrators manage them and assign the engineer.

Monthly partner credits

An administrator or Finance can give you a monthly partner credit allowance. It is added to your awarded credits on the 1st of each month, appears in Credit Transactions labelled Partner award, and — like all awarded credits — expires at the next monthly reset.

Costs and invoices

Cloud costs and project invoices aren't available to Partners in the console — the Module Costs and Project Invoices tabs on the Credits page, and the whole Billing page, are restricted to Finance and administrators. If you need the GCP cloud cost or an invoice for a project you own or deployed, ask the Finance team.

Everyday tasks (same as any User)

These work exactly as described in Using RAD:

• Solutions → Solution Catalog → RAD modules — browse the catalog, configure with either the Conversational Assistant (your default) or the guided Configuration Form, and launch.
• Deployments — track your deployments; open one for Outputs, Build Status, and build history; Update, Delete, or Purge; and rate modules.
• Credits — view your balance and Credit Transactions (with Export CSV), Buy Credits and manage subscriptions while the platform is selling credits.

Getting help

Open the Help page and use the Send Message tab to contact the support team; your tickets are on the My Tickets tab beside it. As a partner you hold a staff role, so you can raise a ticket without purchased credits. The ROI calculator, for estimating your savings, is a tab on the Credits page. The Contact Us link in the footer also goes to Help.