The best way to describe a TidWiT instance is basically to think of it as a license of the TidWiT platform with a certain set of features. Since TidWiT is offered as a SAAS (Software as a Service), an instance could be turned on at any time with no need to install any hardware or software.
Any organization wishing to publish content and distribute it more effectively through its channel would start by getting a TidWiT instance. Any partner wishing to dynamically syndicate this organization’s content libraries or apps would have to get an instance of their own.
The features that come with a TidWiT instance depend on the edition or options purchased with that instance. For example, Commerce as a feature is an add-on to a TidWiT Exterprise instance. For a more complete discussion on edition features and pricing, see Pricing and Billing FAQ.
The cost of a TidWiT instance depends on what edition and which add-on features are chosen. Since TidWiT is provided as a SAAS (Software-As-A-Service), it is usually billed on monthly, quarterly, or annual basis (See Pricing and Billing FAQ for more information on topic)
A TidWiT instance can be turned on in a matter of minutes and it would go live instantly.
Different scenarios exist for deploying multiple instances. The most obvious being an organization launching multiple instances to cater to different content needs of diverse audiences. For example, an organization can launch one instance specific to the content needs of its internal sales. It could launch another to meet the needs of its channel partners, another for consumers, and another for business customers. In the case of corporate customers, an organization can launch multiple instances if it wishes to share valuable information with each of them. In this case, TidWiT allows that each launched instance could be branded to each corporate customer as a value-add.
Yes, syndicated content can flow through to multiple instances dynamically and seamlessly from the parent organization’s instance. This said, while instances may have some overlapping content, each instance can have its own content.
With TidWiT, libraries can be dynamically syndicated between two or more instances in a matter of minutes.
There is no limit for how many TidWiT instances an organization can launch.
Yes, it’s done through content syndication (See topic of Content Syndication for more information). The instance would have the look and feel of the partner, whereas the content would be your content.
Yes, it’s done through content syndication (See topic of Content Syndication for more information). This is one of the most important features of TidWiT, as it saves time and cost involved with manual uploading of content by a partner.
An instance is the actual license of the TidWiT platform, whereas a channel refers to the content that can be shared between two or more instances. For example, for two partners to share content, they must first each launch a TidWiT instance. Once the instances are launched, they can connect and start sharing content channels between each other.
Once an instance is turned off, it will no longer be available for online access. However, content and data will be maintained for 30 days free of charge, after which time it will be discarded.