It greatly depends on the requirements that the model has. Some models can even run off of cpu and system ram. But, there are many GPU VMs available with AWS, Azure, etc. and you’d deploy it similar to how you would your other applications.

I might be misunderstanding the issue, but would turbo & turbo frame tags be the best solution here? When you have a form object and you're submitting the form, I don't think that the Rails controller can respond with a new form for the task like you're doing in the update. (at least not with how you have it setup like that).

Are you trying to do something like nested forms? Once the user uploads a document, you want it to add a new field where they can select an additional document? If this is the case, it may be better to use a Stimulus controller. This episode may help. https://www.driftingruby.com/episodes/nested-forms-from-scratch-with-stimulusjs

  abner.figueroa I think that this is kind of what you're looking for. Please correct me if I am mistaken.

Should be visible now.

You could add this to the form which will disable turbo's default behavior on the form.

data-turbo: { false }