Hi Fly team,
I’m Mario Uher, CTO at https://tagbase.io. We’ve been running our production workloads on Fly since February 2024 and just finished a refactor that extracts
our Verify product — the consumer-facing authenticity check for our NFC tags — into its own service. I’d like to deploy it as two new apps (using a xxx-verify
/ xxx-verify-staging shape), but both are blocked by the abuse filter:
▎ Name blocked by abuse filter. verify is a common phishing target, please select a new app name that doesn’t contain verify.
I get the reasoning — verify is a classic phishing target — and support has been great walking me through it. But any name containing “verify” is blocked, and
our product is called Verify. Any alternative would be a layer of abstraction between our codebase (where everything is named verify) and our deployed app
names — exactly the kind of accidental complexity we just spent a refactor removing.
Fly is all about DX, and getting these two names would just be really nice DX. Could we get an exemption for our org?
Happy to share the actual app names privately with support, along with whatever verification you need.
Thanks,
Mario
