Some things to consider:
- we built Sync'Em with the intent of using it as a base to meet custom requirements
- we can deliver a "branded" version for your organization
- as a development organization, we are experienced contractors
- as a business, we have both licensed and sold intellectual property
- Sync'Em is designed to be portable — only the user interface is done in platform-specific code
- Sync'Em has the underlying architecture to support server-to-server syncing
- easily add infrastructure to sync your Exchange server's information to another server for disaster recovery
- provide your users with Exchange integration without adding infrastructure — even if your company is small and uses an Exchange service provider
- Sync'Em is not limited to syncing only contact and calendaring types of information sources
- Sync'Em has been carefully architected (led by someone who knows software architecture) to abstract and encapsulate the underlying "end-points"
- Sync'Em can support any kind of data source (e.g., a filesystem, a database) where there's an interface that allows determining changes and retrieving the changed items
Features at a glance:
- highly flexible underlying software architecture
- extensive feature-set and configurability
- sophisticated but easy-to-use conflict resolution
- does not rely upon OS X's Sync Services engine for syncing ('though iCal and Address Book are accessed via Sync Services)
- all syncing is via direct connection — no external "sync hosting" involved
- employs an ultra-friendly non-intrusive error-reporting model
We've been delivering Mac and cross-platform applications for over 5 years. We use the latest technologies, standard operating-system interfaces and conform to industry standards so our software, like the Mac, generally "just works."
The following, excerpted from the Business Contexts of our software requirements (Use Cases), provides an overview of the basic Sync'Em concepts.
When a User wants to use Sync'Em to keep various sources of information in sync, the User must specify which information sources are to be synchronized with which other information sources, the place where each such information resides, any credentials required to access each source of information, the schedule for synchronizing the sources of information and, if applicable, which subset of each such information is to be included in the synchronization.