Fly.io through Squiid

What Fly.io is

Fly.io deploys containers as lightweight virtual machines placed in the regions you choose. Machines can be started and stopped in a second, so an app can scale to zero and wake on the first request, and the Machines API lets you create a VM per job, per tenant or per user session programmatically. Private networking connects your services over WireGuard, volumes give persistent disk, and Fly Postgres and managed Postgres options sit alongside. Health checks and rolling deploys are handled by the platform, and the proxy routes each request to the nearest healthy machine.

For agent-built products the interesting capability is per-tenant or per-session compute. Running a dedicated instance for each customer, spinning up a VM to execute a workload and then destroying it, or placing an app near users in three continents are all things that are awkward on function platforms and normal here. It is also a common home for Elixir, Rust and Go services that need long-lived processes and websockets. Regions are chosen per app, so moving a service closer to its database is a configuration change.

Why connect it through Squiid

Fly.io is on the Squiid roadmap. Once connected, Squiid will provision the organization, hold the API token and route deploys and Machines API calls through https://api.squiid.io/v1/fly-io/... with Authorization: Bearer $SQUIID_API_KEY, with flyctl working by base URL swap (gateway convention). Compute, volumes and bandwidth will meter against prepaid credits at Fly's listed price on your single Squiid invoice, which is useful for a platform where an agent can create machines in a loop.

• One account, one key, one bill, one dashboard. Fly.io sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Fly.io credentials. Your code carries SQUIID_API_KEY, so FLY_API_TOKEN, FLY_APP_NAME, FLY_REGION never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Fly.io costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Fly organization with the token held by Squiid
• Containers as fast-booting VMs in many regions
• Machines API for per-tenant or per-job instances
• Volumes and private networking
• Fly list pricing, no markup

How to connect Fly.io

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces FLY_API_TOKEN, FLY_APP_NAME, FLY_REGION
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/fly-io/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Fly.io charges per second for machine CPU and memory plus volumes and bandwidth, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Fly.io usage, with no markup and no per-request margin.

Fly.io has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Fly.io usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: the app is redeployed from your own source into your own Fly.io account, then domains and environment variables are re-pointed. Squiid never owns your code, your schema or your domain, and the gateway speaks Fly.io's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Fly.io through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Fly.io usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.