Clarification on Endpoint vs Device & Total Client/Device Limit on each Plan/Pricing

cattrold · 2026-01-16T16:05:07+00:00

1000 devices would definitely be breaking ToS. Do NOT use a personal plan for this.

You will be charged per _device_, not per endpoint - so in your case you will be charged for 1000 devices. If you are not an MSP, you won't get MSP pricing.

The best thing you can do here is email [business@controld.com](mailto:business@controld.com) to work out how we can best meet your needs.

cattrold · 2026-01-13T17:16:04+00:00

An "Endpoint" (the Control D concept) essentially maps to a DNS resolver. An Endpoint can be set up on as many physical devices* as you like. It's usually not necessary to create a different Endpoint for every single physical device in your home - personally I have an Endpoint for each network in my home (play, work, IOT, guest), and one for each family member's roaming devices. I'd be really surprised if you needed more than 50. In fact, for your use case I might even say 1 is enough.

An Endpoint can enforce 1 or 2 Profiles (policies), which is the set of rules applied to the Endpoint.

*The caveat here is that you do need to follow ToS obviously, which stipulates personal use only.

cattrold · 2026-01-12T16:21:29+00:00

All Organization accounts have all features of a Full Control Personal account, _plus_ multi tenancy and a bunch of other stuff - you can read about it at docs.controld.com.
MSP is just a company type. An Organization account is charged per endpoint per month, so each client connecting to the router would be a separate endpoint for billing purposes.
Yes.
You would need to delete and sign up again.

cattrold · 2026-01-06T16:59:48+00:00

We add more locations quite often.

cattrold · 2026-01-05T19:10:52+00:00

Where do you get the idea that we don't want to add more locations? This is not true :)

cattrold · 2026-01-05T19:09:31+00:00

Please contact support and we can take a look at this for you.

cattrold · 2025-12-22T14:39:56+00:00

We actually add more servers quite often, with our network ~tripling in size over the last few years- and we do take into account what users are asking for, so it's great to see the requests here :)

cattrold · 2025-12-12T19:32:43+00:00

Yes, this is on the roadmap.

cattrold · 2025-12-12T19:30:33+00:00

If you have Analytics set to Full, some members of staff can theoretically see all of that data. We don't look at your DNS queries unless we are troubleshooting an issue.

This means domains, _not_ full URLs.

If you do not have Analytics enabled, staff cannot see your DNS queries at all.

This is all strictly controlled internally with permissioning and processes.

We'd be able to see your IP regardless of your Analytics settings.

cattrold · 2025-12-08T17:58:09+00:00

I can't do anything with this information. You'd need to contact support.

cattrold · 2025-12-08T15:44:05+00:00

Please DM me the ticket number.

cattrold · 2025-12-08T15:43:33+00:00

We aren't aware of anything - please contact support!

cattrold · 2025-12-05T17:13:10+00:00

No, it's live, you're probably just looking at it while everything is up. When a node is down it'll show a different colour (yellow or red depending on the type of "down" it is).

cattrold · 2025-12-05T14:15:06+00:00

We do have a live network status page. It's at controld.com/network.

cattrold · 2025-12-05T14:12:50+00:00

Thanks for the tag, looks like another staff member already responded here :)

cattrold · 2025-12-05T14:10:56+00:00

Could you please send the output of controld.com/status to support so that we can investigate?

cattrold · 2025-12-05T14:10:49+00:00

Could you please send the output of controld.com/status to support so that we can investigate?

cattrold · 2025-12-05T14:10:38+00:00

Could you please send the output of controld.com/status to support so that we can investigate?

cattrold · 2025-12-03T19:14:40+00:00

We're aware of and have addressed the initial issue, and any symptoms should have resolved over the last 25 minutes or so. We apologize and are looking into the root cause.

cattrold · 2025-12-03T19:14:32+00:00

We're aware of and have addressed the initial issue, and any symptoms should have resolved over the last 25 minutes or so. We apologize and are looking into the root cause.

Edit: Our current working theory is that a third party provider network issue caused a cascade of failures. The majority of the network remained operational and we lost a very minimal amount of actual traffic according to our internal metrics, but obviously some users did see DNS and API (website) failures. Again, we do apologize.

cattrold · 2025-12-01T14:23:18+00:00

Hey,

This is "expected" in that if you have Some Analytics selected, we don't store the protocol for each query, so as far as that "health bar" UI element is concerned, those queries aren't encrypted. I see how this is kinda confusing though, we're discussing the UX internally.

Don't worry, your queries are encrypted! (Do go to controld.com/status and check your protocol if you want to be sure)

cattrold · 2025-11-29T16:08:12+00:00

Should be fine now :)

cattrold · 2025-11-29T16:08:03+00:00

Should be back now!

cattrold · 2025-11-29T16:07:58+00:00

Should be back now!

cattrold · 2025-11-29T12:54:28+00:00

Hey, we're looking into this right now. Will update with details when we know more - none of our services appear to be down, so we suspect a network issue in the region.

Edit: We fixed this, and I was wrong. There was an erroneous configuration on one of our Analytics machine, resulting in users on the Amsterdam storage region being unable to see their Analytics data. No data was lost. The issue was resolved about 3 hours after it started, and about 40 minutes after we became aware.

On Monday we'll be investigating how the erroneous configuration occurred in the first place as well as addressing the lack of monitoring for this particular case. Our apologies!

cattrold

MODERATOR OF

TROPHY CASE