The trouble with a mobile phone is that it never travels alone. It brings a little procession of identifiers, towers, switches, billing records and roaming partners wherever it goes. The screen may show a weather app. The network sees an itinerary. John Doyle built Cape because he became convinced that no clever toggle on the screen could tidy up the parade underneath.
This is an inconvenient belief for a founder. If the problem were merely a sloppy app, he could build a neater one. If it were a carrier with weak defenses, he could sell advice to carriers. Both businesses would have been cheaper. Doyle instead followed his diagnosis all the way down and arrived at a peculiar destination: to protect a phone from the network, he would have to become the network.
Cape, founded in 2022, rents access to towers but operates its own software-based mobile core. The distinction is easy to miss and expensive to build. A tower moves the radio signal. The core decides who the subscriber is, how the phone authenticates, where traffic goes and what records remain after the call ends. Doyle's wager is that this quiet machinery can be designed to know less.
A résumé with no obvious destination
Doyle studied computer science at Knox College, graduating in 2002. Then came the Army. From 2003 to 2008 he served in U.S. Army Special Forces as a Green Beret, working in communications. The sequence matters. Communications in a classroom can be elegant; communications in the field must work when the surroundings are untidy and the consequences refuse to remain theoretical.
His next move looked like a turn away from engineering. Doyle entered Harvard Law School in 2009, worked with the Harvard Legal Aid Bureau and earned his J.D. in 2012. He passed the bar and quickly concluded that he did not want to be a lawyer. This could be filed under expensive self-knowledge. Instead, he joined Palantir and went back to code.
At Palantir, Doyle started as a forward-deployed engineer, the kind of job that puts code beside the people who must use it. From 2017 until his departure in 2022, he ran the company's national security business. Those years supplied the missing connection between his earlier lives. He understood software, military operations, regulation and the unlovely mechanics of selling technology to government. He also gained a close view of the vulnerabilities embedded in commercial cellular networks.
Vulnerability became curiosity, and curiosity became what Doyle has called obsession. Phones had evolved into portable vaults containing conversations, movements, contacts and credentials. Yet the infrastructure beneath them still relied on fixed identifiers, long-lived records and trust passed from one network to another. The fashionable security conversation happened at the edge, around encrypted apps and devices. Doyle kept looking toward the middle.
The $5 million lesson
Cape began with confidence of the useful, hazardous variety. Doyle believed a $5 million seed round, a few more engineers and some standard vendors might be enough to switch on the network. It took roughly $50 million. Telecom greeted the new entrant with integration work, regulation, SIM logistics, roaming arrangements and enough legacy convention to furnish a museum.
Naivete was not the business plan, but it helped the company cross a threshold that experienced telecom operators might have politely avoided. Once inside, the team learned where standard components fell short and replaced some of them. The choice created a company with more surface area than a privacy app and, if it worked, more control.
One encounter made the industry's habits vivid. While testing software from a vendor that helps carriers comply with lawful-intercept requests, Cape's reliability engineers unpacked an installer and found an unencrypted text file with client usernames and passwords. Cape notified the vendor and chose another route. Three months later, news of the Salt Typhoon intrusions exposed how foreign hackers had penetrated major telecommunications systems, including interfaces associated with lawful interception. The abstract risk had acquired a plot.
Every handoff is useful. Every permanent identifier or retained record can also become a place to follow the subscriber.
A carrier that tries to forget
Most companies treat data as an asset. Cape treats at least some of it as a liability with a short fuse. Its disappearing call logs are designed to delete detailed call-data records after one day. Its identifier rotation changes how a phone presents itself to the network every 24 hours. Secondary numbers, secure roaming and controls against SIM swaps follow the same theory: a carrier should make surveillance and account theft harder by reducing the durable handles they depend on.
“One of our first design principles was to minimize the amount of data that we collect and the amount of data that we store,” Doyle said when the call-log feature launched. It is the sort of sentence that sounds almost impolite in an industry built around records. Forgetfulness, usually a defect in an operator, becomes a product feature.
There are limits to the romance. Cape is still a regulated carrier. It must connect to a world it did not design, meet legal obligations and persuade customers that invisible infrastructure deserves a monthly bill. Its model is less a clean break than a controlled argument with the existing system.
Guam, proof and the stubborn phone
The argument reached strategic ground in Guam. Cape worked with U.S. naval forces on a pilot designed around a severe assumption: what if the physical telecommunications infrastructure underneath the service could not be trusted? Instead of cleaning every compromised component, Cape proposed running a fresh software-controlled network across it, protecting the path from radio infrastructure back to its mobile core.
The pilot finished ahead of schedule and under budget. More important to Doyle, it met the success measures agreed at the start. He has admitted that the painstaking work of defining those measures felt irritating inside Cape. It also turned a promising demonstration into evidence that could travel through a large institution without its original advocates in the room.
That is the operator in Doyle: impatient with process, then respectful when process makes the result legible. His career has placed him on both sides of the table. He knows the startup's desire to move now and the government's need to explain later. Cape's board-level connection to Vannevar Labs, where Doyle has served, fits the same pattern of defense technology built by people who understand procurement as a system rather than a complaint.
For military personnel, the stakes include location and operational patterns. For a journalist, executive or ordinary subscriber, they may involve identity theft, stalking, data brokerage or the private map of daily life. Cape's dual-use proposition is that these are not separate technical problems. The same infrastructure can serve a naval exercise and a family plan because both users carry the same stubbornly indispensable object.
From premise to proof
Cape emerged from stealth in 2024 and opened a consumer beta with Proton in March 2025. The network moved out of beta in January 2026. Two months later, Cape announced a $100 million Series C at a $900 million valuation, bringing its stated funding total to $191 million. The new capital was earmarked for government, enterprise and consumer expansion, deeper core infrastructure and a larger team.
The milestones offer a neat arc, but Doyle's own account is less polished. The company underestimated the cost. It entered an industry its founding team barely knew. It heard that consumers would not pay for privacy and discovered that government cellular purchasing had few welcoming doors. The achievement is not that Cape avoided these facts. It is that the facts arrived early enough to influence the machine.
Doyle's ambition now stretches internationally and, in his phrase, to space. Cape says its network reaches across 190 countries through partner infrastructure, and its broader design treats physical networks as components rather than kingdoms. It is an elegant idea with a ferocious amount of paperwork attached.
The visible evidence remains wonderfully small: a carrier name in the corner of a screen. Beneath it sits Doyle's long route through code, combat communications, law, national security and telecom. Cape asks the phone network to do something modern technology rarely volunteers to do. Remember enough to connect a person. Forget enough to leave them alone.