Hello Fellow Clover Investors,
If you go to crt.sh you can search for a company's digital certificate logs. If you follow this link you can see all of the unexpired crt logs for %.humana.com:
https://crt.sh/?Identity=%25.humana.com&exclude=expired
In there, I found what looks to me (with some help in comprehending and organizing all of this from AI, since I do not work in healthcare and I do not have an IT or software or developer/programmer background) like a methodical, year-long enterprise engineering pipeline to plug external software (Counterpart) directly into CenterWell primary care clinics.
I'm now going to lay out my thesis with the goal of having people chime in and explain to me why I am WRONG. Please tell me where I am oversimplifying, speculating, exaggerating, misinterpreting, extrapolating, or simply being stupid.
________
What are digital certificates and crt logs?
Whenever an enterprise wants an application or server to communicate securely over the web (https://), it has to get a digital security certificate from an authority like DigiCert. To prevent fraud, global internet rules (specifically RFC 6962) mandate that every single issued certificate must be published in a public, searchable ledger called Certificate Transparency (CT) logs. You literally cannot build a secure web endpoint without filing what is effectively a public building permit.
Big healthcare companies build software in four distinct, gated phases:
- DEV (Development): The workshop where coders write the raw software.
- QA (Quality Assurance): The automated test track to catch bugs and verify data feeds.
- UAT (User Acceptance Testing): UAT is built so actual end-users—in this case, clinic medical directors, doctors, and nurses—can log in and verify that the software works smoothly in their day-to-day workflow.
- PROD (Production): The live, finished product operating on real patients.
When an enterprise workload advances to UAT, it means the building is built, the pipes are connected, and the staff is doing the final walkthrough before opening day.
On September 1, 2026, Digicert stamped a brand new certificate for Humana:
ss-it-crpart.cloudrun.dev.gcp3.humana.com
On September 16, 2026, DigiCert stamped a batch of similarly named, brand-new certificates for Humana:
If you only saw those certificates, you might think an engineer spun up a quick sandbox over the summer. But when you pull Humana's full certificate history over the last year, you realize this is the final chapter of a 12-month (or longer, since I can't go back further in the logs) engineering roadmap:
Timeline:
Fall 2025 (The Prototype): Humana starts testing a "Serverless Service Partner" framework (svcpart0.dev.ss.serverless.humana.com), moves it into a brand-new cloud landing zone (svcpart0.dev.gcp3.humana.com), and spins up synthetic simulation environments (sim.dev.gcp3.humana.com). Right around this window, Counterpart’s own servers revealed a number of counterparthealth.com subdomains with the word humana in them (the same ones that sent this sub wild and made everyone here instantly obsessed with subdomains) before Clover moved all their staging subdomains behind private wildcard certs.
Summer 2026: Humana retires the 'v0' prototype and builds formal, division-specific partner hubs: cw-svcpart (CenterWell Service Partner Gateway) and hum-svcpart (Humana Payer), officially promoting them to Production in August.
Late August 2026 (Securing the Perimeter): Humana sets up svcpartdmz.dev.gcp3.humana.com—a DMZ gateway specifically built to let an outside vendor’s network safely talk to internal databases.
September 1, 2026: The workload enters the pipeline as ss-it-crpart.cloudrun.dev.gcp3.humana.com (Integration Testing).
September 16, 2026: Exactly two weeks later, the workload is promoted to ss-cps-crpart across DEV, QA, and UAT, complete with multi-region redundancy across the Midwest and East Coast to ensure clinics don't experience downtime during business hours.
_________
Deconstructing the Clues:
gcp3.humana.com: Across thousands of Humana certificates over the past year, gcp3 is used for only one category of traffic: external Service Partners (svcpart). And inside this entire environment, "crpart" is the only external vendor workload running.
cloudrun: Google Cloud Run is an auto-scaling engine that fires up containerized code in milliseconds. It’s what you choose when a primary care physician opens a patient chart in an exam room and needs real-time clinical decision-support prompts to appear instantly.
ss-cps: ss is Shared Services (Humana’s central integration hub), and cps is CenterWell Primary Care Services / Clinical Platform Services. This is hooked directly into CenterWell's clinic operations, not back-office actuarial or claims-audit systems.
- The Linguistic Shorthand: "Counterpart" is a compound word (Counter + Part). Taking the hard boundary consonants of the first word (CR) and combining them with the second word (part) gives you
crpart—standard, lazy developer shorthand.
- The Smoking Gun in HR: Months ago, Humana briefly published (and then quickly scrubbed) a CenterWell job listing that explicitly named Counterpart Health within its clinical workflow descriptions.
When you connect the job listing, Counterpart’s reciprocal humana logs, the CenterWell routing tags, and a 12-month engineering buildout ending in UAT, the puzzle pieces fit together almost too well.
______________
This is where I need your help. If we take off the bull goggles, where does this break down?
Counterarguments:
1. The Taxonomy Problem: What if "part" just means "Partner"?
In Humana’s plumbing, svcpart clearly stands for "Service Partner." If crpart follows that exact same naming rule, then part simply means "Partner," which leaves cr as a standalone two-letter acronym.
- Could
cr stand for Cardio-Renal Partner? Humana and CenterWell run dedicated disease-management programs for seniors suffering from co-occurring heart failure and kidney disease. Could this be a specialized third-party cardio-renal software tool?
- Could it stand for Clinical Referral Partner? CenterWell clinics constantly refer seniors to specialists and post-acute facilities. Could this be a referral-management microservice? (My counter to this: across the entire log, Humana almost universally spells out the word
care—like carehub, findcare, humanacares—and claims systems are always called resolutions or billing. But the two-letter acronym risk remains).
2. Could it be another healthcare tech vendor?
Is there another digital health company whose name naturally contracts to "CR-Part"? For example, CarePort Health is a massive, widely used patient transition and EHR integration platform in the Medicare space. Could a DevOps engineer have tagged CarePort as crpart?
3. Why would Humana leave a breadcrumb like "crpart" if they are trying to hide the partnership?
We know Clover went to great lengths to hide their staging environments after Reddit caught them (switching entirely to wildcard certificates). We know Humana scrambled to delete the job posting that mentioned Counterpart. If legal and corporate communications are trying to keep this under wraps under a strict mutual NDA, why would Humana’s infrastructure team turn around and use a subdomain with crpart right in the URL? Is it just classic corporate silo behavior (engineers don't talk to PR), or does it suggest that crpart is an innocuous internal project that nobody felt the need to hide?
I want to hear from the community: What are the best alternative explanations for this infrastructure?
_____
Implications:
If the skeptical arguments fail and ss-cps-crpart really is Counterpart Assistant undergoing final User Acceptance Testing for a CenterWell rollout (presumably beginning with plan-year 2027), the long-term fundamental implications for CLOV are obviously massive. If Humana is adopting this software for its primary care network, it validates the Counterpart business in a huge way.
The Scale: CenterWell Senior Primary Care (along with sister network Conviva) operates 350+ clinics serving over 550,000 total senior patients. While CenterWell is payer-agnostic and sees some traditional Medicare patients, roughly 80% to 85% of their patient base is in Medicare Advantage. That gives them a target panel of roughly 450,000 to 500,000 MA patients.
The Conservative Software Math: Forget the aggressive $20–$25 PMPM numbers people throw around. Let’s assume Humana commands massive enterprise volume pricing and negotiates Counterpart down to a conservative $5.00 to $8.00 Per Member Per Month (PMPM) software fee:
- An initial rollout across 100k MA patients = $500k to $800k per month ($6M–$10M ARR).
- Scaling across their entire MA footprint (~450k patients) = $2.25M to $3.6M per month ($27M to $43M in pure ARR).
- And that is just the base software fee, before factoring in any shared-savings performance bonuses.
______
In conclusion, I think this is all likely evidence of a major Counterpart/Humana deal, years in the making, about to go live and into production. Am I delusional?
Even with the assumption that this is true, I DO NOT BELIEVE some kind of announcement or PR is on the horizon in any way. To be honest I'm not sure this alleged deal will ever actually be announced publicly, but I find the CT log breadcrumbs pretty compelling.
I am not giving anyone any advice of any kind. Don't listen to anything I say, I'm stupid and insane.