User Guide

This guide is for anyone using RAD to deploy and manage cloud modules — the default User role. New to RAD? Start with Using RAD.

What you can do

• Answer four plain questions on Build Solution with AI and have RAD work out which applications you need, what the whole thing costs, and deploy them.
• Browse the module catalog on Solutions → Solution Catalog → RAD modules and deploy ready-made modules through a guided form.
• Track and manage your own Deployments — view results and logs, update, and tear down.
• Manage Credits — check your balance, review your transaction history, and buy more while the platform is selling credits.
• Subscribe to a recurring credit plan, when plans are on offer.
• Estimate your savings with Calculate ROI, on the Credits page.
• Get help through the Send Message form on Help.
• Invite others with your referral link, from Profile → Refer and earn.
• Have RAD pay Google for a Google Cloud project you already own, from Credits → Linked Projects. See Linked projects.
• Run projects for your own clients (starting one needs purchased credits), or accept one someone runs for you, on Solutions → Managed Environments. See Client Projects.

After you sign in you land on Solutions: on Build Solution with AI if you have purchased credits (a subscription or a top-up), which is what unlocks it, otherwise on Solution Catalog → RAD modules. The tabs are, in order: Build Solution with AI, Solution Catalog, then Managed Environments, which holds client projects (while the platform offers them), lab sessions for trainers, finance and admins (while they are enabled), and anything someone else runs for you.

Solutions holds everything you can deploy, on two tabs:

• Build Solution with AI — four questions that end in a working, priced solution. Start here if you know what you want to achieve but not what it is called.
• Solution Catalog — everything ready to deploy, with a type filter across the top and a New solution button beside it that opens Build Solution with AI:
  • All — every kind on one page, each under its own heading; a kind with nothing to show is left out.
  • My solutions — the bundles you have composed yourself.
  • RAD solutions — ready-made bundles curated by RAD.
  • RAD modules — the full catalog of individual applications.

Your top navigation shows Credits (when credits are enabled), Deployments, Solutions, Pricing and Help, with an Ask AI button and a language selector (English or French) beside your profile menu. Ask AI opens an assistant you can question in plain language about modules, pricing and deployments; its answers can be wrong, so check anything important, and the conversation starts afresh each time you open it.

Building a solution from a description

Build Solution with AI and composing your own solutions need purchased credits (a top-up or a subscription; free signup, monthly and referral credits do not count). Partners always have them. Without purchased credits you still see both, locked, with a note on what unlocks them and a Buy credits button while the platform is selling credits, and any solutions you already saved stay listed: you can still deploy or delete them, but not edit them. Deploying for a client project you manage is the exception: the client's wallet pays, so it works whatever your own balance.

On Solutions → Build Solution with AI — also reachable directly at /build — describe what you want people to be able to do, in your own words, no app names needed. RAD works out which applications deliver it, then asks three short questions:

1. Where should it run? Your own Google Cloud project is the default: you keep the billing relationship, your organization's policies, and the project itself afterwards. Choosing a RAD-managed project instead puts the infrastructure inside RAD's own organization and billing account, and you then also say what the environment is for — trying things out, for your developers, or for your end users. A RAD-managed project also asks you to be holding a minimum balance of purchased credits, which the page states. That is a balance requirement, not a charge.
2. Where should it live? Pick the location closest to the people who will use it. Your own project can use any Google Cloud region; a RAD-managed project offers the locations RAD supports — the cheapest in each part of the world. RAD checks this again when you deploy: a location outside that list, in any location setting (including one that takes several locations), is refused before anything is reserved or built, and the message names the setting to change.
3. What should we call it? A name for your own reference, plus a short name (up to seven letters or numbers) used inside your cloud resources. Reuse that short name later to share the same cloud resources.

If the applications RAD proposes aren't quite right, use Not quite? Tell us what to change underneath them — say what to add or drop, and RAD reworks the set instead of starting from scratch. You can also remove a single application, or Start over to clear your answers and the proposal together.

A panel beside the questions shows what you'll get, what it costs and how long it takes — the whole cost, including the shared services RAD adds for you, split into what is taken when you build and what is metered as each part finishes, alongside a build-duration estimate such as "about 1h 20m". Build this saves it under My solutions and opens its deploy page with your answers already filled in; review it there and choose Deploy Solution. Show the engineering detail saves it the same way but opens it on the full configuration form, if you would rather set everything yourself.

Bringing your own Google Cloud project

Deploying into a project you already own means RAD's deployment service account does the work inside it, so it needs access first. Before anything deploys, you prove you control the project: choose Get verification code, run the commands shown as a project Owner (for example in Cloud Shell) — they add a verification label and give RAD read-only Browser access — then choose Verify; the code expires in one hour. You then grant the deployment service account the Owner role on the project; RAD names the exact account and shows the command. If another RAD account has already registered the same project, you are added to it as a collaborator. Free (awarded) credits can pay for a deployment into your own project.

Every deploy and update into a project you own starts with a quick check, before anything is changed: that the project exists and is active, that billing is enabled on it, and that RAD's deployment service account can turn on the Google Cloud services the module needs. If any of those fails, the build stops straight away and Build Status says which check failed and how to fix it, usually with the exact command to run. The check is skipped when the deployment creates the project itself, and it never blocks a deployment just because it could not get an answer.

What a RAD-managed project needs

A RAD-managed project asks for two things before RAD can create it: a verified email address, and a minimum balance of purchased credits for the purpose you chose. Free (awarded) credits — such as the ones you receive when you sign up — do not count toward that minimum. The page shows how many purchased credits you have against what is needed, with a Buy credits link, as soon as you choose the option. The header shows your balance split into purchased and free credits for the same reason.

Finding a module

Open Solutions, choose the Solution Catalog tab and select RAD modules in the type filter to browse the module catalog. Modules appear as cards.

• Browse: You see a single combined catalog of public modules — both modules published by RAD and public modules published by partners.
• Search: The search bar above the tabs searches the whole Solution Catalog — your own solutions, RAD solutions and RAD modules alike. Every word you type must match; a match in the name ranks first, then matches found in a description or in what a solution contains. Your search stays in place as you switch between types, and the counts on My solutions and RAD solutions show how many matches each holds.
• Filter by category: Use the category list beside the grid to narrow the catalog to one category. It appears when a single type (RAD solutions or RAD modules) is selected, and is hidden on All, because solutions and modules use different categories. Each entry shows how many modules it holds; All clears the filter.
• Page through: All shows four of each kind per page; a single type shows more (24 RAD modules or RAD solutions, 12 of your own solutions). Change the number per page, up to 72, beneath the list.
• Pin: Click the pin on a card to keep a favourite module at the top of your catalog for quick access.
• Read each card: Every card shows the module description, a documentation link, an average star rating, how many times it has been deployed, and its price.
• Read the price: Every catalogue card — module, platform solution or custom solution — shows its price the same way: the fee (charged once, when the deployment is created) plus an estimate of the build (metered on every build), for example 50 cr fee + ~19 cr build. A module with no fee reads Free module; its build is still charged. A solution that qualifies for a bundle discount shows it: the fee before the discount is struck through beside the fee you pay. A deployment into a RAD-managed project may also set up a project and shared services first; that cost is shown before you deploy.
• Get help on a module: Click Help on a card to open the Get Support dialog. It has three tabs: End User Support raises a support ticket about the module, End User Training requests paid help setting it up (RAD gets in touch within one business day), and Contact Publisher emails the module's publisher with a question.

A stats strip at the top shows total deployments, your current credit balance (when credits are enabled), and how long deployment history is retained.

Deploying a module

1. Choose how to configure it. Click a module card and pick Conversational Assistant or Configuration Form. The assistant is the default if you have purchased credits (partners always do); without them you get the form, and the assistant is shown but locked until you buy credits. Arriving from Build Solution with AI, a solution opens on the form, since the interview has just asked its questions. The assistant describes every setting in one go, then applies only the changes you accept — each proposed change is shown for you to apply individually, so nothing is set without your say-so. You can switch between the two at any time. Two things the assistant will not do: it never sees or sets a secret (an API key or password) — it tells you the field exists and you type the value into the highlighted box on the page, never into the chat — and it will not accept a value that breaks a field's own rule, telling you what the rule is and asking for a corrected one rather than quietly changing what you typed. Likewise, when the deployment goes into a RAD-managed project it refuses a region that project cannot use, and tells you which regions are allowed.
2. Open the form. The guided configuration form. The first time you deploy a module, the form shows only the essential (mandatory) fields — administrative and internal fields are hidden from you, and optional advanced configuration is deferred. You can unlock the full set of configuration steps later, from the deployment's Update action: tick Enable advanced mode, which is available once your credit balance covers the estimated cost of the update. Advanced mode carries no module fee — updates never do — and is not available on a lab environment.
3. Fill in the configuration. Complete the required fields on each step (for example, project and region). Move forward when each step is valid. The form is generated from the module itself, so where the module declares a rule for a field — a naming pattern, a length limit — you see that module's own error as you type rather than several minutes into a failed build. Fields holding a secret (an API token, a password) are masked and stored in Google Secret Manager rather than saved with the rest of your configuration; because the value never comes back to the browser, such a field shows Configured or Not configured instead, and leaving a configured one blank keeps it rather than clearing it. A field that takes a list or a map must hold one: a map typed as text is read as JSON, a blank one uses the module's default, and anything else is refused when you deploy or update, naming the field, rather than failing part-way through the build. Most application modules build their own container image: while Container Image Source is "custom", a note under Container Image says that field is ignored. Choose "prebuilt" to deploy the image you enter instead.
4. Confirm. The What will be deployed panel at the top of the form lists everything this deployment builds — in a RAD-managed project that includes the Google Cloud project and shared services — with what each one costs (one that already exists is reused, Free, reused), and marks any that is Will be updated first or Needs attention first; you cannot deploy while anything needs attention. Before launching, a confirmation dialog may appear — for example when the module costs credits, has dependencies, or needs special permissions. Review the details, including how many credits the deployment will cost.
5. Deploy. Click Deploy Module to queue the deployment. If you don't have enough credits, RAD shows the module's credit cost against your current balance and prompts you to top up first.

What happens next: Your deployment is queued and then provisioned on Google Cloud. RAD opens the deployment's own page on its Build Status tab so you can follow its progress; it is also listed on the Deployments page.

Deploying a solution

A solution deploys several modules together as one unit, in the right order, into a single tenant. Click Solutions in the top navigation. Ready-to-deploy bundles live on Solution Catalog → RAD solutions and Solution Catalog → My solutions; Build Solution with AI and Solution Catalog → RAD modules are described above.

RAD solutions are pre-composed by RAD — browse by category, open one to see its members, fill in the shared configuration once, and deploy the whole bundle. Members that depend on another wait for it automatically.

A solution with three or more members costs less than deploying the same modules one by one: its module fees are discounted by 15% for three or four members, 20% for five or six, and 25% for seven or more. The discount covers module fees only — build time, and a RAD-managed project's own costs, are charged as normal. The confirmation dialog shows the discount it applied.

Your own solutions (Solution Catalog → My solutions) are composed in conversation. Describe what you want to build — "I need a marketing site with a blog and email campaigns" — and RAD suggests modules from the catalog with a short reason for each. Add the ones you want (up to 12), give it a name, and save it. Your custom solutions are private to you.

• A saved solution shows Draft until you deploy it, then Deployed. A draft can be edited in place; once it has deployed, editing offers to copy it into a new draft instead, so the record of what you actually built stays accurate.
• Pin a solution you use often to keep it at the top of My solutions, just as you can pin a RAD solution or a module.
• Delete removes the saved solution only. It never touches infrastructure you have already deployed — tear that down from the Deployments page.
• RAD connects members to each other only where a known connection exists between those two applications. Where two members have no such connection, it says so on the card rather than guessing — they still deploy, you just wire them up yourself if they need to talk.

Managing your deployments

Click Deployments to see your deployments. Each row shows the module, the deployment ID, an editable star rating, when it was created, how long it took, the status, and the action. There's no project or credits column — open a deployment for its project, and its Builds tab for what each build consumed.

Deployment statuses include Queued, Pending, Working, Waiting (on a prerequisite deployment to finish), Success, Failure, Internal Error, Deleting, Deleted, Cancelled, Timeout, and Expire. A Deleted deployment stays in your list only while you can still purge it; a lab environment your trainer tore down, for example, drops out of your list because only the trainer or an administrator can purge it.

Open a deployment to see its details, which has these tabs:

• Outputs — starts with the page to open: First-time setup when the application needs setting up before its first use, Open application otherwise, or — for a module with no web interface — the API address to connect to. Below that are the rest of the non-sensitive results (such as addresses and endpoints exported by the module). These appear once the deployment succeeds.
• Build Status — live logs, useful for watching progress or troubleshooting a failure. Once the deployment has succeeded, Explain this opens a plain-English explanation of the Google Cloud resources it created, written for someone who does not read Terraform. It sends only the kinds of resource involved and how many of each — never your project ID, resource names, email addresses or any configured values. It also links the module's own documentation page, so the explanation is grounded in how that module actually works rather than in general knowledge. On a step that has failed, Search for a fix opens a search built from the actual error the step printed, and Ask for help raises a support request with that same output attached. If RAD already recognises the failure — or an AI suggestion has already been generated for this build — Ask for help shows that first and asks Does this solve it?: choose Yes, I'll try this and nothing is sent, or No, send to support and the diagnosis you saw goes with your request. Where a module's script failed, the search uses what the script printed rather than the script itself, and it leaves out what identifies you: email addresses, project IDs, service addresses, IP addresses and the names RAD gave your resources. Download saves the whole log as a text file, with secrets masked.
• Builds — the build history for the deployment.

From the details view you can also:

• Update — reopen the configuration form (pre-filled with the current values), change what you need, and re-apply. Available once a deployment has finished — succeeded, failed, timed out, been cancelled, or expired. Update also needs some purchased credits on your account: if you hold only awarded credits, RAD shows a Credits Required prompt instead of opening the form, with a Top Up Credits button to Buy Credits while the platform is selling credits.

  Two things can stop an update before you get to the form. If this deployment depends on another one that has failed, been cancelled or timed out, RAD refuses and lists the deployments to start first — fix those, then retry. (A prerequisite that is still building is fine: the update is accepted and parked until it finishes.) And if you edit a setting that cannot be changed on a running deployment — a region, an encryption key, a toggle that creates a resource — RAD raises a confirmation naming exactly which settings will destroy and rebuild resources. Where your administrator has switched on Enforce Update Safe, those fields are read-only instead, and the only way to change one is to delete the deployment and create a new one.

• Cancel — shown while a deployment is in Queued or Waiting, before it starts building. Cancelling releases it so you can try again, and a cancelled Waiting deployment also releases anything waiting behind it. The same button appears for a purge that has gone an hour without progress.

• Delete — remove the deployment. You get two choices:

  • Delete runs a teardown that destroys the cloud resources the deployment created. This includes a RAD-managed GCP project (the "GCP Project on RAD" option): because deleting it takes the whole project with it, RAD refuses while any other deployment is still running in that project and lists the ones to delete first. Google keeps a deleted project recoverable for about 30 days. Google Cloud's terms do not guarantee that a restored project will be usable, so a restore cannot be relied on to get a deleted project back: take appropriate backups of your data and configuration before you delete, and if a restore fails, redeploy the application and restore its configuration from those backups.
  • Purge removes the deployment from RAD without destroying the cloud resources. Use Purge when a deployment was changed outside RAD, or is stuck and Check status (below) cannot correct it.

  A deployment that is part of a solution can be deleted or purged only from the solution's page.

When a deployment fails

• A known cause is explained for you. When RAD recognises why a step failed — billing switched off on the project, a missing permission, a Google Cloud service not yet enabled, and many more — the failed step on Build Status says what went wrong and what to do about it. The failure email names the same cause and fix, so you often know what to do before opening the page.
• Suggested fixes. For a failure RAD does not recognise, Suggest fixes on Build Status asks AI for the likely causes and the steps to try, worked out from the build's error output with your secrets masked. It needs purchased credits on your account (or a staff role). RAD may already have prepared it by the time you open the page. Suggestions can be wrong: check them before acting.
• Apply suggested fix. Some suggestions include a change to one or two settings — for example more memory, more CPU, a higher instance count or timeout, a larger machine size, or another choice from a setting's own list. Apply suggested fix opens the update form with those values filled in and highlighted; nothing changes until you review the form and submit it. RAD only ever suggests simple settings like these that are safe to change on a running deployment — never an address, a container image, a command, a network range, a secret, a region, or anything to do with your project, billing or access. You get one suggested fix per failure: if the update it led to fails again, the button is no longer offered and RAD points you to support instead.
• Before you ask for help, RAD shows you what it already knows (see Build Status above), so you are not left waiting for an answer you could have had straight away.
• Deleting shared services. Deleting a project's shared services (Services_GCP) can fail while Google is still releasing the network addresses Cloud Run used — this takes about 20-30 minutes after the last application is removed. RAD retries that delete automatically, no sooner than 30 minutes later and at most twice, emails you that it is doing so, and Build Status shows when the next attempt runs. There is nothing for you to do.

When a deployment seems stuck

If a deployment has sat in Queued, Pending, Working or Deleting with nothing changing for 30 minutes, its page offers Check status. RAD asks Cloud Build whether a build is still running for that deployment:

• Nothing is running — the status is corrected straight away (RAD would otherwise do this at its next automatic check), and you can then delete or update the deployment as normal.
• A build is still running — RAD tells you when it will finish, or when Cloud Build will stop it at its time limit, so you know when to check again. A build that is only queued and has not started applying can be stopped with Cancel; one that is already applying is never stopped, because stopping it part-way can leave resources half-created.

Check status is offered to whoever may delete the deployment — its owner or an administrator, for example — and not to Support. A deployment that is Waiting on another one has Cancel instead, and one waiting for related deployments to finish continues on its own when they do.

To rate a module, go back to the Deployments list and click the stars on that deployment's row — the rating isn't set from the details page, and you can only rate deployments you made yourself.

Credits

Open the Credits page to manage your balance.

Your credits sit in four separate balances, and they behave differently:

• Awards — free credits: your signup grant, monthly grants, and referral rewards. These are reset each month.
• Event credits — free credits you claimed with an event code (see below). They expire on their own date, shown when you claim them, rather than with the monthly reset.
• Subscription — credits from a subscription plan. Where the platform is set to reset them, a renewal replaces the allowance rather than adding to it.
• Top-up — credits you bought outright as a one-off. These never expire.

Spending draws on awards first, then event credits, then subscription, then top-up — so the credits that expire soonest are used first, and the ones you bought outright are kept until last.

Deploying a module charges two things. The module fee is reserved when you confirm and charged when the deployment first succeeds — including when a failed deployment is later fixed by an update. The build cost is metered from how long each build actually runs, at the platform's credits-per-build-hour rate, and charged as each build finishes.

The confirmation dialog quotes the whole chain, not just the application you picked. Deploying into a RAD-managed project also creates your private Google Cloud project and the shared services your applications use, and those carry their own costs — the dialog lists them under "RAD also sets these up for you" with a combined total. It also separates what is reserved when you confirm from what is metered as each build finishes, so the second charge is not a surprise. Build costs are estimates until the build completes, so the final figure can differ a little.

Updating a deployment charges the build cost only.

VAT. If RAD's finance team has set a VAT rate for your account, it is added to every module fee and build cost you pay, and to the Google Cloud usage of your RAD-managed and linked projects. The confirmation dialog shows the net figures with a separate VAT line, and VAT must be paid from purchased credits — the dialog tells you how many more to buy if you are short. A rate change applies from your next deployment; it never re-prices one you have already confirmed.

Failed deployments. Whether a deployment that fails is charged is a platform setting rather than a fixed rule: Finance decides, separately for the build cost and the module fee, whether either is taken when a new deployment fails or is cancelled. In the current release neither is charged — a failed deployment costs you nothing. A failed update or teardown is not charged either.

The Credits page has these tabs:

• Credit Transactions — your full history of awards, purchases, and spend, with an Awards, Top-up, and Subscription balance after each entry. Filter by deployment and by date, and use Export CSV to download a report.
• Project Transactions (when project credits are enabled) — what each Google Cloud project cost you, one row per project, with a project search and a date range. A project charge lands on Credit Transactions as a single combined row covering all your projects at once; this tab is the breakdown of that charge.
• Linked Projects — ask RAD to pay Google for a project you already own. See Linked projects.
• Subscriptions (only while the platform is selling credits) — subscribe to a recurring credit plan, or cancel or reinstate the one you have.
• Buy Credits (only while the platform is selling credits) — top up your balance.
• Calculate ROI — the ROI calculator described below, always the last tab.

Whether credits can be bought at all is a single platform switch. While it is off there are no new subscriptions and no one-off top-ups, and the two tabs above are not shown; if you already have a subscription, a notice on Credit Transactions still lets you cancel it.

To buy credits: open the Buy Credits tab, pick a payment provider, choose a currency and amount, and complete checkout on the provider's secure page. The form shows the minimum top-up (set by RAD's finance team, in USD) converted into your currency, and the form tells you how many credits the amount will buy before you pay. Your credits are added automatically once the payment confirms.

Refunds and chargebacks. If a payment is refunded, or you dispute it with your card issuer (a chargeback), RAD takes back the credits that payment added, from the balance they went into — in proportion, for a partial refund. Your history shows it as a negative purchase line. That balance can go below zero, and then RAD switches off the Google Cloud projects it pays for on your behalf until you top up. If a dispute is decided in your favour, the credits are put back.

Some deployments require purchased credits (subscription or top-up, not awards or event credits) before you can start them — in that case, buy credits first even if you have a free balance.

Event codes. A RAD partner event may give you a code for free credits. Type it into the event-code box at the top of the Credit Transactions tab on Credits and choose Claim credits, or open the link the event gave you, which fills the code in for you (you still choose Claim credits). Each code can be claimed once per account and needs a verified email address; some codes are limited to particular attendees or email domains, and every code has a closing date. Event credits pay for module fees and build time, but not for Google Cloud usage in a RAD-managed project, and they do not count toward the purchased-credit minimum a RAD-managed project asks for.

Subscriptions

A subscription is an optional recurring plan that grants a set number of credits each billing cycle.

• Subscribe: choose a plan and complete checkout via your chosen payment provider. You can hold only one subscription at a time — to move to a different tier, or a different payment provider, cancel the one you have first and wait for it to lapse at the end of the current billing period.
• Cancel: stop future renewals. Your remaining credits stay available until you spend them.
• Reinstate: resume automatic renewals on a cancelled plan if you change your mind.

A subscription only grants credits — it does not change your role on the platform.

ROI calculator

Open Credits and go to the Calculate ROI tab to use the interactive ROI calculator. It comes pre-filled with your real recent activity (your deployments and spend) and lets you adjust assumptions — monthly deployments, manual deployment time, engineer hourly cost, and time-savings percentage — to estimate your labour cost, platform cost, net savings, and return on investment. It's an estimator only: it never deploys anything or charges your account.

Seeing what you've spent

You can see your own spending two ways on the Credits page. Credit Transactions lists every award, purchase, and deployment charge on your account, filterable by deployment and date. Project Transactions — available whenever project credits are enabled — breaks the project side of that down per Google Cloud project, showing the credits debited and the underlying cloud cost for each one over a date range you choose.

Platform-wide reporting is still restricted: the Module Costs and Project Invoices tabs and the whole Billing page are limited to administrators and finance users. If you need a formal invoice, ask through the Support form.

Linked projects

Credits → Linked Projects lets RAD pay Google for a Google Cloud project you already own and run yourself. You prepay credits, and RAD debits them hourly for the project's usage. The project keeps its ID, its data and your full control; RAD gets no access to your data or resources.

The tab first states your terms: your VAT rate (or that Finance will confirm one before linking), whether any of Google's own credits — free-tier allowances, usage discounts, promotional credits — are passed on to you (by default they are not, and usage is charged at Google's list price plus RAD's margin), and the floor: the minimum balance of purchased credits you must keep, shown against what you hold. Awarded and event credits don't count toward it.

To link a project:

1. Enter the Google Cloud project ID and choose Continue.
2. Confirm you own the project — the same label check used when you deploy into your own project (a project Owner or Editor adds the label). A project you have already verified is offered for you to pick.
3. Let RAD manage the project's billing link — run the two commands shown, as a project Owner. They give RAD's billing identity the Browser and Billing Project Manager roles: enough to attach or detach a billing account, and nothing more.
4. Cap your Gemini API and GPU quotas in the Google Cloud console, because those can spend faster than your balance can cover. Tick the box confirming you have granted both roles and capped the quotas.
5. Choose Request link. RAD's finance team reviews the request; the list below shows its status (Awaiting approval, Linking, Linked, Paused, Unlinking, Unlinked, Rejected, Withdrawn), and a rejection shows Finance's reason. You can send a request while below the floor, but it cannot be approved until you hold it.

While a project is linked:

• If your purchased balance falls below the floor, RAD pauses the project by detaching billing: its services stop, but your data is kept. RAD emails you before this happens, and buying credits back above the floor resumes it automatically.
• Withdraw cancels a request that has not been approved. Stop (behind a confirmation, Stop RAD paying) detaches RAD's billing account. If no other billing account is linked, the project's services stop — link your own billing account first if it must keep running. Linking your own billing account to the project also ends RAD's part.
• Usage up to the moment billing is detached is still charged once Google reports it.
• Stop finishes only once RAD has confirmed its billing account is off the project. If RAD can't detach it — for example because RAD's billing role was removed from the project — the project stays Unlinking, its usage is still charged to you, and RAD keeps retrying. You can't request a new link for it until that completes.
• Keep RAD's two roles on the project while it is linked. If RAD can no longer read the project's billing, it can't pause it, so until the roles are restored RAD won't resume any of your paused linked projects and can't approve a new link for you.

Approval checks the floor against your recent spend across all your linked projects, not only the fixed minimum, and checks you are still the project's verified owner. A project that RAD itself created or runs for you (a RAD-managed, lab or client project) can't be linked.

Deleting your account

Delete Account at the bottom of your Profile page removes your account permanently. It is refused, with the reasons listed, while your account still owes RAD or is responsible for something RAD is paying for: unpaid Google Cloud usage or build costs, a purchased-credit balance below zero, a client project you run that hasn't been ended and settled, a linked project RAD is still paying for or detaching, or a lab session you run that hasn't ended and settled. Settle those first. You must also delete any deployment that is still running. Your deployment records are kept after your account is deleted, so that late usage is still billed correctly; your credit history is kept for audits.

Email notifications

Choose which emails RAD sends you on your Profile page, under Email Notification Settings. Deployments covers every email about your deployments — build results, lab emails, and the warnings RAD sends before it permanently removes something of yours. Billing covers credit and payment emails. (Support staff also see Support ticket assigned to me.) One email ignores these settings: if a build costs more credits than you have, you are always told what you owe, because it explains why your next top-up gives you less.

Turning Deployments off stops all of those emails, including the warnings. Because RAD never permanently removes anything without warning you first, those removals are held while the setting is off: a RAD-managed project whose billing was switched off for lack of credits is not deleted, and a deployment removed from your list after the retention period is kept rather than permanently erased. When you turn deployment emails back on, the warnings are sent. For a held deployment record, the full notice period starts from that warning. For a held RAD-managed project, the project can be deleted as soon as the following day, so act on that warning straight away.

Client projects

When the platform offers it, client projects live on Solutions → Managed Environments, after the catalogues. It works from both sides.

Run for you. Everything someone else has set up for you — a place in a trainer's lab session, or a client project a partner runs for you — is listed together under Solutions → Managed Environments → Run for you, whichever kind it is. The Run for you view appears only while something is being run for you, including an invitation you haven't accepted yet. While you have that view open, the lab banner at the top of the page steps aside, since the same details are shown there.

If someone runs a project for you. A partner or another RAD user may invite you to a client project they run for you as a managed service. You'll get an email. Sign in with the exact address it was sent to, creating an account if you don't have one, and confirm your email address if RAD asks. Then open Solutions → Managed Environments → Run for you and choose Accept under Invitations for you.

• The project then shows under Projects run for you, and what they deploy for you appears in your Deployments. It's yours: they build and run it.
• You don't pay RAD for it. Its costs come from a balance the subscriber funds; anything between the two of you is agreed outside RAD.
• While they manage it you can see it, but only they can change or delete it. You can read its secret values, such as passwords and API keys; they can't.
• If their balance runs low, the project may be paused (nothing is deleted) and you're emailed. If it isn't topped up in time it's deleted, and you're told.
• At the end, they can hand it over to you. It then runs on your own credits, like anything you deploy yourself, and they no longer have access. You'll need enough purchased credits to keep a production project running.

If you run projects for your clients, see the Client Projects Guide. Starting one needs purchased credits; managing one you already run does not.

Getting help

Open Help and use the Send Message tab to raise a question or report a problem. Fill in the form to send your message — this raises a support ticket and notifies the support team, who follow up with you. Raising a ticket needs purchased credits (a subscription or a top-up) while credits are on sale; without any, the form shows a prompt to buy credits instead. While the platform is not selling credits, anyone can raise a ticket. Accounts holding a staff role — administrator, partner, finance, support, agent or trainer — never need purchased credits to raise one. You can raise up to 5 tickets in 24 hours. A Contact Us link in the footer also takes you to the Help page; to suggest an improvement instead, use the Feedback link beside it, which opens RAD's public feedback board.

Your tickets are on the My Tickets tab, next to Send Message, newest first: each shows its status (New, In progress, Resolved or Closed), subject and the date you sent it, and expanding one shows its category, priority, module, the date it was resolved and your message. Refresh reloads the list. Sending a ticket takes you straight to this tab, so the one you just raised is what you see.

If you no longer need help with a ticket that isn't closed, expand it and choose Withdraw ticket, then confirm. The ticket is closed and shows as Withdrawn, and Support sees that you withdrew it, so nobody keeps working on it. It isn't deleted: it stays in your list. You can raise a new ticket at any time.

Inviting others

Your referral link is on your Profile, in the Refer and earn section (the Credits page also has a Referral link button that takes you there). People who sign up through it are linked to your account, and you earn referral credits for them, subject to any monthly limit the platform sets. The section shows how many of your referrals earned you credits this month and in total — a count only, never who they are. It is hidden only when the platform has turned referral rewards off.