Porting from Orgo

Use this mapping to plan a port; it is not a compatibility promise. Names are used nominatively. Based on each provider's public documentation; check their current docs before migrating.

Call mapping

Source call	CE call or workflow	Behaves differently
POST /computers	POST /computers	Names alone do not establish schema parity; CE uses image,size,mode and accepted operations.
POST …/suspend and …/resume	POST …/pause and …/resume	Observe CE paused/running/ready and its memory-retention limits.
POST …/click, …/type, …/key	POST …/desktop/actions	CE validates a bounded action batch and releases its temporary input state.
Per-computer password query token for terminal/VNC	Typed sessions and single-use connect tokens	A CE session secret is not a general access token; SSH has no query-token exchange.
POST /v1/chat/completions with computer_id	Your own model loop and adapter	CE does not host the model or promise that API.
POST /templates and template builds	Private images	CE captures a stopped disk; template-build parity is not promised.

Validate the port

Replace authentication, error parsing and list handling explicitly. Keep separate control/data credentials and inspect each accepted operation rather than assuming a synchronous return. Test expiry, revoked authority, an interrupted response and cleanup against the exact CE SDK/API version. Do not carry vendor-specific prices, timing claims or lifecycle defaults into CE configuration.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.