On this page 8 sections
If you’ve raised a round in the last 12 months, somewhere in your founder Slack there’s a thread about AWS Activate credits. The numbers get traded around like trophies. “We got the $100K.” “We only got $25K, why?” “Does anyone know if they expire?”
This post is the operator-level version of those conversations. It covers who qualifies in 2026, how the tiers work, the application path that gets you to the top tier fastest, and the expiry rules that quietly cost teams six figures. It ends on the part most posts skip: where you spend the credits matters more than how many you have.
What AWS Activate actually is
AWS Activate is AWS’s startup program. You apply through an accredited partner (VC, accelerator, incubator) or directly, and if you qualify you get a credit balance applied to your AWS account, plus business-tier AWS Support for the duration of the program.
There are two tiers in 2026 worth knowing:
| Tier | Credit amount | Eligibility | Validity |
|---|---|---|---|
| Activate Founders | Up to $1,000 | Self-funded, bootstrapped, or pre-seed without an associated org | 2 years |
| Activate Portfolio | Up to $100,000 | Backed by an accredited partner (VC, accelerator, incubator) | 1 to 2 years, partner-dependent |
The headline most founders chase is the $100,000 Portfolio tier. The cap your startup qualifies for inside Portfolio depends on your investor or accelerator’s negotiated tier with AWS.
Y Combinator, Sequoia, a16z, Accel, and the larger accelerators usually unlock the full $100K. Smaller funds or early-stage angels often unlock $5K to $25K. The partner’s tier decides the amount, so pitching your business harder doesn’t move it.
How to actually get the credits
The move that matters most is applying through the partner whose tier is highest. If you have a choice (say your accelerator gets $25K but your lead investor’s fund gets $100K), apply through the higher one. You can only redeem once.
The Portfolio application flow in 2026 has five steps.
1. Get your partner’s referral code or org ID
Most VCs have a portfolio operations lead who emails you the link in the first week after close. If they haven’t, ask.
2. Create your AWS account (or use the existing one) and link it to AWS Organizations
Credits apply at the account level. If you plan to run multi-account, set up Organizations first and then apply, so credits land in the management account and propagate.
3. Fill out the Activate Portfolio application
It asks for company name, website, AWS account ID, partner referral, expected workload and founding team. Approval typically takes 5 to 10 business days.
4. Confirm the credit balance landed
Look under Billing console > Credits, and check the expiration date.
5. Activate Business Support for the credit period
This unlocks 24/7 production-system support and faster case response times, which matters once you’re running production traffic.
Applications usually stall for one of three reasons:
- There’s no business website. A landing page with company name and contact info is enough, though a subdomain on Notion doesn’t always pass.
- AWS can’t find a matching partner record. If your investor signed your SAFE through a special-purpose vehicle, AWS sometimes can’t match the partner, so ask your VC for the canonical entity name on the Activate program.
- The account was already redeemed. Activate credits are once per startup, and if a co-founder or technical advisor used the same AWS account on a prior project, you may be flagged.
The expiry trap
The detail that costs teams the most is simple: Activate credits expire.
Portfolio credits typically have a 12 to 24 month validity from the date they’re applied. After that date the unused balance is gone, with no rollover and no extension, even if you ran short of runway.
In practice, a startup that raises a $3M seed in month 0 and gets $100K of credits in month 2, but doesn’t have meaningful AWS spend until month 8 or 9 (because it’s still in build mode), burns through maybe $20K to $30K of credits before expiry. The rest evaporates.
There are three ways to avoid this:
- Front-load infrastructure. Move workloads onto AWS earlier. Even staging and CI/CD running on EC2 spot instances eat credits and give you real production telemetry to debug against.
- Use the credits for everything they cover. Activate credits apply to most AWS services: EC2, RDS, ElastiCache, S3, CloudFront, Lambda, EKS, ECS, EBS, NAT Gateway, data transfer. They don’t apply to Marketplace purchases, AWS Support fees beyond Business tier, or third-party reserved instances, so default the entire stack onto credit-eligible services.
- Run your platform layer inside your own AWS account. Most teams miss this one, and it’s the subject of the next section.
Where credits leak: the platform-markup problem
Most early-stage startups run their applications on a managed PaaS such as Heroku, Render, Railway or Fly.io. The PaaS bills you for compute at a marked-up rate (typically 2x to 4x the underlying AWS or GCP price), and that bill goes to the PaaS company rather than to AWS.
Your AWS Activate credits sit in your AWS account and cover AWS services running there. A Heroku bill is outside their reach.
So a startup with $100K of Activate credits, running entirely on Heroku, sees roughly this picture over 18 months:
| Line | Amount |
|---|---|
| Heroku spend at typical Series A scale ($2K to $5K/month) | $40,000 to $90,000 |
| AWS Activate credits redeemed (no AWS workloads) | ~$0 to $5,000 |
| AWS Activate credits expired unused | $95,000+ |
The credits were free dollars from your investor’s relationship with AWS, earmarked for you, and they expired unused.
The framing we use at Ownkube is that your AWS Activate credits were meant for AWS, and a PaaS vendor’s margin can’t spend them. The only way to capture them is to run your compute, databases, and storage inside an AWS account you control, billed by AWS directly.
Managed PaaS is fine in principle. The problem is paying twice without noticing: once to AWS for credits you don’t use, and once to the PaaS for compute that could have run on AWS.
A worked example: capturing the credits without the ops burden
Take a hypothetical seed-stage SaaS with one web service, two background workers, a 50GB Postgres, and rotating PR preview environments. That’s roughly 8 vCPU and 16 GB of production pods plus 4 vCPU and 8 GB for previews.
Option A: Heroku
The stack is Heroku Performance dynos, Postgres Standard-2, Redis Premium-1 and preview apps, at an approximate monthly bill of $2,400 to $3,200.
| Line | Amount |
|---|---|
| Activate credits redeemed | $0 |
| Year-1 cash out the door | ~$30,000 to $38,000 |
| Activate credits left expiring | ~$70,000+ |
Option B: managed Kubernetes (EKS) in your own AWS account
The stack is an EKS control plane, 2 multi-AZ node groups, RDS Postgres Multi-AZ, ElastiCache and an ALB, at an approximate monthly AWS bill of $1,100 to $1,600.
Activate credits cover 100% of the bill until they run out, so year-1 cash out the door is $0 until the credits are exhausted (typically month 8 to 14 at this scale). The DevOps overhead is significant unless something abstracts it, and you’d typically need a DevOps engineer or equivalent.
Option C: platform layer in your own AWS account
You run Ownkube in your own AWS account: Starter (free forever, one AWS instance) for early development, and Production ($5 per vCPU + $1 per GiB RAM) once you scale to multiple nodes. The AWS bill is the same as Option B, paid to AWS directly, and Activate credits cover 100% of it until exhausted.
Builds, deploys, TLS, a ready-to-share URL, managed Postgres, logs, metrics, and rollbacks come with the platform instead of being separate projects. Year-1 cash out the door is a small platform fee (free on Starter, $5 per vCPU + $1 per GiB RAM on Production).
Option C captures the credits and skips the DevOps hire, which is the combination most seed and Series A founders we talk to are after.
When credits aren’t the right reason to choose AWS
If your team doesn’t need AWS-specific capabilities, don’t pick AWS just for the credits. The credits expire, and you live with the architecture decision long after.
Cases where AWS is a fine technical fit regardless of credits:
- You need compliance certifications (SOC 2, HIPAA, FedRAMP) and AWS’s evidence story is shortest.
- You need specific AWS services (S3, DynamoDB, Bedrock, SageMaker) that your application directly depends on.
- Your enterprise customers contractually require their data to be in AWS, in their region, under their KMS keys.
- You expect to scale into spot instances, multi-AZ, multi-region, or private VPC peering with vendors.
Cases where AWS plus Activate is the wrong reason:
- “We just want the credits.” If you’re going to run on a different cloud anyway, the credits won’t save you.
- “We’ll migrate later.” Migration is expensive, and the bill you avoid by not migrating is usually larger than the credits you’d have captured.
Decision checklist
Before you apply, confirm:
- You have a partner referral that unlocks the highest tier you’re eligible for.
- Your AWS account is set up under Organizations (or you’re fine starting in a single account and migrating later).
- You have a realistic plan to spend the credits inside the validity window.
- Your application workloads are or will be hosted in AWS, not on a marked-up PaaS that doesn’t accept Activate credits.
- You have a strategy for handling the recurring DevOps work (hire, software, or shared with backend team).
If you can’t tick the last two, you’ll watch most of the credits expire unused.
Closing
AWS Activate credits are one of the strongest economic levers a funded startup has in 2026. Up to $100,000 of free AWS spend, applied to compute, databases, storage, and edge, runs production for most seed-stage SaaS for a full year. The catch is that the credits only land if your stack runs in your AWS account, billed by AWS directly, without a platform markup in between.
If you want every credit dollar to land on your own AWS bill and skip the DevOps hire, Ownkube runs in your own AWS account with builds, deploys, TLS, managed Postgres, and autoscaling built in, and you pay AWS directly for the compute. Starter is free forever on one AWS instance; Production is $5 per vCPU plus $1 per GiB RAM per month once you scale.
Activate credits do not apply to Ownkube Compute, our hosted option, which runs on a prepaid wallet from $5 a month. See Ownkube pricing for both. Deploy my first app.