Managed deployments
InferCrane Cloud is the MVP path for customers who want InferCrane to operate a model deployment. It is deliberately time-boxed and prepaid. BYOC remains a separate path in which the customer pays their cloud directly. The control plane must not queue provider work unless the tenant’s available wallet credit covers the complete authorization hold. A merely positive balance is insufficient: available credit must be greater than or equal to the current hold.Customer flow
- Choose a model and serving goal.
- Select InferCrane Cloud · prepaid and a 1, 6, or 24 hour runtime window.
- InferCrane checks a current exact provider price and launch evidence.
- Review the hourly rate, authorization hold, available credit, and any shortfall.
- Add credit when needed, then approve the deployment.
- InferCrane atomically reserves credit and queues one durable deployment operation.
- The runtime clock starts only when the stable endpoint is activated.
- At the runtime limit, InferCrane withdraws the route, deletes provider resources, settles measured runtime, and releases unused held credit.
What you pay
The current MVP supports one elastic RunPod GPU per managed deployment. The GPU is created with the control plane’s own RunPod credential, not a customer credential, and the product you buy is InferCrane Cloud. The server sets the hourly rate from a current, complete provider price observation. A browser request cannot set or change the rate.
For example, at a rate of
$0.70/hour, a one-hour deployment holds $0.816667: one hour of
runtime plus the ten-minute cleanup allowance. The hold is not the final charge. The charge never
exceeds the hold, and unused credit returns to the available wallet after provider deletion
succeeds. A deployment that never activates is not charged.
The quote returns the hourly rate, the hold, the runtime limit, the cleanup allowance, the GPU and
its placement, and the time until which the quote is valid. Provider credentials and provider
resource identifiers stay server-side.
Why the rate differs from the GPU price catalog
The GPU price catalog lists each provider’s public price for a GPU. It is the reference for BYOC, where you pay the provider directly and provider charges never pass through InferCrane. The InferCrane Cloud rate is a different price: what InferCrane charges to provision, serve, and delete the deployment for you. Expect it to be higher than the provider’s listed price for the same GPU. The deployment review shows the exact rate and hold before anything is charged.Atomicity and recovery
Wallet reservation, deployment intent, and lifecycle operation are one database transaction. Idempotency keys cannot create duplicate holds. A deployment name has at most one open hold; a name deployed again after deletion gets a new hold, and the settled one stays as history. Deletion settlement and wallet release are also one transaction and are safe to retry. The background expiry worker finds:- activated reservations past their time limit; and
- terminal failed or cancelled launches that never activated and have no live replica.