See all connected sources
Bring Apple Contacts, iCloud, Google Contacts, Outlook, Exchange, CardDAV, and JMAP-compatible servers into one workspace.
See personal, work, client, and self-hosted contacts together while preserving which account owns each record and which operations that provider supports.
For professionals and families whose contacts are split across personal accounts, employers, cloud providers, and private servers.

When the same person appears in several address books, combining everything into an anonymous list can make editing more dangerous. Cloud Contacts keeps provider names and record ownership visible before you move, repair, or synchronize data.
Bring Apple Contacts, iCloud, Google Contacts, Outlook, Exchange, CardDAV, and JMAP-compatible servers into one workspace.
See the provider behind each record, including concise summaries when a person exists in several sources.
Read, write, group, and synchronization capabilities remain tied to the provider and protocol that support them.
Add the providers and standards-compatible servers you already use.
Filter by source, inspect people that appear more than once, and decide which record is authoritative.
Apply changes to the intended account instead of assuming every connected source behaves the same way.
Cloud Contacts treats a provider as more than an icon. It affects authentication, supported fields, groups, and whether changes can be written back.
Contact lists and details identify the owning providers without hiding multi-provider membership.
Each connected account keeps its own authentication and server configuration.
Unavailable operations should remain unavailable rather than implying that every service supports them.
No. It can provide a unified view while preserving the underlying source of each record. Moving or copying records is a separate user-approved action.
Yes. Cloud Contacts can show that a person exists across multiple sources and summarize the provider names without hiding that ownership.
No. Fields, groups, write-back, and synchronization behavior vary by provider, protocol, permissions, and server implementation.