onrup

Switching

Alternatives, and what moving costs.

What is on these pages?

For each platform: why teams actually leave it, what the migration involves step by step, and what you lose by going. They are switching guides rather than sales pages — several of them end by suggesting you stay, which is sometimes the right answer.

If you are choosing between two specific products rather than surveying a field, the head-to-head comparisons are the more direct read.

How a migration usually goes wrong

The dataset moves easily. Conversation and instruction formats are interchangeable and convert without loss, so the part everyone worries about is rarely the part that hurts.

What hurts is everything that was implicit. An adapter cannot move unless the base model and version match exactly, so in practice you are retraining rather than porting. Evaluation results from the old platform are not comparable to results from the new one, so the first honest comparison has to be built from scratch. And a requirement that was never written down — a compliance certification, data residency, a support relationship — turns up halfway through and stops the move.

Each page below leads with what the incumbent is genuinely good at, before the steps. If that section describes why you chose them, the rest of the page is not for you.

Managed fine-tuning platform

Serverless GPU platform

Closed model API

Hyperscaler ML platform

Last verified 6 August 2026.

Start with the free tier

A magic link creates your account, your tenant and your first API key. No card until you ask for compute.