Cerebrium vs Northflank

Cerebrium

Per-second GPU prices are public, a 94-operation OpenAPI spec covers the management API, and service account tokens expire and are limited to named projects. Deployed endpoints are callable without a token unless disable_auth = false is set, and no request rate limits, 429 handling or SLA were found in the reviewed documentation.

Northflank

OpenAPI 3.0 with over 100 paths, enums and per_page, page and cursor on every list. No scale to zero for services; minimum instances must be at least 1.

Cerebrium

1. Set disable_auth = false in cerebrium.toml before deploying. The default leaves the endpoint callable by anyone with the URL
2. Authenticate headless with CEREBRIUM_SERVICE_ACCOUNT_TOKEN. cerebrium login opens a browser
3. Raise response_grace_period for long work. It defaults to 15 minutes and async runs stop at 12 hours
4. Send ?async=true to get a run_id with HTTP 202, and add webhookEndpoint because async calls return no result to the caller
5. Check the plan before choosing hardware. A100, H100, H200, B200 and RTX PRO 6000 need Standard, and protected compute bills at twice the listed rate

Northflank

1. Issue the agent a team token under an API role limited to one project, not a personal token
2. Read x-ratelimit-remaining and wait x-ratelimit-reset seconds on a 429; the default is 1,000 calls an hour
3. Page lists with per_page up to 100 and the returned cursor instead of numbered pages
4. Use a job, not a service, for anything that finishes; services bill until paused or deleted
5. Fetch any docs page with .md appended to get Markdown