Deployment and ownership

Define what you receive and how it operates.

A Genesis engagement makes application source rights, hosting, platform connections and operating responsibilities clear before delivery. Customer application assets and Genesis platform technology have distinct ownership boundaries.

Ownership boundary

Application code and platform IP
have distinct scopes.

Your application

The frontend and backend application code, data and other deliverables expressly included in your agreement.

Genesis platform

Genesis, Context Memory, generation technology and shared proprietary platform components remain Dalfin AI intellectual property.

Deployment planning

Agree the arrangement your organisation needs.

  • Platform and context

    Genesis and Context Memory operate under the agreed Dalfin AI service and data-processing arrangements.

  • Application runtime

    Agree hosting, required Genesis connections, authentication, shared components and operational access.

  • Ongoing responsibility

    Define deployment, support, training, maintenance and handover responsibilities.

Private deployment and handover

An application's code ownership does not mean every shared service is delivered with it. Some application components require continuing connectivity to Genesis. The engagement identifies those dependencies and any supported transition arrangements.

Delivery responsibility

Choose the support your technical team needs.

  • Customer led

    Your technical team leads engineering and validation using Genesis.

  • Assisted delivery

    Your team and Dalfin AI share delivery under an agreed scope.

  • Dalfin delivered

    Dalfin AI leads the agreed application delivery programme.

Discuss your deployment
and ownership requirements.

Tell us about your processes, current systems and delivery requirements. We will arrange a relevant Genesis demonstration.

Request an enterprise demo