What are Products

If you click on the Billing section, you will see something like this.

This section allows you to:

1. Add a billing method and see subscription state (not pictured above)
2. Increase/decrease the number of billable User and Router products
3. View your invoices

Limits

Whatever the amount of User and Router devices you choose here is what your global account limit will be. This limit includes the sum of all User or Router type devices within the primary Organization as well as all Sub-Organizations (if any). For example, if you have 500 Users as the limit, you can spread this limit as you see fit.

• Primary Organization uses all 500, and has no Sub-Organizations
• Primary Organization uses 100, and each of the 4 Sub-Organizations also has a limit of 100
• Primary Organization uses 0, and 10 Sub-Organizations have a limit of 50

Essentially, you commit to a set number of seats and can allocate them any way you see fit, within the primary Organization or child Sub-Organizations. The primary Organization is responsible for the billing with Control D. How you choose to bill your Sub-Organizations (if you do) is up to you.

🚧

Overcommit Devices

Control D will allow you to temporarily go over your pre-selected limits in order to create Devices within your sub-organization not to disrupt work flows. You will then be greeted with a scary yet polite warning message prompting you to increase your billable limits.

Users vs Routers

You may be wondering what the best (most affordable) way to deploy Control D is, and whether you should leverage cheaper "User Devices" or more expensive "Router Devices". The answer depends on your situation and how granular you want your filtering to be. Here is a quick comparison an a few example scenarios.

Many people, same rules

You have a handful of sites or networks, each one having a 0-50 LAN clients. Everyone on each network is subject to the same filtering policy (Profile). Deploy a "Router Device" on each site/network, default pricing applies.

If your networks are bigger than ~50 clients, contact us and we'll setup custom pricing specific to your needs.

Many people, different rules

In this scenario, you may have a single site/network, or multiple, with different types of end-users. One such example could be a school with a student body and staff. The student body could be further sub-divided into pre-teens and teenagers so you may require at least 3 different Profiles (policies).

Deployments in this scenario can vary, but this is one way you can do it, which would require 3 Router Devices.

• Pre-teen students / vlan100: Device 1 - Enforces the most restrictive Profile.
• Teenage students / vlan200: Device 2 - Enforces a less restrictive Profile
• Staff / vlan300: Device 3 - Enforces least restrictive Profile

Larger networks require custom per Router pricing, please contact us.

Control all end-points, on any network

In this scenario you may not want to deploy Control D on an entire network, but rather directly on some (or all) end-user physical devices. This provides for the most granular level of control over each individual user owned device, and makes Control D work on every single the device is taken to. Simply deploy a "User Device" on each physical gadget such a laptop, tablet or mobile phone. This can be achieved manually, through RMM, or self-onboarded by the end user.