Understand application ownership, platform dependencies and the decisions made for enterprise deployment and security.
Ownership, deployment and security
Enterprise software needs clear boundaries: what your organisation owns, what technology remains part of Genesis, where your application runs, and who is responsible for access and operation.
What does the customer own?
Under the applicable engagement agreement, customers own the agreed applications and customer-specific source-code deliverables created for their organisation, together with their own business data.
Dalfin AI retains the Genesis platform, Genesis Context Memory technology, reusable shared components, underlying tools and other intellectual property identified as Dalfin technology in the agreement. Third-party components remain subject to their respective terms.
The statement of work identifies the application deliverables, source handover arrangements and any licensing conditions that apply.
Does an application remain connected to Genesis?
Yes, for the agreed Genesis-dependent capabilities. Ownership of generated application source does not mean every resulting application can operate entirely separately from the Genesis platform.
Applications may continue to rely on Genesis for shared or reusable capabilities and other contracted services. The required connections, service responsibilities and effects of losing connectivity are documented for the specific solution.
If your organisation has particular availability, network-isolation or operational-resilience requirements, raise them during scoping so they can be assessed and designed appropriately.
Where does the application run?
Application hosting and runtime arrangements are agreed for each engagement. They may involve your organisation's cloud or other approved infrastructure, subject to architecture, connectivity and security requirements.
The location and operating model of the Genesis platform and Context Memory should not be inferred from where the generated application itself is deployed. Deployment alternatives, including any private or isolated arrangement, require explicit assessment and agreement; they are not standard commitments in this public guide.
How are security and access handled?
The agreed solution design should address:
- User identities, roles, permissions and approval responsibilities.
- The kinds of business and personal data processed.
- Integration boundaries and credentials management.
- Logging, monitoring, backup and recovery responsibilities.
- Infrastructure location, availability and regulatory requirements.
- Testing, change approvals and access to production environments.
Security controls are assessed against each customer's risk profile and deployment model. This public guide does not certify a particular security standard, data residency arrangement, zero-access guarantee, or compliance outcome.
How are sensitive materials managed during discovery?
Only provide materials through an agreed authorised channel. Do not include passwords, secret keys, live personal data or confidential records in an open enquiry form or a publicly shared example. Dalfin AI and the customer agree appropriate access and handling arrangements for any sensitive material needed for engineering.
What happens at acceptance and handover?
The parties confirm which deliverables and evidence are required, which tests must pass, who approves release, and who operates and supports the resulting application. Any material unresolved issues should be recorded and handled through the agreed exception or change process.
Commercial terms, service levels, warranties and support obligations are set out in the applicable agreements rather than in public product documentation.
Compare engagement models ยท Contact Dalfin AI (opens in a new tab)