Convex through Squiid
Reactive backend where queries, mutations and the database are TypeScript. Convex is on the Squiid roadmap.
What Convex is
Convex replaces the database plus API layer with typed TypeScript functions. You write a query function, the client subscribes to it, and when underlying data changes every subscriber updates automatically without websocket plumbing or cache invalidation. Mutations are transactional, scheduled functions and cron jobs are part of the platform, file storage and full-text search are included, and the schema is defined in code with end-to-end types from the database to the React component. Actions handle calls to outside services such as model providers, keeping non-transactional work separate from the transactional mutation path.
For agent-written apps this removes a whole category of glue. There is no REST layer to generate, no state synchronisation to debug and no separate ORM, so a feature is one function and one component. It suits collaborative and live interfaces particularly well: dashboards, chat, multiplayer tools and anything that shows an AI job's progress while it runs, because the progress row updating in the database is enough to update the UI. Local development runs against a development deployment with the same types, so an agent sees real type errors instead of runtime surprises.
Why connect it through Squiid
Convex is on the Squiid roadmap. When it is connected, Squiid will provision the deployment, hold the deploy key and the admin credentials, and route client and admin traffic through https://api.squiid.io/v1/convex/... with Authorization: Bearer $SQUIID_API_KEY, with the Convex client working by base URL swap (gateway convention). Function calls, storage and bandwidth will be metered at Convex's listed price against prepaid credits, with the plan cost passing through on one monthly Squiid invoice.
- One account, one key, one bill, one dashboard. Convex sits beside every other service your project uses, on the same invoice and the same credit balance.
- Key custody. Squiid holds the Convex credentials. Your code carries
SQUIID_API_KEY, so CONVEX_DEPLOYMENT, CONVEX_URL, CONVEX_DEPLOY_KEY, NEXT_PUBLIC_CONVEX_URL 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 Convex 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 Convex deployment
- Reactive queries with end-to-end TypeScript types
- Transactional mutations, cron jobs and file storage
- Usage metered against prepaid credits
- Convex list pricing, no markup
How to connect Convex
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 CONVEX_DEPLOYMENT, CONVEX_URL, CONVEX_DEPLOY_KEY, NEXT_PUBLIC_CONVEX_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx
# every request: https://api.squiid.io/v1/convex/...
# header: Authorization: Bearer $SQUIID_API_KEY
Add it in your dashboard
Open the Squiid catalog, add Convex and fund credits. Squiid provisions the project and keeps the provider keys.
Put the one key in your env
Add SQUIID_API_KEY to .env and delete CONVEX_DEPLOYMENT, CONVEX_URL, CONVEX_DEPLOY_KEY, NEXT_PUBLIC_CONVEX_URL. Nothing else from Convex needs to exist in your project.
Point your agent at it
Claude Code, Cursor and Codex read the same variable and call https://api.squiid.io/v1/convex/. Agents like Convex because a feature is a typed function plus a component, with no API layer to keep in sync.
Pricing through Squiid
Convex charges a plan fee plus function calls, database bandwidth and storage 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 Convex usage, with no markup and no per-request margin.
Convex 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 Convex 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: data is exported and functions are redeployed from your source into a deployment in your own Convex account. Squiid never owns your code, your schema or your domain, and the gateway speaks Convex'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
Convex 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 Convex 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.
Related services
Supabase
DatabasesPostgres with auth, storage, realtime and edge functions attached
Next upProvisionedTurso
DatabasesSQLite on the edge with per-tenant databases and local replicas
RoadmapProvisionedVercel
HostingFrontend hosting with git-based deploys and preview URLs per branch
Next upProvisionedClerk
AuthDrop-in authentication with prebuilt components and organizations
LiveProvisionedNeon
DatabasesServerless Postgres with instant branching and scale to zero
LiveProvisionedQuestions people ask
Is Convex available through Squiid?
Not yet. It is on the roadmap as a provisioned service and can be followed from your dashboard.
Is Convex a database or a backend?
Both. It stores your data and runs the TypeScript functions that read and write it, with reactivity between the two.
Will realtime subscriptions work through the gateway?
That is the intent. Client subscriptions will authenticate with SQUIID_API_KEY while the Convex deploy key stays with Squiid.
Convex or Supabase?
Supabase is Postgres with services around it and is the safer default if you want SQL. Convex is a reactive TypeScript backend that removes the API layer.
How will it be billed?
Plan cost passes through at Convex's listed price and metered usage draws from prepaid credits, with no Squiid markup.
Connect Convex with one key.
Convex is a database and backend in one: TypeScript functions define queries and mutations, results update reactively in the client, and scheduling and file storage are built in. Planned for Squiid.