Reference / providers / generated

Fly.io Sprites

This reference is generated from the same provider capability model used by every Wildflower SDK. It describes the portable create surface and the non-secret connection context kept separate from provider credentials.

Contract valuesprites

Create inputNo provider-specific create options

Connection fields0

Create options

Wildflower rejects provider-specific create options for this adapter instead of silently ignoring them.

Runtime behavior

These capability facts come from the same generator-owned model used by the provider catalog and SDK documentation.

Image selectionfixed

Timeoutprovider managed

Output streamsseparate

Working directorySupported

Environment variablesSupported

Persistent resumeSupported

Explicit stopNot supported

Snapshots / restoreNot supported

DeleteSupported

Connection context

This adapter needs no additional non-secret connection fields. Its provider credential is still connected separately or supplied as an inline override.

Credentials never enter the create body

Connect the provider once for the project, or send a typed inline credential override. Wildflower keeps credentials in authentication headers and never serializes them into sandbox JSON.

Usage, cost, and latency evidence

Billing signalno documented api

Wildflower integrationestimate only

Provider granularitynone

Expected lagunknown

Provider-reported costUnavailable

Live credential proofNot verified

Fly.io Sprites provider cost is not available

Sprites bills actual consumption, so Wildflower's normalized wall-time estimate is intentionally low-confidence.

No public per-Sprite billing API is documented.
Actual CPU and memory consumption cannot be reconstructed from lifecycle wall time.

Review the official provider signal source. A normalized list-price estimate remains separate from provider reporting and invoice reconciliation.

Fly.io Sprites

Create options

Runtime behavior

Connection context

Usage, cost, and latency evidence

Continue