The terms that govern your use of the RAD platform and our services.
Last Updated: 1 October 2026
These Terms of Service ("Terms") govern your access to and use of the RAD (Rapid Application Deployment) platform, our websites, and related services (together, the "Services") provided by Tech Equity Cloud Services Ltd, a company registered in England and Wales under number 13561408 ("Tech Equity," "we," "our," or "us"). By accessing or using the Services, you agree to be bound by these Terms. If you are using the Services on behalf of an organisation, you represent that you have authority to bind that organisation, and "you" refers to that organisation.
RAD is a web application that simplifies the deployment and management of enterprise-grade cloud platforms. RAD deploys infrastructure using pre-built blueprints into Google Cloud, which is the only cloud provider the Services currently support. Support for further providers may be offered in future, but no such support forms part of the Services unless and until we state otherwise in writing. Deployments may run in Google Cloud projects that you own and control, or in projects provisioned and managed by us on your behalf. Using a project we manage requires a verified email address and the minimum purchased-credit balance described in Section 14.2. Where we provision and manage the project, the additional terms in Section 14 also apply, and they describe controls and automated actions that do not apply to projects you hold directly with Google.
Beta release. The Services are currently offered as a beta release, ahead of general availability. Features are under active development: some are incomplete, may change or be withdrawn without notice, and may not function as described. Interfaces, pricing structures, credit mechanics, and the module and solution catalogue may change between releases. You should not rely on the Services for production workloads without independently satisfying yourself that they meet your requirements, and you should maintain your own backups and recovery arrangements for anything you deploy. The disclaimers in Section 9 and the limitations in Section 10 apply with particular force during the beta period.
The Services are built on, and in some cases resell, third-party cloud infrastructure. Your use of the Services is therefore additionally subject to the terms of the underlying cloud provider:
We do not control, and are not responsible for, changes the cloud providers make to their services or terms. We will pass through provider terms as they are updated by the provider.
To use the RAD platform you must create an account with accurate, complete information and keep it up to date. You are responsible for safeguarding your account credentials and for all activity under your account. Notify us promptly at admin@techequity.cloud if you suspect unauthorized use of your account.
The Services are offered under the subscription tiers described on our pricing page. Subscription fees are billed in advance for each billing period and are non-refundable except where required by law or expressly stated otherwise. We may change our fees with notice effective from your next billing period.
Credits. Deployments are paid for in credits. You may receive free credits — a sign-up grant, monthly grants, referral rewards, and credits claimed with an event code — and you may buy credits by subscription or as a one-off top-up. The platform shows each balance separately. Free monthly grants are reset each month; event credits expire on the date shown when you claim them; subscription credits are replaced at renewal where the platform is set to do so, and otherwise remain until spent; top-up credits do not expire. Free credits are used before purchased credits, except where a module or charge requires purchased credits; Google Cloud usage in a RAD-Managed Project is always paid from purchased credits.
What a deployment costs. A deployment is charged the module's fee, which is shown before you confirm and is collected when the deployment first succeeds, plus build time, metered for each build at the rate shown in the platform. Updating a deployment carries no module fee. Whether a failed deployment is charged is a platform setting, stated in the price information before you deploy; at present a failed deployment is not charged. The figures in force are shown in the platform and on our pricing page, and may change under this Section.
Cloud infrastructure consumption charges are separate from RAD subscription fees. Where infrastructure runs in your own cloud account, the provider bills you directly. Where infrastructure runs in a RAD-Managed Project (Section 14), its Google Cloud usage is charged to your purchased credits as Google reports it, at Google's list prices plus our margin, converted to credits at the rate shown in the platform. Discounts and credits that Google gives us are not passed on.
You agree not to, and not to permit any third party to:
You retain all rights to the data, configurations, and content you submit to or deploy through the Services ("Customer Content"). You grant us the limited rights needed to operate the Services on your behalf, including deploying Customer Content to the cloud environments you designate. You are responsible for ensuring you have the necessary rights to the Customer Content and that its use with the Services complies with applicable law. Our collection and use of personal data is described in our Privacy Policy.
We and our licensors retain all right, title, and interest in and to the Services, including the RAD platform, blueprints, software, and documentation. No rights are granted to you other than as expressly set out in these Terms. Open-source components included in or deployed by the Services (such as OpenTofu) are licensed under their respective open-source licenses.
We work to keep the Services available and performant, but the Services are provided on an "as is" and "as available" basis unless a separate written agreement with us states otherwise. During the beta period described in Section 1, availability may additionally be affected by ongoing development work, and we do not offer an availability commitment or service level agreement unless one is set out in a separate written agreement with you. Scheduled maintenance, provider outages, and factors outside our reasonable control may affect availability. Support is provided through the Help page in the platform; we do not commit to a response time unless a separate written agreement with you does.
To the maximum extent permitted by law, we disclaim all warranties, express or implied, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Services will be uninterrupted, error-free, or secure, that any feature will reach general availability or be retained in its current form, or that deployment durations, credit costs or other figures observed elsewhere will be reproduced in your environment.
To the maximum extent permitted by law: (a) neither party will be liable for any indirect, incidental, special, consequential, or punitive damages, or for loss of profits, revenue, data, or business opportunity; and (b) our total aggregate liability arising out of or relating to the Services or these Terms will not exceed the amounts you paid to us for the Services in the twelve (12) months preceding the event giving rise to the claim. Nothing in these Terms excludes liability that cannot be excluded under applicable law.
You may cancel your subscription at any time, effective at the end of the current billing period. We may suspend or terminate your access to the Services for material breach of these Terms (including non-payment or violation of the acceptable use provisions) if the breach is not cured within a reasonable period after notice, or immediately where required to protect the Services, other customers, or our cloud providers. Upon termination, your right to use the Services ceases; provisions that by their nature should survive (including Sections 6, 7, 9, 10, and 12) survive termination. Infrastructure deployed into your own cloud accounts remains yours and is unaffected by termination of your RAD subscription, though you become responsible for managing it directly.
These Terms are governed by the laws of England and Wales, without regard to conflict-of-laws principles, and the courts of England and Wales have exclusive jurisdiction over disputes arising out of or relating to these Terms, except where applicable law provides otherwise.
We may update these Terms from time to time. When we do, we will post the updated Terms on this page and revise the "Last Updated" date above. For material changes, we will provide notice by email or through the Services before the changes take effect. Your continued use of the Services after changes take effect constitutes acceptance of the updated Terms.
This Section applies only where you deploy into a Google Cloud project that we provision and manage for you (a "RAD-Managed Project"), which you select when you deploy. It does not apply to deployments into a Google Cloud project you hold directly with Google. Where this Section conflicts with the rest of these Terms, this Section controls for RAD-Managed Projects.
14.1 The project is ours; what runs in it is yours. A RAD-Managed Project is created under our Google Cloud organisation and billed to our Google Cloud billing account. You do not hold a direct agreement with Google in respect of it, and you do not own the project itself. You retain your rights in the Customer Content you deploy into it under Section 6. Because the project is ours, the controls and automated actions described below are available to us, and they are the price of not having to hold your own cloud account.
14.2 Tiers. RAD-Managed Projects are offered in tiers. Each tier carries a monthly Google Cloud budget, a minimum purchased-credit balance you must hold before a project on that tier can be created, and its own set of restrictions. The tiers available to you, and the figures applicable to each, are shown in the platform at the point of deployment. We may change those figures with notice under Section 13.
14.3 Restrictions we apply. RAD-Managed Projects are created with organisational policies and guardrails that constrain what can run in them. These include, and may not be limited to: a restricted set of Google Cloud services and APIs; a restricted set of deployment regions; and a limit on how many RAD-Managed Projects you may hold at one time. Each tier also carries a monthly Google Cloud budget, which raises spend alerts; a budget notifies and does not block, so it is not a cap and we do not describe it as one. The control that actually interrupts a project is the automated suspension in Section 14.4. Some modules and solutions in our catalogue cannot be deployed into a RAD-Managed Project at all, either because they require a service the guardrails do not permit or because they are unsuited to the tier. These restrictions exist to bound the cost and blast radius of a project billed to us, they may change as we tune them, and a change may mean a module or region that worked previously is no longer available.
14.4 Automated suspension of billing. Where your purchased credit balance falls below the tier minimum, we may automatically disable Google Cloud billing on your RAD-Managed Project. This is done by an automated process without prior notice to you, and it will interrupt everything running in that project: services will stop, and resources that depend on continuous operation may be degraded or lost. Billing is re-enabled automatically once your purchased credit balance is restored, but we do not guarantee that any resource or data in the project survives the interruption, and restoring your balance does not restore anything that was lost while billing was disabled. You are responsible for maintaining a sufficient balance and for your own backups.
14.5 Retention — when a dormant deployment record is removed. We remove our records of a deployment only when all of the following are true. Each is a separate condition, and if any one of them is not met, we keep your record:
Records of RAD-Managed Projects themselves are excluded from this process entirely and are not removed by it.
What removal does and does not do. Removal deletes our records — the deployment record and the infrastructure-as-code state we hold for it. It does not stop, delete, or otherwise affect the cloud resources themselves. They continue to run, and:
14.6 Not for production, and no availability commitment. RAD-Managed Projects on our lower tiers are intended for evaluation, development, and training. They carry a monthly Google Cloud budget that raises alerts as spend approaches and exceeds it — alerts notify, and do not stop a workload — they are subject to the automated suspension in Section 14.4, which is the control that does interrupt a project, and no availability commitment or service level agreement applies to them. Do not place production workloads, personal data you cannot afford to lose, or anything requiring continuous availability into a RAD-Managed Project unless a separate written agreement with us says otherwise.
14.7 Deployments made for you by another user. Where an administrator creates a deployment on your behalf, the credits for it are drawn from your balance, not theirs, and the deployment is recorded as yours.
Lab sessions. A trainer may enrol you in a lab session, which gives each participant their own environment in a RAD-Managed Project for a set time. When creating the session, the trainer chooses whether they fund every participant's place or each participant buys their own; that choice cannot be changed once the session exists. If you buy your place, your payment is held until your environment's time starts and becomes non-refundable only then; if your environment never starts, your payment is returned to you when the session settles — unless your account no longer exists, in which case we retain it. Credits the session does not use are returned to the trainer. The trainer can see participants' email addresses and the status, time and credits of each environment, and can extend, end or remove environments in their sessions, but cannot read your environment's secrets or see deployments you create yourself. Lab environments, and the projects they run in, are deleted when your time or the session ends. If you do not want to take part, do not accept the invitation.
Questions about these Terms should be sent to admin@techequity.cloud with "Terms of Service" in the subject line, or by post to:
Tech Equity
16 Carew Close
Grays, Essex, RM16 6RZ
United Kingdom