We Are Now MeteoreBot — and the old domain had to go
If you arrived here from meteorabot.com, that redirect is permanent. The engine is the same, the team is the same, your account, wallet, positions and history are the same. What changed is the name on the door — and the reason is not marketing. We retired the old domain because it had drifted into a legal position we were no longer willing to sit in, and the cleanest way out was not to patch it but to leave it behind entirely.
This is the least fun post we have written. It is also the most important one, so we would rather explain it properly than bury it in a changelog line.
The short version
Ang meteorabot.com domain had been reaching, and being used from, jurisdictions where we are not permitted to offer this product. That reach was not something we sought. It accumulated quietly, over months, through search, syndication and word of mouth.
Once we understood the size of it, we took advice, and the advice was unambiguous: the exposure was attached to the domain and its history, not to the software. So the domain is gone. meteorebot.com is the only address we operate now.
How a domain quietly becomes a liability
Nobody sets out to operate somewhere they are not allowed to. The way it actually happens is much more boring than that, and that is precisely what makes it dangerous.
You build a product. It works. People write about it. Search engines index it in languages you never targeted. Aggregators list it. Someone posts it in a forum in a country you have never thought about, and that thread ranks for two years. Traffic arrives. Some of it converts. None of it announced itself. By the time the pattern is visible in your own analytics, you are not looking at a marketing opportunity — you are looking at a compliance footprint, and it has your domain name written all over it.
The uncomfortable part is that intent is a weak defence. In most of the regimes that matter here, the test is not "did you mean to serve this market." It is closer to "was your service available to it, and did you benefit." A domain that has been reachable, indexed, and transacting in a restricted jurisdiction for an extended period is not a clean thing to hold, however honourable the intentions behind it.
What we could have done
Bolt geo-blocking onto the existing domain, keep the name, keep the SEO, and hope that a clean forward-looking record outweighs a messy backward-looking one.
What we actually did
Walked away from the domain, its history, its index and its backlinks — and rebuilt the brand on an address with no legacy attached to it at all.
Option one is cheaper by every commercial measure. It is also the option where, two years from now, someone gets to point at a continuous chain of activity under one name and ask what exactly changed. Option two costs us years of accumulated search authority and a name people already knew. We chose the expensive one on purpose.
The bullets we dodged
We want to be careful here, because this is the part where companies either overshare and regret it or say nothing and look evasive. We are going to describe the categories of risk we were carrying, and not speculate about any particular authority, because speculating publicly about regulators you have not heard from is its own kind of stupidity.
What sat on the table was some combination of the following:
Unlicensed-offering exposure. Making an automated trading product reachable in a market that requires authorisation to offer it. This is the headline risk and it does not care how the traffic found you.
Payment and banking fallout. Processors and banks are far less interested in nuance than regulators are. A single restricted-jurisdiction flag can end an account relationship in a week, with funds frozen while it is sorted out.
Domain-level seizure and blocking. Domains get seized, and they get blocked at the national level. Either outcome takes your users' bookmarks, your email and your entire search presence with it, without warning.
Director and personal liability. In several of the relevant regimes this does not stop at the corporate entity. That is not an abstraction to the people who run this.
Retroactive reach. The one that actually decided it. Cleaning up today does not clean up the eighteen months behind you if you are still standing on the same domain, using the same name, serving the same users.
None of these landed. No account was frozen, no domain was seized, nothing was served on us. That is the entire point. We would much rather write this post than the other one.
What actually changed
Practically speaking, less than you would think — which is why we could move fast.
- The domain. Everything lives at meteorebot.com. The old address permanently redirects here and will keep doing so.
- Access controls. Restricted jurisdictions are enforced at the edge now, before a request ever reaches the application, rather than as a checkbox in a terms page nobody reads.
- A clean record. The new domain starts with no history, and that history now begins with controls already in place rather than bolted on afterwards.
- Nothing about the engine. Same models, same ensemble, same execution path, same code. This was never a product problem.
- Nothing about your account. Your wallet, balance, open positions, trade history and settings carried over untouched. There is nothing you need to migrate.
What you should do
Update your bookmark to https://meteorebot.com. That is genuinely the whole list.
And keep reading it carefully. A rebrand is exactly the moment impersonators wait for — a period where users have been told the name changed and are therefore primed to accept a second change from someone who is not us. We will never announce a new domain by DM, Telegram, Discord or email. See Mag-ingat sa mga Copycat.
Why we are telling you at all
We could have moved the domain in the night and let the redirect speak for itself. Plenty of companies do. The reason we are not doing that is straightforward: you are trusting this platform with a funded wallet and an automated strategy. A user who notices the name changed and cannot find a single word about why is a user who is entirely correct to assume the worst.
So: the name changed because we were carrying legal exposure we did not want, we acted on it before it turned into anything, and the cost of acting was a name and a decade of search authority. We think that is a trade worth making, and we would make it again.
Our counsel has asked us to keep specific jurisdictions and correspondence out of a public post, which we think is reasonable. If you are a partner, processor or counterparty who needs more detail than this, contact us directly at meteorebot.com/contact and we will handle it properly.