EA studio cooperation: define the license and delivery
EAXAU coordinates studio cooperation and licensing around strategy selection, technical adaptation and license verification. Whether you need a compiled EA, a source-code license or custom development, start by identifying the source, permitted use and deliverables before agreeing a quote.
QQ 3832001817 · WeChat oooiniooo0624 / xau6000. Include the product name or page link if you have one. Otherwise, describe the problem you want to solve.
Choose the type of cooperation
| Requirement | What to clarify first |
|---|---|
| Compiled EA or tool license | Product and version, MT4 or MT5, environment, account allowance and term |
| Source-code license | Included source files, build environment, third-party dependencies and rights to modify, use commercially or redistribute |
| Adaptation of an existing project | Current issue, target environment, permitted changes and functions to preserve |
| Custom development | Features, inputs and outputs, acceptance examples, delivery scope and timing |
| Studio supply partnership | Products you are entitled to supply, evidence of rights, delivery capability and support scope |
MT4 and MT5, and compiled files and source code, are distinct delivery options. Feasibility, adaptation work and fees depend on the materials and scope under review.
Put the license scope in writing
Receiving a file does not establish every right to use it. Confirm who grants the license, which version it covers and the following details:
- Permitted accounts, devices, term and project scope.
- Whether modifications are allowed and how modified work may be used.
- Rights to commercial use, resale, redistribution or supply to third parties.
- Whether the license is exclusive, and any separate restrictions on third-party components.
- Responsibility for updates, maintenance and support, including their duration.
Source delivery, exclusivity, resale rights and maintenance should be agreed separately. Do not infer rights omitted from the agreement merely because source files are supplied.
Make delivery checkable
For a compiled product, confirm the installation file, version, license information and installation instructions. For source-code or custom work, also specify the editable files, dependencies, build process, configuration notes, test examples and acceptance record that are included.
Each quote should state inclusions, exclusions, acceptance criteria, revision scope and support duration. Additional features, third-party costs and ongoing maintenance should be identified before work starts if they are charged separately.
Formal cooperation depends on verifiable licensing evidence, a written scope and signed documents. The agreed delivery list determines what is included in a particular order.
To turn a requirement into a checklist and review the delivery item by item, see the EA requirements and acceptance guide.
Four steps from enquiry to delivery
- Describe the requirement. Share a product link or short brief, the platform, intended use and desired deliverables.
- Check rights and feasibility. Establish the licensing party, available materials, technical environment and missing information.
- Agree a written quote. Specify scope, fees, payment arrangements, acceptance and support before starting the agreed work.
- Deliver and review against the list. Check files, functionality and licensing scope; record revisions and their resolution.
Copy this enquiry checklist
Type: compiled license / source-code license / adaptation / custom development / studio supply.
Product or materials: name, public link or a short feature description.
Environment: MT4 or MT5, computer or VPS, intended instruments and account mode.
Intended use: individual / team / commercial project; modification or redistribution required?
Deliverables: installation files / source code / documentation / training notes.
Timing and budget: preferred date, budget range and essential conditions.
For an initial enquiry, business and technical requirements are enough. Before sharing restricted materials, confirm your right to provide them and use an agreed handover channel.
Common questions
Does a compiled EA purchase include source code?
Not necessarily. Compiled-product access and source-code licensing must be confirmed separately.
Can I modify, sell or pass source code to another studio?
That depends on the written license. Explain your intended use so the licensing party can confirm each permission.
Can an MT4 project simply be switched to MT5?
The implementation, dependencies and target environment need assessment. Agree feasibility, scope and acceptance criteria before requesting a final quote.
Can I see delivery requirements before ordering?
Yes. Describe the intended purchase or development scope and request a delivery list, acceptance method and support term in the quote.
Send your requirement to EAXAU · Browse the product entry point