BEFORE WE TALK
A few good
questions.
How Fusion fits your team, your delivery process and your security requirements.
Working with Fusion
What is the difference between Fusion Standard and Fusion Autonomous?
Standard is the SaaS platform your engineering team operates, using your own AI provider accounts. JadeX engineering oversight is provided through a separate development-services engagement. Autonomous is a managed AI engineering service: JadeX runs the specialist squad, with engineering review, oversight and escalation included within the agreed service scope.
Can this work alongside our existing team?+
Yes. Agents implement scoped tickets and prepare tests in parallel with delivery squads. Human-led, Autonomous and Hybrid Delivery share the same backlog and governance.
What does “six-person capacity” mean?+
Fusion Autonomous is offered as the equivalent capacity of six full-time human developers, with specialist AI roles across technical leadership, front end, back end, integration, QA and review. Role mix, workloads, concurrency and review capacity are agreed for your service.
What happens to our Engineering Memory?+
The customer-specific Engineering Memory created through Autonomous is fully owned by you and exportable. You retain this asset throughout and beyond the engagement.
How do we get started?+
Start with a conversation about your team and backlog. We agree a suitable service, initial scope, integrations and security requirements before delivery begins.
SECURITY & CONTROL
Protecting your engineering environment.
Does our intellectual property remain ours, and is it kept confidential?
Yes. Your existing source code, data, documentation and intellectual property remain yours and are treated as confidential. Your customer-specific Engineering Memory is also fully owned by you and exportable. Ownership of new deliverables and any applicable third-party or pre-existing components, together with confidentiality and permitted use, is set out in the agreed service terms and any applicable NDA.
Where are our code and data processed?
Fusion Standard uses your own AI provider accounts and credentials. Fusion Autonomous uses JadeX-managed, self-hosted AI infrastructure. The processing locations, model choices and data flows for your service are agreed as part of onboarding and your security review.
Who can access our repositories?
Repository coverage, integrations and operating responsibilities are agreed before delivery begins. As part of the security review, confirm which JadeX engineers, AI agents and connected services need access, the permissions they require and how that access will be revoked.
Is our code used to train AI models?
Training and data-use terms depend on the models, providers and configuration used for your service. With Fusion Standard, the terms of your own AI provider accounts apply. For Autonomous, confirm the model configuration and data-use commitments with JadeX before onboarding; self-hosting alone does not establish a data-use policy.
Can AI agents change or release production code without approval?
AI agents implement agreed, scoped work and prepare tests. JadeX engineers review changes and request rework or approve them for your agreed release process. Your team retains control over priorities, approvals and release decisions. Production access and release permissions are agreed before delivery begins.
How are credentials and sensitive information handled?
Fusion Standard uses your own AI provider accounts and credentials. Repository tokens, API keys, sensitive data and the responsibilities for managing them should be covered in the agreed security setup. Confirm the storage, permitted access, rotation and revocation arrangements for your configuration with JadeX before connecting systems.
What happens to our code and Engineering Memory when the engagement ends?
The customer-specific Engineering Memory created through Autonomous is fully owned by you and exportable, throughout and beyond the engagement. Retention and deletion of code copies, logs and other service data, together with revocation of repository and provider access, should be confirmed in your service terms.
LET’S BUILD WHAT’S NEXT