Who Owns RSA Archer — and Is It Going Away? A Factual Explainer

If you searched "is RSA Archer end of life" or "who owns Archer now," you're likely an Archer customer trying to make a renewal or platform decision with incomplete information — because clear, non-vendor, non-alarmist answers to these questions are genuinely hard to find. This page is the factual version. It was last reviewed in July 2026; ownership facts are dated so you can verify them independently.

GRC Migrate is independent — no commissions from Archer, Vanta, Drata, or any platform vendor, ever. We have no stake in whether you stay on Archer or leave it.

The direct answer: Archer is not end-of-life

RSA Archer is not discontinued, not end-of-life, and not in wind-down. Archer operates today as a standalone company, continues to release product updates, maintains its customer base across regulated industries, and is actively sold. Any claim to the contrary is wrong, and you should treat sources making that claim as unreliable.

What is true: the product has changed hands several times in the past decade, it is now owned by the private equity firm Cinven — which acquired Archer in 2023 — and those transitions have left many customers uncertain about roadmap direction, support experience, and pricing trajectory. That uncertainty is a legitimate thing to evaluate — and it is a different thing from end-of-life. This page treats the two separately, because conflating them is how bad decisions get made in both directions.

The ownership timeline — dated facts

2001–2010: Archer Technologies. Archer began as an independent GRC software company, Archer Technologies, founded in 2000–2001.

2010: EMC acquires Archer. EMC Corporation acquired Archer Technologies in January 2010 and placed it under its RSA security division — which is where the "RSA Archer" name comes from.

2016: Dell acquires EMC. Dell's acquisition of EMC brought RSA — and Archer with it — under Dell Technologies.

2020: Dell divests RSA. Dell sold RSA to a consortium led by Symphony Technology Group (STG) in a deal announced in February 2020 and completed later that year. Under STG, RSA's businesses were progressively separated, and Archer began operating as a standalone business unit.

2023: Cinven acquires Archer. The private equity firm Cinven announced its agreement to acquire Archer from STG in January 2023, with the transaction completing that year. Archer has operated since then as a standalone company under Cinven ownership.

Today: Archer continues as an independent company focused on integrated risk management, with ongoing product releases and an active enterprise customer base — particularly in financial services, insurance, healthcare, and government, where its configurability and regulatory depth are genuine strengths.

What PE ownership typically means for enterprise software customers

This section is deliberately general. These are patterns commonly observed across private-equity-owned enterprise software as a category — framed as considerations customers evaluate, not predictions about what Archer's owners will or won't do. Some PE-owned software companies invest heavily and improve; others optimize for margin. Knowing the general patterns tells you what questions to ask, not what the answers will be.

Pricing discipline. PE ownership typically brings sharper attention to revenue per customer. In practice, across the category, that often means firmer renewal pricing, less discounting flexibility, and more structured escalation. If you've noticed your renewal conversations getting more formal, that's consistent with the pattern — and it makes the negotiation levers on our Archer renewal cost page more relevant, not less.

Support and organizational restructuring. Ownership transitions commonly involve reorganization — support teams, account management, and partner ecosystems can change shape. Some customers experience no difference; others report turnover in the account relationships they'd built. The practical takeaway is to ask for support SLAs in writing rather than relying on relationship history.

Roadmap consolidation. PE-owned software companies typically concentrate investment on the segments and use cases where they're strongest — for Archer, that is large regulated enterprises. Customers in the core segment often see continued investment; customers at the edges of the target market sometimes find the roadmap moving away from their needs. A mid-market company running a handful of frameworks on Archer should honestly assess which side of that line it's on.

None of this is unique to Archer, and none of it is a reason to panic. It is a reason to go into your next renewal with clear questions — which is the next section.

Why customers ask the end-of-life question anyway

Search data shows a steady stream of "archer end of life" and "is archer discontinued" queries — for a product that is neither. Three things drive this, and they're worth naming honestly:

Ownership churn reads as instability. Four ownership configurations in roughly thirteen years (EMC, Dell, STG, Cinven) is a lot of change for a system of record. Customers who lived through the transitions reasonably wonder what's next, even when the product itself is stable.

The brand history is confusing. "RSA Archer" is still the common name, but RSA and Archer have been separate companies since the STG-era separation. Customers who search for RSA product announcements and find Archer absent sometimes misread that as the product disappearing, when it actually moved.

Ecosystem gravity has shifted. The compliance automation category (Vanta, Drata, and peers) has absorbed much of the mid-market conversation. When the tools people talk about change, incumbents get asked existential questions — regardless of their actual health.

If you arrived here worried, the honest summary is: the product is alive and actively developed; the uncertainty is about direction and cost trajectory, not existence. Evaluate accordingly.

Questions to ask at your next renewal

These are worth asking whether you intend to stay or not — the answers are useful in either direction, and a vendor's willingness to answer them in writing is itself information.

• Roadmap commitments: What are the committed investments in our licensed use cases over the next 24 months? Which capabilities on the public roadmap apply to our deployment model (SaaS vs on-prem)?
• Support SLAs: Can our support response times and escalation paths be stated in the contract rather than in policy documents that can change? Who is our named account contact, and what happens if that changes?
• Price protection: Will you cap renewal escalation in writing for a multi-year term? What happens to module pricing at the next renewal if we add a use case mid-term?
• Version and hosting continuity: For on-prem customers — what is the support horizon for our current version, and what would a SaaS transition cost and involve?
• Exit terms: What are our data export rights and assistance commitments if we ever leave? (Asking this at renewal, when you have leverage, beats asking at departure, when you have none. Our Archer data export guide covers what extraction actually involves.)

If you're evaluating alternatives anyway

For some customers, the ownership question is the prompt that starts a broader evaluation that was already due — the program has consolidated to a few frameworks, admin capacity has thinned, and the honest question is whether an enterprise GRC platform still matches the program's shape. If that's where you are, start with the independent Archer alternatives guide, take the legacy migration assessment for a complexity score, and see the Archer vs Vanta comparison for the category-level fit question. And if the evaluation concludes that Archer remains the right platform for your program — that's a perfectly good outcome, now backed by evidence.

Facts on this page were last reviewed in July 2026. Ownership events are dated so you can verify them from primary sources. If you spot an inaccuracy, tell us — this page's usefulness depends on it staying correct.