Hi Railway Trust & Safety team,

My workspace codeCave was restricted today (workspace owner: conradocanas@gmail.com), apparently by an automated risk flag. I'm a paying customer running live production applications for real clients, and I'd like to resolve this quickly and bring my workloads fully within your Acceptable Use Policy.

What runs here: the large majority is standard SaaS — Nuxt web apps + managed Postgres serving real client products (e.g. the Hub project = hub.codecave.ar, and the MVPs project hosting several live apps: a sports-booking platform, a medical-shifts platform, an events site, and others). These are ordinary web + database workloads.

Being transparent about the likely trigger: I also run a few scheduled data-collection jobs (B2B lead-gen and public real-estate listing aggregation) that make periodic outbound requests. I understand bursty egress on shared IPs can resemble abuse signatures. These are not proxies, anonymization services, crypto miners, or compute resellers — they collect publicly available business data at low volume. I've stopped them and will keep them off pending your review. I'm glad to add identifying contact info to the User-Agent, respect robots.txt, rate-limit egress, or move any borderline component to an official API / off-platform — whatever you need.

Two requests:

1. Please reinstate the workspace so my clients' production apps come back online; or
2. If reinstatement needs review time, please grant a temporary read-only / data-export window (or briefly start my Postgres services) so I can take database dumps — my Postgres volumes are intact and I simply need a short window to pg_dump them.

Happy to provide anything that helps you verify — invoices, the live client URLs, project IDs.

Thank you for taking a look.

Conrado Cañas · codeCave · conradocanas@gmail.com