# How the ID-Truster ecosystem fits together

> The ID-Truster ecosystem has three parts. One app for your customers, the ID-Truster Hub in the middle, and a ClientDB at your company. See how they connect.

Source: https://idtruster.com/business/how-it-works/architecture/
Language: en

1.  [Business](https://idtruster.com/business/)
2.  [How it works](https://idtruster.com/business/how-it-works/)
3.  How the ID-Truster ecosystem fits together

How it works

The ID-Truster ecosystem has three parts. One app for your customers, the ID-Truster Hub in the middle, and a ClientDB at your company. See how they connect.

Last updatedNovember 13, 2026

Key takeaways

-   The ID-Truster ecosystem has one app for your customers, the ID-Truster Hub in the middle, and a ClientDB for every company.
-   Every company has its own ClientDB, its own systems, and its own key. No company can see another company's data.
-   Your ClientDB contacts the Hub, never the other way around. You do not open any inbound ports in your firewall.
-   The Hub works like a mailbox. It passes messages on and deletes them right away.

On this page

1.  [The three parts](#the-three-parts)
2.  [Many companies, one app](#many-companies-one-app)
3.  [How the parts connect](#how-the-parts-connect)
4.  [The details behind the map](#the-details-behind-the-map)

ID-Truster does not sit between you and your customers. It runs in parallel with the channels you already use, such as phone, email and SMS. It is an ecosystem of three parts that run in different places. This article is the map. It shows the three parts, where each one runs, and how they connect.

## The three parts

-   **The ID-Truster app** is free and runs on your customers’ phones and desktops. It is the same app for every company in the ecosystem, across all industries.
-   **The ID-Truster Hub** is ID-Truster’s central system. It sits in the middle and passes messages between the app and each company’s ClientDB.
-   **ClientDB** runs at each company. It creates, stores, and checks that company’s data, and signs everything it sends with the company’s own key.

Each company connects its CRM and newsletter system to its own ClientDB, and each company’s public key is in its own DNS.

## Many companies, one app

The diagram shows one company. In the ecosystem, many companies stand side by side, each with its own ClientDB, its own systems, and its own key. They all reach the same app through the Hub, and no company can see another company’s data.

## How the parts connect

Your customer data stays with you. What moves through the Hub is a signed signal that tells the app which company is contacting the customer, and the customer’s answer back. The Hub never connects to your systems. Your ClientDB only makes outbound connections. It listens to the Hub for signals addressed to it and picks them up itself, so you do not open any inbound ports in your firewall.

The connection always starts from your ClientDB, never from the Hub. Your ClientDB signs in with an email, a password and a token. On top of that, you create your own Ed25519 connection key and give the Hub only the public part. Every call from your ClientDB is signed with your connection key, and the Hub checks the signature before it accepts the call. The private key never leaves your company. Answers to the app are signed with a second key, your answer key, which the app checks against your DNS.

The Hub works like a mailbox. It knows which app or which ClientDB a signal is for, passes it on, and then deletes it right away. ID-Truster knows nothing about your ClientDB and cannot contact it.

## The details behind the map

Each part of the map has its own article.

-   [Where data is stored](https://idtruster.com/business/how-it-works/data-privacy/) covers where data is created, where it is stored, and what ID-Truster can see.
-   [How data moves through the ecosystem](https://idtruster.com/business/how-it-works/data-flow/) covers what moves through the Hub and what the Hub can read.
-   [How your two signing keys work](https://idtruster.com/business/how-it-works/signature/) covers your connection key and answer key, and why ID-Truster cannot fake an answer from you.
-   [ID-Truster runs alongside your systems](https://idtruster.com/business/how-it-works/parallel-system/) covers what stays the same and what happens if something is down.

## Questions about the ID-Truster ecosystem

-   ### What is the ID-Truster ecosystem?

    It is the free ID-Truster app your customers use, the ID-Truster Hub in the middle, and a ClientDB at every company that uses ID-Truster. Each company connects its own systems to its own ClientDB, and its public key is in its own DNS.

-   ### Does ID-Truster have access to our ClientDB?

    No. Your ClientDB runs self-hosted or in your own Supabase Cloud account. ID-Truster knows nothing about it and cannot contact it. Your ClientDB contacts the ID-Truster Hub, never the other way around.

-   ### Do we need to open ports in our firewall?

    No. Your ClientDB only makes outbound connections to the ID-Truster Hub. Nothing from outside connects to it.

-   ### Who is responsible for the security of our ClientDB?

    You are responsible for the security of the parts you host yourself. If your own systems are compromised, ID-Truster can close your company's access to the ecosystem until you have them under control again.

Ready to join the ID-Truster ecosystem? See what's included in each plan.

[See plans ](https://idtruster.com/business/plans/)

How it works

## More on how it works

-   ### [What a trust code is and how it's built](https://idtruster.com/business/how-it-works/trust-code/)

    What the code contains, when your system creates it, and what your ClientDB stores.

-   ### [How a trust code is verified](https://idtruster.com/business/how-it-works/trust-code-verification/)

    What happens from the moment your customer taps Check until the answer is on screen.
