Company
Sovereign Inc.
A Delaware corporation. It develops Tunnel Sovereign, the sovereign communication authority platform, which is available for controlled evaluation.
- Delaware corporation
- Founded by Francesco Tripepi
- Available for Controlled Evaluation
Corporate identity
The company, and the platform it develops.
Two names appear across this site and they are not interchangeable. One is the legal person. The other is the product.
- Legal entity
- Sovereign Inc. A Delaware corporation. It is the legal person behind everything published here, and the party to any agreement.
- Jurisdiction
- Delaware, United States.
- Product
- Tunnel Sovereign. The platform, and the name used everywhere on this site when the subject is the technology rather than the company. See the platform overview.
- Category
- Sovereign Communication Authority. An authority plane over secure communication, not another secure messenger.
- Leadership
- Francesco Tripepi, Founder, Chief Executive Officer and architect of the Tunnel Sovereign platform. The company is founder-led, and the person accountable for what this site claims is the person who designed the system it describes.
- Stage
- Available for Controlled Evaluation. Current assurance, verification status, and evidence boundaries are published on Assurance.
- Contact
- Written enquiries reach enterprise@tunnelsovereign.com. Security reports have their own route, on security reporting.
Accountability
One name, and it is on the architecture as well as the company.
The useful question about a company this size is not how many people are in it. It is who answers when a published claim turns out to be wrong, and whether they understand the system well enough to answer properly.
- Accountable for the claims
- Francesco Tripepi. Every capability statement, stated limit and evidence classification on this site is published under his name, including the ones recording what has not been demonstrated. The register is on Assurance.
- In a technical briefing
- An engineer is present. A briefing is a working session on the trust model, the deployment boundary and the evidence behind each claim.
- A security report
- Has a route of its own, published on security reporting. It is an engineering route rather than a support queue.
- Commercial agreements
- Executed by Sovereign Inc. Deployment scope, support and operational responsibilities are governed by that written agreement rather than by this website.
- Company structure
- Founder-led. This page names the roles that are settled, and does not present an executive team, an advisory board or an investor roster.
Messenger and Sovereign
Two planes, and only one of them is new.
Tunnel Messenger is the communication plane: an operating secure messaging application. Tunnel Sovereign is the authority plane that governs whether a communication is permitted at all, from which device, with whom, under which mission, with which capability, and for how long.
Secure messaging protects the communication. Tunnel Sovereign governs the authority to communicate.
Sovereign is not the messenger renamed. It is a separate control plane, developed against the problem the messenger does not address, and it is the product this site is about. Messenger usage is not a Sovereign deployment and is not presented as Sovereign deployment, traction or revenue anywhere on this site or in any material this company issues.
Sovereign systems
Three systems, and one argument about authority.
Sovereign Inc. develops three systems. Each has its own scope and its own evidence, they are licensed and evaluated separately, and only one of them is the subject of this site.
- Verity Command
- Sovereign mission intelligence, decision authority and authorized action. It is a separate platform with its own site: Verity Command.
- Tunnel Sovereign
- Secure communications and governed mission distribution across authorized people, devices, systems and operational environments. The subject of this site.
- QECNet Trust Fabric
- Identity, key lifecycle, policy and trust foundation. It has no public page yet, and is named here rather than linked.
How the two platforms are intended to meet
One decides what is worth sending. The other decides whether it may be received.
Neither holds the other's keys. That separation is the point of the interface, and it is what makes a refusal meaningful rather than cosmetic.
- Verity Command produces governed intelligence, recommendations and authorization decisions.
- The authority layer determines whether a specific action or distribution is permitted.
- Tunnel Sovereign distributes authorized mission information to trusted participants and endpoints.
- An instruction that is invalid, expired, revoked or unauthorized is refused rather than delivered.
- Evidence records the decision and the effect that followed it, including the refusal.
That interface is specified and is not yet operating. The specification is a baseline awaiting ratification, no component of it is deployed, and nothing on this page should be read as describing traffic moving between the two platforms today. Tunnel Sovereign is evaluated on its own capabilities, which are published with their limits on Assurance.
What this page leaves out
The absences are deliberate.
A company page is the easiest place on a website to imply an institution that has yet to exist. This one states what is settled and stops there.
- Customers and deployments
- None is claimed: no customer, contract, pilot, design partner or operational deployment. When one exists and can be named, it will be named here.
- Assurance and approvals
- Certification, accreditation, government operating approval and independent assessment are all open. Each is listed with its current state on Assurance.
- Corporate detail
- Funding, valuation, headcount and facilities are outside what this site publishes.
Working with Sovereign Inc.
The first conversation is a technical one.
An executive security briefing covers the trust model, the deployment boundary and the evidence behind each claim, with an engineer present. A controlled evaluation puts the platform in your own environment under a scope agreed in writing.