Hey everyone! We’re super excited to launch our first new endpoint security vendor in quite some time. Phase one of our integration allows you to provision new Threatdown accounts right from within Syncro, and it fully integrates with our new Universal Billing system allowing you to automatically bill your clients on their recurring invoices for their usage, even as that usage changes each month.
For those of you with a Threatdown instance already with another reseller, we also fully support migrating your instance over to Syncro to take advantage of the integration.
Threatdown is providing Syncro customers end-to-end support (including tier-1 support), and there are no minimums or time-based commitments to make. It’s exclusively usage based, and your usage will appear monthly on your Syncro invoice.
I created my account as I’m excited about this option. At least to start with for our residential clients. But when I go to enable Universal Billing it asks for information that I can’t find. I went to integrations and it lists other RMM’s but not Syncro. Is this portion not live yet?
Hey Glen, this is the API credentials you’ll need to create in Threatdown and then add into Syncro. This gives us access to read the usage data so that it works within the Universal Billing framework.
Yep, just tried it with all 3 and I get the same error. Is there a full integration coming where we can deploy Threatdown within policies? Or is this just a billing integration?
Ok great, glad you got it working. Phase 1 is the billing integration, and Phase 2 will consist of deployments through asset policies in Syncro, as well as alerting.
Will there be an opton to deploy Threatdown with a Synco policy? Right now there is an option for Webroot, Ensisoft, Bitdefender, and Windows Defender. If I can create a policy with the Threatdown option for really easy deployment, would be ideal.
Hey Jeff, yes this is part of phase 2 which is looking like end of the year or early next year. For now, we do have a deployment script in our Community Library that can be added into applicable policies as a “setup script.”