Porting from Boat
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. Or keep your Boat client and switch base URL and key: see Boat-compatible API.
Call mapping
| Source call | CE call or workflow | Behaves differently |
|---|---|---|
| POST /sandboxes | POST /computers | Use image/size/mode and wait for an operation; a sandbox type is not a CE class. |
| GET /sandboxes | GET /computers | CE returns data,next_cursor,has_more rather than pageInfo. |
| DELETE /sandboxes/{id} and X-Ascii-Confirm-Delete | DELETE /computers/{id} and CE-Confirm-Delete | The confirmation value is the actual CE computer ID; retain the accepted operation. |
| boat exec / boat ssh / boat scp | cec exec / cec ssh / cec cp | Exec crosses the data plane; SSH keeps end-to-end keys and host checking. |
| boat fork | Private image plus create | No launch fork-running endpoint; stopping and capture change the workflow. |
| 24-hour create/fork idempotency | Control Idempotency-Key and explicit data keys | Keep CE scope/body/replay rules; a secret is not returned twice. |
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.