Netlify through Squiid

What Netlify is

Netlify hosts frontend projects with a build pipeline attached to your repository. Every deploy is atomic and instantly rollbackable, deploy previews appear per pull request with collaborative comments, and redirects, headers and proxy rules are declared in a config file rather than in infrastructure. Netlify Functions and Edge Functions run server-side code, and small extras like built-in form handling and scheduled functions remove a surprising amount of glue from simple sites. Build plugins run as part of the pipeline, so tasks like sitemap generation or asset compression happen on deploy rather than on your machine.

For an AI-coded project Netlify is the pragmatic host when the app is not tied to Next.js: an Astro marketing site, a Vite single-page app, a static docs build or a landing page an agent generated in an afternoon. Form handling in particular means a contact form works without writing an API route, a database table or an email integration. Split testing between branches is also built in, which lets a generated variant be tested against the current site without a separate tool.

Why connect it through Squiid

Netlify is on the Squiid roadmap. When it lands, Squiid will provision the site, hold the personal access token and route builds and management calls through https://api.squiid.io/v1/netlify/... with Authorization: Bearer $SQUIID_API_KEY, with the Netlify CLI working by base URL swap (gateway convention). Pro seats pass through at $19 per seat per month at Netlify's listed price with no Squiid fee, and bandwidth, build minutes and function invocations above the plan meter against prepaid credits at list. Site-level environment variables are scoped per context, so a preview never accidentally writes to production data.

• One account, one key, one bill, one dashboard. Netlify sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Netlify credentials. Your code carries SQUIID_API_KEY, so NETLIFY_AUTH_TOKEN, NETLIFY_SITE_ID 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 Netlify 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 Netlify site with the token held by Squiid
• Atomic deploys with instant rollback
• Deploy previews per pull request
• Functions, forms and scheduled jobs
• Pro at $19 per seat passed through at list price

How to connect Netlify

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 NETLIFY_AUTH_TOKEN, NETLIFY_SITE_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Netlify charges a per-seat plan fee plus bandwidth, build minutes and function usage above the included allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Netlify usage, with no markup and no per-request margin.

Netlify Pro passes through at $19 a month at the provider’s listed price on your monthly Squiid invoice. Service subscriptions carry 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 Netlify 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 Netlify account, then domains and environment variables are re-pointed. Squiid never owns your code, your schema or your domain, and the gateway speaks Netlify'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

Netlify 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 Netlify 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.