nolverostae

I can't give more specific information about my situation, but I would recommend contacting one of the companies that has a public article on the "Wegzugssteuer", for example the one I linked in the first comment. That way you know you get someone that actually knows how to deal with this.

My first tax advisor barely even knew about the Außensteuergesetz and almost got me into larger trouble because of that. I'd guess since this law only affects a tiny portion of the population you really need someone that specializes in it.

If they specialize in it they'll have done this many times before and you can just use their pre-made constructs. Then the main issue is avoiding getting squeezed by them.

You definitely need advice from professionals, yes. All included, I'd expect it to cost 5k€-30k€, but not more.

> You are signing paper that claims you never left Germany!!!

No you aren't. You are signing a paper that says a managerial decision about the shares of the company happened in Germany. Where you live does not matter. You just have to do a board meeting, and be physically present in Germany during the meeting.

In fact, you likely want to keep any proof of your travel from a different country, which makes it obvious to the authorities that you don't spend all your time there.

There's multiple variants though, this is just one of them. You can also pay someone to manage the shares (and of course contractually bind them to not do anything without permission).

Edit: Also, to be clear, you don't need to manage the company from Germany. You only need to manage the holding company from Germany, where the only managerial decision is related to the shares themselves.

It will be interesting to see. Just for completeness, Fastly is not requiring us to BYOIP or anything unless it causes them actual problems, which so far it hasn't. I'm sure they also have other similar businesses to ours so they should have some experience.

I guess I'll see in a while if this was also just a sales tactic from Cloudflare or not.

To (1) - if this was the case, it would have been great if they had talked about it openly or in any way really. To (2) - I do agree that $300 is probably cheap. But I also think that $10k is very expensive, and it seems Fastly agrees.

(3) Mh, I don't think this is doxxing and didn't expect having names would be a big problem. I've just updated the screenshots anyways and censored the names of the representatives.

Cloudflare of course chooses who they want to do business with, but they also pride themselves in being neutral.

I would be very happy to hear Cloudflare's actual side of this. (Or - it would have been great if they had given their side to us before getting into this mess). The only critical information from our side that I'm aware of is that we're a casino with multiple domains - which is why I put that right at the top. But most of the info should be relevant to any business interacting with CF.

I do admit that I originally drafted this article as a "customer support of last resort", since that seems to work well for CF specifically. But it's too late for that anyways by now - the problem is "resolved" by fire and we don't plan to move back.

I purely posted it now as a precautionary tale for other people because of all the pain it has caused us. So the audience is tech people in most companies of small size that will hit more traffic at some point in the future.

This is literally all written communication they gave us. The only other thing was calls. Not calls with anyone that had any knowledge about what any issues were, but calls with sales.

BYOIP is reasonable, though I doubt anyone actually does legislation blocks by IP. Since like half of companies on the internet use Cloudflare or other multi-tenant infrastructure everyone is aware that you can't block an IP address and hit one target. The only thing I've seen is DNS blocks (both DNS protocol directly and based on TLS SNI).

FYI, we also fully block users from the US (due to regulations).

My problem here is mainly the unprofessional communication and huge mess of mixing "compliance" with sales, without giving any clear information or options. And then the removal of our account without warning while we were still talking to them.

I did mention the multiple-domains issue in the post. It would not have been amazing for us to remove our secondary domains, but we would have been very happy to do it if it had resolved the issue. We asked them again and again but they would not give us any detail or options apart from their 120k/year package. Note that BYOIP (which I guess they could reasonably have required to isolate us even if we only use a single domain) is available for a fraction of the cost elswhere (e.g. fastly).

Since we already left Cloudflare the only reason I finished writing this article is to warn others. I think it's still relevant to many companies regardless of what you think of casinos, since very unprofessional sales tactics (unprofessional as in business threatening) seem common place with them. Do look at the linked other posts and comments here from other people affected that don't have anything to do with casinos.

I'm happy to answer questions as well.

We do already fully block the Netherlands since a long time ago since their regulations don't allow us to operate there.

Over 90% of our traffic is cached, since it is static assets. I can look up how much traffic reaches our origin, but the main factor is the number of static files hit. We used Cloudflare Analytics (part of the business plan) to track this, and since it didn't really impact our tech much until now I don't have an exact overview. I mainly know which (uncached) endpoints are hit how much. Fastly is currently saying 15TB per week which seems roughly the same range as Cloudflare's 80TB / month number.

I do encourage you to read the whole article cause there is some fine details in there. The main point is that we were happy to remove any domains apart from our main domain (which gets > 95% of our traffic) but Cloudflare did not give us that option or any other detail on the supposed issue.