The AWS ISV Partner Path is the AWS Partner Network track for companies whose product is software — and AWS has renamed it the Software Path, “to better reflect offering types, rather than partner types.” The path is a progression from Registered to Validated to Differentiated, and the AWS Foundational Technical Review is the gate between the first two.
Most ISVs meet the AWS Partner Network as a set of acronyms someone in alliances says confidently: FTR, ACE, ISV Accelerate, Validated. What none of them explains is the shape underneath — that these are stages in a sequence, that each one gates specific benefits, and that the marketplace listing you actually want sits on top of them.
Here is the sequence, with the current names, and what each stage is for.
What is the AWS ISV Partner Path?
The AWS ISV Partner Path is the AWS Partner Network engagement track for organizations that build software. AWS now calls it the Software Path, and describes it as being “for organizations that develop software that runs on or is integrated with AWS.”
It is one of five paths a partner can enrol in:
| Path | AWS’s description |
|---|---|
| Software Path (formerly ISV Path) | “For organizations that develop software that runs on or is integrated with AWS” |
| Hardware Path | ”For organizations that develop hardware devices that work with AWS” |
| Services Path | ”For organizations that deliver consulting, professional, managed, and value-added resale services” |
| Training Path | ”For organizations that sell, deliver, or incorporate AWS training” |
| Distribution Path | ”For organizations that recruit, onboard, and support their partners to resell and develop AWS solutions” |
The rename matters more than it looks. Paths describe what you offer, not what kind of company you are — which is why a company can sit on more than one. An ISV that also delivers implementation services belongs on the Software Path and the Services Path, and gets a different set of benefits from each.
One practical note before you enrol in anything: AWS states that “if you need to remove a Partner Path from your account, you must contact APN Support for assistance.” Enrolment is easier than un-enrolment. Choose deliberately.
The three stages, and what each one is for
AWS describes the journey as running “from enrolled to differentiated status,” tracked in the Partner Scorecard — “your tool to track progression of your AWS Partner path and tier requirements.”
Registered. You have an APN account and have selected a path. This is administrative. It gets you into Partner Central and the training and enablement material, and nothing more. Plenty of ISVs sit here for a year without realising there is anywhere else to be.
Validated. The stage that changes what you can do. Reaching it means AWS has technically reviewed your product, and it is the entry requirement for the programs that actually carry commercial value. The ISV Workload Migration Program, for example, requires partners to “complete an AWS Foundational Technical Review and be at a Validated stage, offer a SaaS solution on AWS, and have a qualified migration use case.”
Validated is also a status you can lose. AWS: “Partners on the Software Path are required to submit FTR renewal requests before the due date to maintain the Validated stage.”
Differentiated. The stage where AWS is willing to point customers at you: competencies, service-ready designations, solution-level badging, and deeper field engagement. AWS notes that some benefits — the BOX Program among them — are “available to partners at the Validated or Differentiated Stage in AWS Partner Central.”
The specific requirements for each stage are published in Partner Central and change; the Partner Scorecard is the authoritative view of where you stand against them. Read it there rather than from a blog, including this one.
The Foundational Technical Review is the whole gate
If there is one thing to take away, it is this: the FTR is the step between “we have an AWS account” and “AWS will engage commercially.”
AWS describes it as “the cornerstone of engagement,” formerly known as the Technical Baseline Review, and says it “enables AWS Partners to identify and remediate risks in their products or solutions based on AWS best practices related to security, reliability, and operational excellence.” It is “created in alignment with AWS Well-Architected Framework pillars and is led by an AWS Partner Solutions Architect (SA) in a one-on-one engagement.”
Three practical consequences:
It is a real technical review, with remediation. It is scoped to one solution, not to your company, and you will be asked to fix things. Budget engineering time, not just an alliances lead’s calendar.
It unlocks solution-level badging — the AWS-issued designation that appears against your product rather than against your company name.
It expires. AWS extended the renewal period “from 2 to 3 years for partners on the Software Path,” which is generous but not indefinite. An FTR that lapses takes Validated status with it, and the programs that depend on Validated go with that. Put the renewal date in the same calendar as your marketplace agreement renewals.
How the path relates to selling on AWS Marketplace
This is the part most often muddled, so it is worth stating plainly: the Software Path and AWS Marketplace are related but separate.
You register as an AWS Marketplace seller to list and transact. You progress through the Software Path to unlock AWS Partner Network benefits. The two reinforce each other but neither is a prerequisite for the other in the way people assume.
Where they genuinely connect:
Co-sell runs on the partner relationship, not the listing. Submitting opportunities through APN Customer Engagements — and getting AWS sellers engaged on them — depends on your partner standing, not on having a listing. The AWS ACE guide for ISV sellers covers how that pipeline actually works.
Partner funding is gated on program status. POC funding, migration programs, and market development funds each have their own eligibility, and several depend on stage. AWS partner funding programs covers which is which.
The marketplace listing is where the money moves. Progression gets you AWS attention; the listing turns that attention into a transaction. The AWS Marketplace seller’s guide covers the listing side.
A useful way to hold it: the Software Path is your relationship with AWS. AWS Marketplace is your relationship with the buyer, running on AWS’s billing rails.
A sequence worth following
For an ISV starting from nothing, this order wastes the least time:
- Enrol in the Software Path. Free, fast, and it gates everything else.
- Register as an AWS Marketplace seller in parallel. The listing work and the partner work are independent, so run them concurrently rather than in series.
- Scope and schedule the FTR against one solution. This is the long pole — treat it as an engineering project.
- Reach Validated, then check which programs that opens for your specific motion. Do not chase all of them.
- Get co-sell hygiene right before pursuing Differentiated. AWS field engagement is earned through pipeline discipline, and nothing substitutes for opportunities that are submitted accurately and kept current.
- Diarise the FTR renewal. Three years passes quickly and the status drops without ceremony.
Frequently asked questions
What is the AWS ISV Partner Path? It is the AWS Partner Network track for companies whose offering is software. AWS has renamed it the Software Path, describing it as being for organizations that develop software that runs on or is integrated with AWS.
Why did AWS rename the ISV Path to the Software Path? AWS renamed it “to better reflect offering types, rather than partner types” — paths describe what a partner offers, which is why one company can enrol in several.
What are the AWS partner stages? Registered, Validated, and Differentiated. AWS describes the journey as running from enrolled to differentiated status, tracked in the Partner Scorecard in AWS Partner Central.
What does the AWS Foundational Technical Review unlock? It is the gate to Validated stage and to solution-level badging. AWS describes it as helping partners identify and remediate risks based on best practices for security, reliability, and operational excellence.
How often does the FTR need renewing? Every three years for partners on the Software Path, extended from two. Partners must submit FTR renewal requests before the due date to maintain Validated stage.
Do I need to be on the Software Path to sell on AWS Marketplace? They are separate registrations. You register as a marketplace seller to list and transact, and progress through the Software Path to unlock partner benefits such as co-sell engagement and funding.
Takeaways
- The ISV Path is now the Software Path. Paths describe what you offer, so a company can enrol in more than one.
- The stages run Registered → Validated → Differentiated, tracked in the Partner Scorecard.
- The Foundational Technical Review is the gate to Validated and to solution-level badging. It is an engineering project, not a form.
- Validated is losable. The FTR renews every three years for Software Path partners, and lapsing takes dependent benefits with it.
- Partner path progression and AWS Marketplace seller registration are separate. Run them in parallel.
- Requirements change. The Partner Scorecard in Partner Central is the authoritative view, not any article about it.
Partner standing is what gets AWS engaged; a working co-sell motion is what keeps them engaged. See how co-sell automation in Suger syncs opportunities between your CRM and AWS Partner Central — so pipeline hygiene stops depending on somebody re-typing deals into a portal.
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.