Legal
Terms of Service
The rules for using The Deployer, including our Launch and Move offers. We have tried to write them so you can actually read them.
1. Who we are and this agreement
These terms are an agreement between you and The Deployer ("The Deployer", "we", "us"), a service operated from India.
They apply when you use thedploy.com, the app at app.thedploy.com and portal.thedploy.com, our documentation, the free public repository check, our MCP server and API keys, or any service we sell, including Launch and Move. By creating an account, running a check or placing an order, you agree to them. If you use The Deployer for a company, you confirm you can bind that company to these terms.
Our Privacy Policy, Refund Policy and Acceptable Use Policy form part of these terms.
2. What The Deployer does
The Deployer is a cloud deployment and operations platform. For a project you authorise, it can analyse source code, propose deployment architectures, create or modify supported resources inside a cloud account you connect, deploy application workloads, and provide operational tooling. The features available depend on your plan, application, cloud provider, region and what the product supports at the time.
The Deployer runs a control plane. Your application and its cloud resources are created in the cloud account you connect (AWS, Google Cloud, Microsoft Azure or DigitalOcean), unless a feature explicitly says otherwise.
- Your apps keep running without us. If you stop paying or close your account, what we created stays in your cloud account until you remove it. Plan limits apply to actions in The Deployer, not to apps already running in your cloud.
3. Eligibility and account security
- You must be at least 18 years old and give accurate information when you sign up.
- Keep your password and API keys safe. You are responsible for activity under your account. Tell us promptly at hello@thedploy.com if you think someone else has used it.
- One person per account. Team access is available on plans that include members.
5. Deployment approvals and automated actions
You start every first deployment of a project. Some infrastructure changes are presented to you for confirmation before they run. You are responsible for reviewing what is shown, including the account, region, architecture, network exposure, destructive changes and estimated cost.
These actions run without a separate confirmation each time, because you set them up or started them:
- Push-to-deploy redeploys (on plans that include it) of a live project when you push to the connected branch.
- Redeploys requested through our MCP server or API key tools on projects that are already live.
- Automated recovery during a deployment you started: bounded retries that may change configuration, rebuild, and commit fixes to your branch.
- Scheduled operations you set up, such as scheduled start, stop or resize.
6. AI-assisted features
AI may help interpret repositories, propose infrastructure, diagnose logs and suggest code or configuration changes. AI output can be incorrect, incomplete or unsuitable for your application. We apply non-AI checks to some privileged operations, but those checks do not guarantee that every deployment is correct or secure. Review material changes before relying on them.
- Code changes are committed to your branch so you can review them in your repository's history.
- You remain responsible for the code you deploy and for how your app handles your users' data.
7. Cloud costs and estimates
Your cloud provider bills you directly for infrastructure, network traffic, storage, managed services and other provider usage. Those charges are separate from anything you pay us, and we cannot refund them.
The Deployer may show cost estimates. Unless a feature explicitly says it is a hard, provider-enforced cap, an estimate or threshold is not a guarantee that spending cannot go above it.
Usage-based services can generate charges because of traffic, application behaviour, abuse, configuration mistakes or provider price changes. You should use provider billing alerts, quotas and account-level controls that suit your risk tolerance.
8. Plans and billing
- Plans. The Free plan and paid plans have the limits and features shown on our pricing page at the time you use them.
- Prices and taxes. Prices are shown in US dollars or Indian rupees. Taxes are added where the law requires.
- Terms. Paid plans are bought for a monthly or yearly term. If you cancel, you keep your plan until the end of the term you paid for, and it does not renew.
- Payment processors. Payments are handled by our payment processors. We do not receive your full card number.
- Price changes. We may change prices for future terms. We will tell you at least 30 days before a change affects a renewal. Founding prices stay fixed for as long as the offer says.
- Refunds. Our Refund Policy is part of these terms.
9. Launch and Move
Launch and Move are fixed-price offers in which we do the deployment work for you, inside your own cloud account.
Launch
Launch (and Launch + Secure) deploys a repository that is not yet live into your cloud account, with HTTPS, health checks, deploy-on-push and monitoring. A Launch is delivered when all of these are true:
- the deployment has completed;
- the intended app process is healthy;
- the verified public or provider address is reachable, where the app has one;
- we have given you a handoff.
The delivery window and the automatic refund if we miss it are set out in the Refund Policy.
Move
Move creates a new deployment and does not delete the original application environment. Traffic is switched only after you approve the cutover. A copied database can diverge after the cutover, so the original database is not automatically a complete rollback once new writes occur. The migration plan should describe database cutover and rollback limitations for your application.
- Database copy. If you give us your current database's connection string, we copy its data into your new setup by reading from it on your new server. We do not write to your original database, and we store the connection string encrypted.
Both offers
- Eligibility. We accept an order only for a repository our check can read and deploy. If we cannot deliver an order we accepted, you get a full refund.
- What we need from you. Access to the repository, a verified connection to your cloud account, and any configuration the app needs. The delivery clock pauses while we are waiting on you or on a limit set by your cloud provider.
- Changes to your repository. To make an app deployable, we may commit small deploy-readiness changes, such as a Dockerfile or a health check. Each one is listed in your repository's history and in your handoff.
- Security review. The repository exposure check included with these offers looks for common committed credentials and selected deployment-related risks. It is not a penetration test or a full application security review.
- What is not included. Writing new features, fixing application bugs unrelated to deployment, and your cloud provider's charges.
- Included Pro months. Each order includes three months of Pro, starting when you pay. If the order is refunded, the included months end at the same time.
10. Your code, content and data
Your code, configuration and data remain yours. You give us permission to copy, process and store them only as needed to provide the service to you, including sending relevant parts to our AI provider. We learn from deployment failures and fixes across projects to make the service more reliable, using records from which secrets and identifying details have been removed. We do not sell your code or data.
The Deployer, including its software, documentation and brand, belongs to us. If you send us feedback, we may use it without owing you anything.
11. Data protection
Our Privacy Policy describes how we process personal data. We do not publish a standard Data Processing Addendum yet. If you are a business customer and need processor terms, write to hello@thedploy.com; any addendum we sign with you forms part of this agreement.
12. Acceptable use
You must follow our Acceptable Use Policy. In short: no malware, phishing, spam or unlawful content, no attacking or scanning systems you are not authorised to test, and no abuse of free plans or shared resources.
Do not interfere with the service, access data belonging to other users, run denial-of-service tests, or attempt destructive security testing. Good-faith security research within our Vulnerability Disclosure Policy is permitted.
Do not copy, resell or reverse engineer the service except where the law allows it.
13. Third-party services and open source
The Deployer connects to services run by others, such as cloud providers, code hosts, domain registrars and payment processors. Their terms govern your use of them, and we are not responsible for their availability, pricing or actions.
The Deployer and the configuration it generates use open-source software, which is provided under its own licence terms.
14. Beta and preview features
Features identified as beta, preview, experimental or early access may be less reliable, change materially or be withdrawn. Do not use a preview feature for a critical production dependency unless you accept those limitations.
15. Service availability and support
Unless a paid plan or separate agreement includes a service level agreement, we do not promise a specific uptime or response time. No plan includes one today. We aim to answer support requests sent to hello@thedploy.com promptly.
Because your apps run in your cloud account, an interruption to The Deployer affects our tools (deploys, dashboards, the assistants), not the running apps themselves.
17. Suspension and termination
- You can stop using The Deployer at any time. There is no self-serve account deletion today; to close your account and delete your data, write to hello@thedploy.com or use the contact form.
- We may suspend or close an account that breaks these terms, fails to pay, or puts other users or systems at risk. Where we reasonably can, we will warn you first and tell you why.
- Closing an account does not delete resources in your cloud account. You can remove them from the app before you leave, or at your provider afterwards.
18. Disclaimers
We work to keep The Deployer reliable, but the service is provided "as is" and "as available". To the extent the law allows, we make no promise that it will be uninterrupted or error-free, or that it will meet every need you have. The only delivery guarantees we give are the ones in section 9 and in our Refund Policy.
19. Limits on liability
To the extent the law allows, we are not liable for indirect or consequential losses, lost profits, lost data, or cloud charges run up in your account. Our total liability for all claims relating to the service is limited to the amount you paid us in the 12 months before the event that gave rise to the claim. Nothing in these terms limits liability that cannot be limited by law.
20. Indemnity
You agree to cover our reasonable losses if a third party makes a claim against us because of the code you deploy, the content you serve, or your breach of these terms.
21. Governing law
These terms are governed by the laws of India, and the courts of India have jurisdiction over any dispute. Before starting a formal dispute, please write to hello@thedploy.com so we can try to resolve it.
22. Changes to these terms
We may update these terms as the service changes. If a change materially affects you, we will tell you by email or in the app at least 14 days before it takes effect. Continuing to use The Deployer after that means you accept the updated terms.
23. Contact
Questions about these terms: hello@thedploy.com. Help with your account: hello@thedploy.com. You can also use the contact form.