These terms govern RD role requests and controlled access to Rotorcraftory's defense, autonomous systems, cloud, product, rental, and managed-operation programs.
Last updated: July 29, 2026
Do not submit classified, secret, export-controlled, operationally sensitive, or third-party-confidential information through the public access-request form. Begin with a high-level institutional use case.
These terms apply to institutional access for RATS (Rotorcraftory Advanced Tactical Systems), RADS (Rotorcraftory Advanced Defense Systems), RDOS (Rotorcraftory Defense OS), MAVLink Cloud, Fleet Telemetry Cloud, mission-planning workflows, agricultural analysis, UAV and ROV deployments, AI-assisted operations, products, subscriptions, demonstrations, rentals, pilots, and related services provided by Rotorcraftory Private Limited.
The public defense page is a high-level capability overview. Detailed specifications, pricing, technical documentation, software access, demonstrations, product onboarding, procurement discussions, fleet data, and operational workspaces require an approved RD role and may require additional product, subscription, confidentiality, or commercial agreements.
RD access is intended for eligible companies, commercial operators, research or educational institutions, government bodies, public-safety teams, critical-infrastructure programs, and defense organizations. It is not a general consumer product catalogue. Submission does not guarantee approval; Rotorcraftory may approve, deny, defer, limit, or condition access after suitability and compliance review.
Applicants must be pursuing a lawful, authorized institutional or commercial use. Programs involving Indian airspace, unmanned aircraft, radio links, data collection, autonomous systems, payloads, or remote vehicles remain subject to all applicable laws, permits, airspace controls, spectrum requirements, organizational approvals, and competent-authority directions.
References to DGCA-aligned or compliance-aware mission planning describe intended workflow support only. They do not represent DGCA ownership, certification, endorsement, authorization, or approval of Rotorcraftory, RDOS, an aircraft, an operator, or a mission. The operator and institution remain responsible for obtaining and maintaining every required permission.
Rotorcraftory operates as a supplier, technology developer, integrator, rental or managed-service provider, and program-support partner as stated in the applicable written agreement. Rotorcraftory does not assume the role of regulator, airspace authority, mission commander, or prime contractor unless expressly agreed in a signed contract.
By requesting access, you confirm that your identity and organization details are accurate, you are authorized to represent the stated organization or program, and the use case is lawful. Submit only unclassified, non-secret, high-level information. Do not submit classified, export-controlled, operationally sensitive, restricted, or third-party-confidential material through the web request form.
RATS, RADS, RDOS, software, interfaces, architecture, workflows, designs, documentation, media, benchmarks, prototypes, training material, and in-house products remain proprietary to Rotorcraftory Private Limited unless expressly licensed in writing. Access does not grant ownership or a right to copy, reverse engineer, disclose, resell, or create derivative products.
Rotorcraftory capabilities must not be used for unlawful surveillance, unauthorized intrusion, prohibited weaponization, harmful deployment, privacy violations, unsafe flight, or any activity barred by applicable law or contract. Rotorcraftory may refuse mission categories, payloads, locations, integrations, or counterparties that create unacceptable legal, safety, or ethical risk.
RD access does not itself authorize autonomous flight, payload carriage, delivery, or beyond-visual-line-of-sight operations. Each operation is subject to mission-specific review of the aircraft, crew, operating area, communications, contingency plan, payload, weather, insurance, airspace permissions, and applicable regulatory approvals. Availability may be limited to trials, simulations, supervised programs, or approved corridors.
Aircraft, payload, sensor, communications, and support rentals require a separate written rental or managed-service agreement. That agreement may define trained operators, permitted locations and missions, deposits, fees, custody, maintenance, loss or damage, insurance, incident reporting, return condition, data handling, and early termination. RD approval alone does not create a rental entitlement.
Cloud and managed-operation services may process aircraft identifiers, telemetry, mission records, logs, imagery, maps, payload data, operator actions, alerts, and analysis outputs. The institution must have authority to provide and process that data. Access controls, retention, permitted use, storage location, security commitments, export, and deletion will be defined by the applicable privacy notice and written service agreement.
RDOS AI features may organize information, suggest checklists, explain telemetry, identify patterns, or assist with planning and review. AI output may be incomplete, delayed, or incorrect and must not be treated as an operational authorization or substitute for trained judgment. An authorized human operator and the responsible institution remain accountable for every mission, safety decision, command, and approval.
Parts of RATS, RADS, RDOS, cloud services, autonomy, analytics, AI, integrations, rentals, and product programs are in active development or limited release. Features, names, interfaces, pricing, eligibility, supported vehicles, timelines, and availability may change during testing, validation, and controlled rollout.
RD approval may enable technical briefings and evaluation, but it does not guarantee supply, pricing, a demonstration, subscription capacity, aircraft availability, procurement acceptance, delivery dates, or deployment readiness. Product, subscription, rental, pilot, and managed-operation commitments become binding only through an authorized written agreement.
Rotorcraftory may monitor access for security and compliance, apply product or organization-specific limits, and suspend or revoke RD access when terms are breached, information is inaccurate, misuse is suspected, legal or safety risk is identified, a program ends, or continued access is no longer appropriate.
Rotorcraftory may revise these terms as the program develops. Material changes may require a fresh recorded acceptance before protected access, product use, rental, or deployment continues. The terms version accepted with an access request is retained with that request.
These access terms do not replace the general website terms, privacy policy, confidentiality agreements, purchase terms, subscription terms, statements of work, rental agreements, data-processing terms, or other signed contracts. Where a signed agreement applies to a specific product or program, that agreement governs that scope.
Return to the public overview or continue to the institutional access section.