Shared across eligible Cloudflare services.
The one-minute answer
Yes: the grant can pay for much of Tegy’s Cloudflare application infrastructure. No: it cannot pay for AI Gateway, Codex, OpenRouter, or other third-party AI models. The biggest remaining uncertainty is whether Cloudflare Containers—the service that runs each live Tegy chat—counts as eligible usage.
One year after the confirmation email; exact time is unstated.
A cap inside the $10,000 total, not extra credit.
Cloudflare explicitly excludes it for now.
How the grant works
The credit is attached to the same Cloudflare account that runs Tegy. Eligible usage is deducted automatically. Cloudflare says the balance may not appear in the dashboard, so monthly invoices are the reliable record.
Grant became active
The approval email confirmed $10,000 for 12 months on Tegy’s production account.
Check the invoice
Review eligible usage, deductions, remaining runway, and anything billed outside the grant.
Graduate or use it up
The grant ends after one year or when fully consumed—whichever happens first. Extensions are not offered.
What we do receive
Eligible infrastructure credit, up to three Enterprise domains, security and network benefits, and priority ticket/chat support.
What it is not
It is not cash, is not transferable, cannot be applied to another account, and does not stop paid services automatically at expiry.
What can the credit pay for?
“Covered” means Cloudflare lists the service as eligible. “Not covered” means another bill still applies. “Confirm” means we should not budget on the credit until Cloudflare answers in writing.
Swipe the table to see what each item means for Tegy.
| Cost area | Coverage | What it means for Tegy |
|---|---|---|
| Workers, Durable Objects, D1 and Queues | Covered | These already run Tegy’s public app, coordination, chat history and reliable event delivery. |
| R2 file storage | Covered | Attachments and durable workspace files can draw from the grant, up to the $10,000 total. |
| Workers AI | Covered, capped | Up to $2,500 of the grant can support Cloudflare-hosted AI jobs such as transcription or embeddings. |
| Images, Stream, Workflows, Vectorize and Argo | Covered | Useful later for media delivery, durable background jobs, semantic search and measured performance needs. |
| Cloudflare Containers | Confirm first | Containers run each live Tegy chat but do not appear in Cloudflare’s published covered-product list. |
| AI Gateway | Not covered | Core Gateway features are currently free, but the grant cannot fund its Unified Billing balance. |
| Codex and third-party AI models | Not covered | Tegy’s main AI answer generation remains outside the Cloudflare startup grant. |
| Domain registration and premium network products | Not covered | Registrar fees, Magic Transit, Spectrum, dedicated IPs and the China Network require separate payment. |
Recommended plan for Tegy
The right move is to capture the benefits already aligned with Tegy—not redesign the product around expiring credit.
Activate the two immediately useful Enterprise domains
tegy.io and tegyusercontent.com are both still on Cloudflare’s Free plan. The first protects the app; the second protects the separate user-generated artifact boundary. This uses two of the three included Enterprise domains without consuming the $10,000 usage balance.
Let existing eligible usage draw naturally
Keep Workers, Durable Objects, D1, Queues and R2 on the current architecture. Check the first monthly invoice before forecasting how much runway the grant creates.
Ask Cloudflare about Containers before budgeting
Tegy uses one scale-to-zero Standard-1 Container per active chat. If those CPU, memory, disk and network line items are eligible, the grant becomes materially more valuable. If not, they remain a direct cost.
Use Workers AI only for a proven supporting job
The clearest candidate is audio transcription, which currently uses a third-party provider. A future move requires a quality, latency and cost comparison plus explicit approval before changing what the AI receives or how it is processed.
Consider semantic project search later
Workers AI embeddings plus Vectorize could power explicit search over project files. It should be an optional product capability, not a silent replacement for Tegy’s current full-file handoff to Codex.
Two questions need written confirmation
The approval includes priority support. These are the only material gaps preventing a clean cost forecast.
Are Cloudflare Container charges eligible?
Ask whether Container vCPU, provisioned memory, disk, network egress and logs are deducted from Tier 3 startup credits, and whether any product-specific cap applies.
What is the exact graduation commitment?
Confirm the timestamp, Enterprise-domain conversion steps and SLA. Cloudflare’s new US page advertises a 100% SLA, while an older still-live program terms page says the Startup Plan has no SLA.
Avoid the billing cliff
When the credit expires or is exhausted, eligible services do not necessarily stop. Usage can begin charging the payment method on file. Enterprise domains that are not moved to a paid plan revert to Free. The team should set internal reminders well before July 2027 and decide what to retain, downgrade or disable.
Suggested checkpoints: first invoice, January 2027, May 2027, and 20 July 2027.
Sources and confidence
Confirmed facts come from the account-specific approval email, current Tegy production configuration and Cloudflare’s official documentation. No private account identifier or inbox content is reproduced here.
- Cloudflare Startup Program Current tiers, eligible services, caps, exclusions, expiry and support.
- AI Gateway pricing Core features are free; paid features and billing are separate.
- AI Gateway Unified Billing Separate prepaid balance and current 5% purchase fee.
- Cloudflare Containers pricing Separate CPU, memory, disk, network and related usage dimensions.
- Cloudflare Vectorize Semantic search and retrieval use cases.
- Published legacy program terms Used only to identify the conflicting SLA and post-expiry wording.
Review date: 22 July 2026. Repository baseline:
da70f917a718a24570fdd2da48e5f23ead27340d. This is an
operational decision brief, not legal or tax advice. Cloudflare can update
its program coverage; the account invoice and written support responses
should govern future budgeting decisions.