Start a specific research, commercial or institutional conversation

For industrial and scientific research partners

Describe the precise issue you want evaluated, such as detection of a class of machinery faults or reconstruction of a research calculation. Indicate the equipment or environment, current baseline, representative non-sensitive examples, expected success criteria and who could independently evaluate the result. A meaningful collaboration starts by agreeing the technical test and permitted data scope.

The programme should also establish who controls background IP, what would be created in the research, where source information remains stored, whether publication is possible and who is authorized to approve a later commercial use. A research discussion does not automatically grant BTG the right to ingest or resell your data.

For source holders and prospective contributors

Explain the type of source—such as industrial operating logs, laboratory measurements or an existing algorithm—and the right you believe you control. Describe major restrictions imposed by employers, original licensors, institutional ethics or privacy rules. If you are acting for an organization, explain which office has authority to approve an access or commercial licence.

Do not send raw patient, employee, student, private location, confidential research or community-controlled material through an ordinary initial inquiry. The appropriate first step is a lawful rights and security discussion about what could be shared, under what rules and by which approved mechanism.

For software developers and technology integrators

Identify the target platform, intended task, the component or input/output contract required, dependencies and acceptable runtime limits. State whether you are interested in the DataChip/Composer/SDK architecture, a restricted research test, a Bridge connector or a controlled computational service. The technical qualification scope should be clear before anyone promises compatibility.

An integration can be conceptually compatible yet still lack a signed SDK contract, end-to-end device qualification or approved deployment. Public illustrations of Bridge or the Exchange should not be treated as service-level commitments.

For financial, legal or policy reviewers

Specify whether your interest concerns commercial licences, ownership of underlying datasets and inventions, contributor remuneration, public information standards, corporate issuance or regulated market operation. These subjects have different governing authorities. An institutional review of a research method should not be framed as endorsement of a proposed securities exchange.

Useful feedback includes jurisdiction-specific legal constraints, privacy or sovereignty questions, investor-protection issues, technical audit standards and the records an independent reviewer would require. BTG’s public documentation distinguishes proposed infrastructure from completed licensed operations.

What happens after an inquiry

A legitimate next step would identify the parties, narrow the scope and determine whether a professional review, technical evaluation or separate agreement is necessary. No confidentiality obligation, data access grant, ownership assignment, fee agreement or financing commitment should be inferred solely from reading the website or sending an introductory message.