Bottom line
Tegy can use eligible Microsoft startup credits to pay for
Azure OpenAI calls to gpt-5.6-luna and
gpt-5.6-terra. The credits stay inside Azure:
Tegy would authenticate to an Azure OpenAI resource with an API key
or Entra token, Azure would meter the calls, and eligible sponsorship
credits would offset that Azure invoice. This is not a cash-out, and
it does not fund ChatGPT/Codex subscriptions or third-party model
providers.
[M2]
[M3]
[M5]
$150K
Microsoft public ceiling over time
Staged milestones; not an upfront award.
$200K
Possible investor-network ceiling
Eligibility depends on Microsoft’s investor path.
$350K
Google AI-program headline ceiling
The July email said Tegy may be eligible.
2 / 2
Current Tegy model variants on Azure
Luna and Terra are listed Direct from Azure.
Two offers were being conflated
The mailbox evidence supports two separate tracks. Neither the email
headline nor an internal status update establishes the exact usable
balance in a cloud billing portal.
Reported active; balance unverified
Microsoft for Startups
-
An internal “Free Money” thread said Microsoft was active with
credits and that Tegy had applied for more.
[E1]
-
The same thread used a headline of “up to $150,000,” consistent
with Microsoft’s current public program.
[M1]
-
No original Microsoft promotional award email was found in the
searched personal mailbox.
-
Exact amount, expiration, subscription type, and remaining
balance require authenticated sponsorship-portal review.
Eligibility outreach; not an award
Google for Startups Cloud Program
-
The high-value July 16 message was “Google x Tegy – Great News!
Exclusive GFSCP Eligibility.”
[E2]
-
It said Tegy “may be eligible” for “up to $350,000” over two
years; both phrases are conditional.
-
The
admin@tegy.io archive shows an application
acknowledgment and a later action-needed update—not a welcome
email confirming award size.
[E3]
-
Google’s public program limits these credits to eligible Google
Cloud services; third-party models are excluded.
[G1]
What “cash in” means operationally
An API key is an authentication credential, not stored value. The
monetary value remains a sponsorship balance attached to the Azure
subscription.
01
Sponsorship award
Eligible credits appear on Tegy’s Azure subscription.
02
Azure OpenAI resource
Create a resource under that credited subscription.
03
Model deployment
Deploy Luna or Terra where quota and region allow.
04
Key or Entra token
Tegy authenticates directly to the Azure endpoint.
05
Azure-metered usage
Eligible charges consume sponsorship before cash billing.
Microsoft documents Azure OpenAI endpoints and both API-key and
token-based authentication.
[M5]
Microsoft’s sponsorship rule is billing-source based: models sold and
billed directly by Azure are covered; partner and Marketplace models
are not.
[M3]
Billing guardrail: Microsoft says the sponsorship
subscription automatically converts to pay-as-you-go when credits are
exhausted or expire. Before any production routing, Tegy should verify
the expiry date and add budget alerts plus an explicit spend ceiling.
[M6]
What the Microsoft credits cover
| Destination |
Startup-credit treatment |
Why |
| Azure OpenAI / Direct from Azure |
Covered |
Microsoft explicitly allows Azure credits for Azure OpenAI,
and Azure-direct model usage is billed to the Azure
subscription.
[M2]
[M3]
|
| OpenAI Platform API |
Not the same balance |
Microsoft distinguishes OpenAI as a third-party benefit from
Azure OpenAI, which is the Microsoft product paid by Azure
credits.
[M2]
|
| ChatGPT or Codex subscription |
Not covered |
These are not Azure-metered services. Sponsorship coverage
follows the Azure subscription invoice.
[M3]
|
| OpenRouter |
Not covered |
OpenRouter is a third-party billing destination, not Direct
from Azure.
[M3]
|
| Anthropic Claude through Foundry |
Not covered |
Microsoft names Anthropic among popular providers excluded
from startup sponsorship coverage.
[M3]
|
| Azure Marketplace products and support plans |
Not covered |
Microsoft explicitly excludes non-Azure products,
Marketplace products, and support plans.
[M2]
|
The $150,000 is a progression, not a lump sum
Microsoft’s current general program starts at $1,000 and evaluates
higher milestones based on verification, active workloads, and
sustained usage. An eligible investor-network path may unlock up to
$200,000, but that does not establish Tegy’s award.
[M0]
[M1]
| Milestone |
Published requirement |
Meaning for Tegy |
| $1,000 |
Sign up and verify identity. |
Starter credit; it does not prove later tiers. |
| $5,000 |
Complete business verification as a registered entity. |
Likely first meaningful proof point to inspect in the portal. |
| $25,000 |
Use 5+ Azure workloads over about 60 days. |
Requires real adoption, not merely creating resources. |
| $50,000 |
Use at least 7 workloads over about 60 days. |
Expanded Azure architecture becomes part of qualification. |
| $150,000 |
Use 10+ workloads and sustain approximately $3,000/month of
Azure usage for about 60 days.
|
The headline tier presupposes material production usage and
should not drive spending merely to unlock credits.
|
Microsoft says milestone upgrades are evaluated automatically, need
not be sequential, and the $25,000 milestone includes a one-time
two-year extension.
[M1]
Direct fit with Tegy’s current runtime
At repository commit f55288f, Tegy routes all user chats
through the Codex app-server and selects Luna or Terra. Azure lists
both exact model IDs as Azure-direct models with Responses API,
structured output, image, function/tool, and parallel-tool support.
[T1]
[M4]
| Tegy mode |
Current model |
Azure listing |
Credit fit |
| Signal |
openai/gpt-5.6-luna, xhigh |
gpt-5.6-luna, Direct from Azure |
Strong model match |
| Playbook |
openai/gpt-5.6-terra, medium |
gpt-5.6-terra, Direct from Azure |
Strong model match |
| Doctrine |
openai/gpt-5.6-terra, high |
gpt-5.6-terra, Direct from Azure |
Strong model match |
Compatibility is promising, not yet proven. Tegy
currently implements only
chatgpt and
openrouter Codex authentication modes. Adding Azure
requires a third provider route and an end-to-end proof of Tegy’s
app-server, tools, streaming, and StrategyOS behavior.
[T2]
Some Azure GPT-5.6 quota tiers also require an explicit quota request.
[M4]
Where the Google offer helps—and where it does not
The Google path is worth pursuing, but it cannot pay Tegy’s current
OpenAI-model bill without a model/provider change.
| Published element |
Current term |
Implication |
| Headline |
Up to $350,000 over two years for qualifying AI startups. |
The email’s number matches the public maximum, not an award. |
| Year 1 |
100% coverage up to $250,000 for AI-first startups. |
Potentially substantial subsidy for Gemini-native production. |
| Year 2 |
20% coverage up to an additional $100,000. |
Only one-fifth of eligible year-two usage is credited. |
| Models |
Credits cover Google models such as Gemini and Gemma. |
Useful for workloads deliberately moved to Google-native models. |
| Exclusions |
Third-party models and Marketplace offerings are not covered. |
No reimbursement for Luna, Terra, Claude, or OpenRouter billing. |
| Eligibility |
Scale-tier AI startup criteria include VC backing, recent
fundraising, company age, prior-credit limits, and using or
planning to use Gemini as a product foundation.
|
Approval remains discretionary and fact-specific. |
Source for program structure and eligibility:
[G1].
Source for third-party and Marketplace exclusions:
[G2].
Recommended decision
1. Validate Azure first
It offers the exact Luna/Terra family Tegy already uses. Verify
the sponsorship balance and make a minimal Responses API call
before committing engineering time.
2. Continue Google qualification
Treat the Google email as a valuable lead, not booked credits.
Use an award for Gemini-native workloads only after a deliberate
model-quality and routing decision.
3. Do not optimize for headline tiers
Microsoft’s upper milestone requires sustained spend and many
workloads. Architecture should follow product need, not be
inflated to chase a larger credit ceiling.
Smallest responsible proof
-
Sign in to the Microsoft sponsorship portal and record only the
award amount, remaining balance, expiration date, subscription
type, and pay-as-you-go conversion setting.
-
Add Azure budgets and alerts before creating production-capable
resources.
-
Confirm that
gpt-5.6-terra is deployable in an allowed
region and request the smallest appropriate quota if needed.
-
Send one Responses API request using a temporary Azure endpoint and
verify that Cost Management records an Azure-native meter against
the sponsorship subscription.
-
Run a bounded Tegy compatibility proof: streaming, function/tools,
parallel tools, reasoning configuration, image input, and one
StrategyOS task.
-
Compare output quality, latency, token accounting, and effective
credited cost against the current ChatGPT/OpenRouter route.
-
Only after operator approval, implement Azure as a production
provider or fallback. Provider routing changes the user-to-model
boundary and is outside this report’s read-only research scope.
What is confirmed and what remains open
Confirmed
Azure startup credits can pay eligible Azure OpenAI usage; Azure
lists Luna and Terra as Direct from Azure; Tegy currently selects
those model variants.
Strong inference
Azure is the lowest-change path to subsidizing Tegy’s existing
core models because its API and tool capabilities align on paper.
Unverified
Tegy’s exact Azure award and expiry, available GPT-5.6 quota,
billing deduction, production reliability, and full Codex
app-server compatibility.
Private mailbox evidence
These citations record only the minimum metadata and short excerpts
needed to support status claims. Message IDs, authentication codes,
account numbers, tenant identifiers, and full private threads are not
reproduced.
E1 Internal “Free Money” thread
- Mailbox
tornikeonoprishvili@gmail.com
- Subject
- Free Money
- Dates
- 10–15 July 2026
- Participants
- Tornike Onoprishvili and Gary; internal Tegy discussion
- Supports
-
The team’s Microsoft status was reported as active with credits,
with a further application underway; the account login was
reported as
admin@tegy.io.
“Microsoft = active with credits (applied for more)”
Interpretation: an internal operational update, not independent
proof of the amount, balance, expiration, or eligible meters.
E2 Google eligibility outreach
- Mailbox
tornikeonoprishvili@gmail.com
- Sender
- Pui Kit TAM (Lucas), Google Cloud North America,
puikit@xwf.google.com
- Subject
- Google x Tegy - Great News! Exclusive GFSCP Eligibility
- Received
- 16 July 2026
- Supports
-
The remembered high-value outreach was from Google and described
possible eligibility for up to $350,000 over two years.
Tegy “may be eligible” for credits “up to $350,000.”
Interpretation: conditional sales and qualification language, not a
credit-award notice.
E3 Google application-status records
- Mailbox
- Messages addressed to
admin@tegy.io, located in the personal Gmail archive
- Records
-
Application acknowledgment on 15 July 2026; “Tegy: Google for
Startups Cloud Program Update” marked action needed on 20 July;
follow-up meeting on 22 July.
- Supports
-
An application and qualification process was underway after the
outreach.
Interpretation: process evidence only. No reviewed message was
treated as proof of a final $350,000 award.
Official and repository sources
Official program pages are temporally sensitive. Links were checked
on 25 July 2026; model availability, quotas, and credit terms should be
rechecked before implementation.
M0 Microsoft benefits overview
Supports the general $150,000 ceiling, possible $200,000
investor-network ceiling, and eligible-Azure-services framing.
Microsoft for Startups Benefits Overview
(Microsoft Learn, updated 16 June 2026).
M1 Microsoft credit progression
Supports the $1K, $5K, $25K, $50K, and $150K milestones and their
verification, workload, sustained-usage, and extension requirements.
Getting started with Microsoft for Startups
(Microsoft Learn, updated 11 June 2026).
M2 Azure OpenAI eligibility
Supports applying Azure credits to Azure OpenAI and the exclusion
of non-Azure, Marketplace, and support-plan purchases; also
distinguishes Azure OpenAI from the third-party OpenAI benefit.
Azure experience for founders
(Microsoft Learn, updated 14 April 2026).
M3 Foundry sponsorship billing boundary
Supports coverage for models sold and billed directly by Azure and
exclusion of partner, community, Marketplace, and named third-party
providers including Anthropic.
Microsoft for Startups Sponsorship Coverage for Foundry Models
(Microsoft Learn, updated 14 April 2026).
M4 Azure-direct GPT-5.6 catalog
Supports Azure-direct availability of gpt-5.6-sol,
gpt-5.6-terra, and gpt-5.6-luna, listed
APIs and tool capabilities, and the possible need for a quota
request.
Foundry Models sold by Azure
(Microsoft Learn, checked 25 July 2026).
M5 Azure endpoint authentication
Supports Azure OpenAI resource endpoints and authentication by
Azure OpenAI API key or bearer token.
Azure OpenAI REST API reference
(Microsoft Learn, checked 25 July 2026).
M6 Sponsorship conversion risk
Supports the warning that the Azure Sponsorship subscription
automatically converts to pay-as-you-go when credits are used or
expired.
How to Apply to Microsoft for Startups
(Microsoft Learn, updated 18 June 2026).
G1 Google AI startup program
Supports the $350,000 headline, two-year structure, year-one and
year-two percentages, Gemini/Gemma coverage, eligibility criteria,
and third-party model exclusion.
Google Cloud AI startup program
(Google Cloud, checked 25 July 2026).
G2 Google program FAQ
Supports discretionary acceptance and the exclusion of third-party
services and Google Cloud Marketplace offerings.
Google for Startups Cloud Program FAQ
(Google Cloud, checked 25 July 2026).
T1 Tegy runtime model selection
Supports the active Codex runtime and the Signal, Playbook, and
Doctrine mappings to Luna and Terra.
shared/agent-runtime.ts at f55288f.
T2 Tegy’s implemented auth routes
Supports the finding that Tegy currently implements
chatgpt and openrouter Codex auth modes,
with OpenRouter configured over the Responses wire API; Azure is
not yet an implemented route.
auth modes
and
provider configuration.
Report scope and limitations
-
This is an engineering and program-eligibility decision brief, not
legal, tax, or accounting advice.
-
No Microsoft or Google cloud console state was changed while
researching this report.
-
The Microsoft sign-in flow was not completed, so no MFA was
triggered and no live balance was claimed.
-
No Azure model was deployed and no billable inference request was
made; technical fit remains subject to the bounded proof above.
-
No provider-routing or model-visible behavior was changed in Tegy.