Deployment and ownership

Define what you receive and how it operates.

An enterprise engagement should make hosting, source code rights, platform connections and operational responsibilities clear before delivery.

Ownership boundary

Application code and platform IP
have distinct scopes.

Your application

The agreed frontend and backend application code, together with the application delivery scope.

Genesis platform

The Genesis platform, Context Memory and shared platform components remain Dalfin AI intellectual property.

Deployment planning

Agree the arrangement your organisation needs.

  • Platform and context

    Confirm where Genesis and Context Memory operate and how context is handled.

  • Application runtime

    Agree hosting, required components, platform connections and operational access.

  • Ongoing responsibility

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

Private deployment and handover

Specific options and any disconnect conditions are confirmed against the current architecture and engagement agreement.

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