I’ve been trying to get a straight answer out of NVIDIA Inception for four months. Other founders on this forum have been at it longer. Posting publicly because the private channel isn’t working, and the same gap keeps showing up across these threads.
Quick context. We’re an Inception member. Received $10K in AWS Activate credits in 2024. This January, on AWS’s confirmation that we were eligible for the difference, we applied for the $25K Grow Tier. The application keeps getting auto-rejected with “you have already received credits at the same or greater amount.” That doesn’t track. $10K is less than $25K, and AWS’s own guidance says startups can reapply at a higher tier for the difference.
How we got here
One thing up front: “have you tried emailing inceptionprogram@nvidia.com” is the standard first reply on these threads, and we’ve been on that route for months. Posting publicly as escalation, not instead of using the private channel.
January 2026: our Airtable submission got stuck. I emailed Inception support. They cleared the request state on the provider side, and we resubmitted on 27 February. That worked. The benefit moved to “NVIDIA Confirmed” on the Inception portal, with the note to follow up with the partner. That state reset was a provider-side action, and it’s exactly the kind of intervention several other forum posters (linked below) have been asking for.
AWS rejected the application anyway.
I went back to Inception with a specific question: what credit tier is the Org ID / provider package attached to our request, and is there a separate Org ID, invitation, or provider mapping for the $25K offer? I cited AWS’s own published guidance directing applicants to ask the provider about Org ID and provider-specific package eligibility.
The reply didn’t engage with the question. I was told instead that review and approval are managed entirely by AWS, that AWS provides the Org ID, and that NVIDIA has no visibility into the application status.
That answer addresses a question I did not ask. I am not asking NVIDIA to approve AWS credits. I am asking NVIDIA to explain the provider-side state that NVIDIA confirmed.
There’s also a direct inconsistency. Two months earlier, the same team had taken provider-side action on our case. The portal state reset is provider-side. Either Inception can engage with the provider-side mechanics (in which case the tier-mapping question is answerable), or January was a one-off worth explaining.
Our AWS account team also went directly to Inception with the same question on our behalf. They got substantially the same canned reply. One AWS contact noted on the record that this isn’t the first time they’ve had trouble understanding the Inception × Activate handoff.
Four months in. Private channel exhausted. AWS-side fully cooperative. The unanswered piece is provider-side.
We’ve also confirmed the practical prerequisites our AWS contact pointed to from a similar case they’d seen resolved: company details, products, and profile filled out on the Inception portal; NVIDIA GPU instances running consistently on AWS for roughly two years (core to our stack). All in place. AWS services currently paused while this is unresolved.
A blind reset and resubmission would just put us through the same process a third time unless the underlying Org ID / provider package / tier mapping is checked first.
What AWS’s own documentation says
The AWS Activate Portfolio path is for provider-backed startups. It requires association with an Activate Provider and that provider’s Organizational ID. ( Credits )
The Org ID is, in AWS’s words, a unique, case-sensitive code “provided by the accelerator, VC, or startup organization.” If a member needs one or theirs appears invalid, AWS tells them to contact the provider directly. ( Applying for AWS Activate Credits: A step-by-step guide | AWS Startups )
AWS also explicitly says that if an applicant has an Org ID from an Activate Provider, they are eligible for that provider’s specific package levels and should ask the provider for more information. Directly on point for the tier-mapping question I’ve been asking.
Activate Providers are responsible for verifying their member startups’ affiliation and securing their Organizational IDs. ( OAS Template )
NVIDIA is a featured Activate Provider. ( AWS Startups )
Startups can reapply for a higher tier; the new award reflects the difference. AWS gives the worked example of $10K to $100K equalling a $90K difference. A $10K-to-$25K upgrade is squarely inside what AWS’s guidance contemplates.
NVIDIA’s own Inception page says members can request benefits through the Inception portal, including cloud credits from NVIDIA and partners. ( Join NVIDIA Inception for Startups )
“Contact AWS” doesn’t answer the whole problem. AWS owns final credit approval. NVIDIA owns, or at least controls, the upstream Inception provider process: the Benefits Catalog, the request state, provider affiliation, and the handoff AWS depends on. When AWS Activate rejects an application or can’t issue an Org ID, AWS’s documentation routes the member to the provider. That’s NVIDIA. The “AWS handles everything” line from Inception support isn’t consistent with what AWS publishes.
This isn’t an isolated case
Across this forum, members are getting stuck at different points in the same NVIDIA Inception × AWS Activate handoff. Ordered roughly by how closely each parallels mine:
@manisha4 (April 2026). $25K Grow Tier specifically. AWS rejected for a “domain mismatch” between root email and application domain that didn’t actually exist. After requesting manual review, the user got:
“After further review, we are unable to approve your AWS Activate Credit application… Due to Amazon’s internal policies, we are unable to provide specific details regarding the rejection criteria.”
Ticket closed without elaboration. NVIDIA’s forum reply: “it is definitely an Amazon issue. You will need to contact the Amazon support team to resolve this.”
@chelsey (March 2026). Same portal status as mine: “Follow up with the partner for the latest information.” AWS wanted an Org ID. She couldn’t find one in the Inception dashboard or approval emails. NVIDIA: “log into the Inception membership portal and you should find it in the benefits catalog.” She already had. That was the question.
@rick.gruenhagen (December 2025). AWS wanted NVIDIA’s Org ID. NVIDIA support told him:
“The review and approval of this benefit is solely managed by AWS, and they will provide you with an Org ID.”
Rick pushed back in plain terms:
“AWS very clearly wants Nvidia’s OrgID for the credit application on AWS Activate.”
NVIDIA then pivoted to “it should be in the portal.” He checked. Found offer codes but no Org ID. Thread closed without resolution.
Shashank.Nigam (December 2025), same thread. 15 days waiting for the $100K Org ID. NVIDIA:
“AWS fully manages the review and approval process for this benefit (including issuing the Org ID)… NVIDIA doesn’t have visibility…”
The same reply also said NVIDIA could reach out to AWS directly for a status update. So members are left unclear whether NVIDIA genuinely has no role after submission, or whether there’s a partner contact path NVIDIA can use to intervene. Which is it?
santhi (November 2025) stated the loop in one sentence:
“NVIDIA Inception support has clearly mentioned this is taken care by AWS Activate. AWS Activate Support is saying ORG ID is not provided by them.”
And:
“This has really hampered our product development since AWS costs are adding up for us.”
The thread was later closed by staff on the assumption that silence meant resolution. The OP never confirmed it was resolved.
jungwon423 (April 2025). AWS rejected the Activate Portfolio application explicitly because the provider hadn’t confirmed affiliation. The rejection told the applicant to contact the provider. He’d already emailed InceptionProgram@nvidia.com twice with no reply.
“AWS Activate continues to tell me that they’re waiting for confirmation from the provider (NVIDIA Inception).”
That’s a step a member cannot complete on NVIDIA’s behalf.
albert56 (January 2026). Got $10K, couldn’t apply for $25K. Same shape as my case. AWS’s own documentation explicitly says higher-tier applications can be valid after lower-tier credits, and tells members to confirm provider-specific package eligibility with the provider.
kwkelvin (May 2026) and prachidebnath (December 2025). Both stuck on the Inception portal before they could even submit. Popup blocked, “Request Benefit” button greyed out, benefit marked as requested without actually being requested. kwkelvin opened a second thread when the first one didn’t get an actionable answer. NVIDIA’s public reply:
“Your best bet for support is to reach out to the Inception team directly at inceptionprogram@nvidia.com.”
These last two aren’t my current blocker (my Airtable went through), but they’re directly relevant. It’s the exact provider-side state issue Inception cleared on our case in January. The fix exists. It just isn’t consistently available to members and isn’t documented anywhere members can find.
The pattern
Members get stuck at different points in the same NVIDIA Inception × AWS Activate handoff. Three distinct stages:
- Before submission. The portal can mark a benefit as requested even when the member hasn’t completed the partner form. The member then needs NVIDIA to reset the state. Sometimes Inception does this (our January case); often the member is told to email an alias and waits.
- After submission. The portal shows “NVIDIA Confirmed” or “Follow up with the partner,” while the member still can’t find the Org ID or verify which AWS Activate tier was mapped. (My current state. Chelsey’s too.)
- At provider-confirmation. AWS tells the member it’s waiting on NVIDIA. NVIDIA tells the member AWS manages the process. (
jungwon423,santhi.)
The common issue is the NVIDIA provider-side handoff, not AWS final approval.
The response template has also been consistent. Across at least 13 months, from April 2025 to May 2026, multiple NVIDIA staff members have given variations of three replies: “AWS manages this,” “email inceptionprogram@nvidia.com,” and “check the Benefits Catalog.” Members who’ve already done all three are left without a next step. The cases that did resolve mostly required going outside the documented flow. luke153’s $100K case in the thread above, for example, only got unstuck after a direct call with an AWS rep.
Worth saying: the Inception program does work for plenty of startups, and Inception support has been useful to us at points (the January state reset being one). The problem is specifically the cases where the handoff fails and the response is templated deflection rather than engagement.
What I’m hoping someone from Inception can address
Not asking for credit approval. Asking provider-side questions that AWS’s own documentation says to ask the provider.
1. Our specific case. The request currently showing as “NVIDIA Confirmed” on our portal: was it actually mapped to the $25K Grow Tier on the AWS side, or not? If it was, NVIDIA should help explain why AWS is treating it as blocked by our prior $10K award. If it wasn’t, NVIDIA needs to correct the Org ID / provider package / tier mapping. That’s the binary I’ve been asking for since the rejection, privately and otherwise. If Inception genuinely can’t see this, say so and tell me who can.
2. Who owns the Org ID / tier mapping at NVIDIA? AWS’s docs name the provider as the owner of Org ID and provider-package eligibility. NVIDIA is the provider here. A founder can’t confirm NVIDIA affiliation on NVIDIA’s behalf, and can’t correct a provider package or Org ID mapping inside NVIDIA’s Inception flow. When a member can’t verify what tier their request is attached to, who at NVIDIA handles that? If the genuine answer is “nobody, AWS does it all,” that contradicts AWS’s published guidance and is worth flagging openly. If it’s someone, members need the path.
3. The state-reset fix. The provider-side reset that worked on our case in January would have unblocked several of the people linked above. Is it documented anywhere? If not, can it be? Members shouldn’t have to discover that capability exists by accident. Its existence also has implications for how NVIDIA describes its role in the provider-side flow.
4. The threads above. Several closed on the assumption that silence meant resolution.
What would actually help
A clear, public explanation of the AWS Activate benefit flow through Inception, covering:
- where the Org ID / provider package comes from
- whether $10K, $25K, and $100K use different mappings
- what “NVIDIA Confirmed” actually means in the handoff
- how members can verify the tier attached to their request
- who handles provider-confirmation failures
- who owns escalation when AWS says the issue is provider-side
That would help founders, AWS contacts, and NVIDIA staff stop losing time to the same loop.
Why this is still public
Inception’s pitch is acceleration. GPU access, credits, network, a runway to scale. You sign up, you build against it, your stack and your cost base assume it’s there. The $25K Grow Tier exists for exactly the moment that work starts paying off and you need more compute.
So when the handoff breaks at that tier, it doesn’t break for someone still figuring out their idea. It breaks for someone who’s $10K in AWS compute deep, with customer pipelines tied to specific timelines, who suddenly has to rethink core parts of the business. The canned reply pointing back to an email alias lands very differently at that point.
I’ve been on the receiving end of this for four months. The threads above show I’m not the only one. New posts with the same blocker keep arriving at a steady cadence, going back over a year. Same dead-end in the private channels, based on my own correspondence and what other founders have described. More than a year of this pattern, and no one on the provider side has owned it.
For our case specifically, AWS has now offered a different credits path (Incremental Workloads Migrate) to unblock the immediate compute need. That solves our compute. It doesn’t solve the Inception × Activate handoff. It costs us continued access to the Inception network and wider program resources we joined for. And it does nothing for the next founder in the same queue.
We’re members in good standing. We meet every documented eligibility criterion. The $25K Grow Tier is a benefit the program publicly advertises. Being routed around it shouldn’t be the outcome.
So this post is essentially a last attempt to fix the situation. For us, before the migration path locks in and we lose Inception access either way. And for the people behind us, who’ll otherwise keep hitting the same wall.
The actual failure isn’t any single rejected application. It’s the absence of accountability for a known, recurring break in a program NVIDIA puts its name on. No one I’ve corresponded with has said “I own this, here’s what I’m doing about it.” Every reply has redirected somewhere else. Founders keep posting, keep getting templated answers, and either give up or end up on workarounds AWS has to construct for them.
If someone at NVIDIA is actually in a position to own the handoff (not just reply on this thread), please do. And if not, it would be useful to know who is, so future founders aren’t pushed through the same loop.
For other founders on these threads: if you’ve been in this, I’d genuinely like to hear how you’re holding up, and how you’re thinking about whether to keep pushing or take whatever workaround you can find. luke153’s experience suggests a direct AWS rep call may be the only working path on the $100K side. Is that the de facto route for $25K too? Is there a working flow nobody’s documented?
And if there’s anyone from AWS reading: the Inception × Activate handoff is the thing that’s breaking. The folks I’ve spoken to on the AWS side know it. Raising it here because the provider-side answers need to come from the provider. Happy to have AWS weigh in too.
Thanks.