Monday morning, a client-data login page showed an unfamiliar device

I used to keep client records, project files, and collaboration notes on one cloud platform because it was convenient. Then a security incident made me realize something: saving a few dozen yuan a month does not save the communication and recovery time that follow.

When I am handling contracts, quotes, or client lists, I no longer rush to buy a bigger plan. First, I clarify who can get in, what they can see, and what we do if something goes wrong.

What the Railway incident really taught me was not to hunt for a button

Railway is a cloud platform development company. It published a fairly detailed incident review, saying attackers may have exploited an AI model without security restrictions, prompting the company to strengthen its defenses. For a small team like mine, the useful lesson is not to rely only on the platform’s protection. I also need to check my own accounts, permissions, and backups.

My friend Chen Xin, an independent development consultant in Hangzhou, shared client files differently in March 2025. Instead of giving everyone permanent access, she created temporary access links and logged each download. She told me: “I am not more technical. I just never wanted to ask a client again, ‘Can you send me that contract we discussed last time?’” For someone just starting out, that approach fits better than simply buying security services.

What would it cost me to replicate this today?

The starting budget can be zero: check login verification, access logs, and recovery options on the platforms I already use, then make an offline backup of the most important client files. The time investment is 60–90 minutes. The technical barrier is being able to understand a web page’s login, permissions, and download settings; I do not need to write code. The first step is to open my cloud platform’s dashboard, find “Account Security” or “Login Settings,” and confirm that my email address and phone number still work.

If a platform offers extra protection, I would compare plans costing a few dozen to several hundred yuan per month. There is no need to upgrade right now. First, I complete the backup, permissions, and recovery process. I made the same mistake before: I merely labeled a file “final version” without preserving the actual history, so I still panicked when something went wrong.

I take it step by step, depending on my stage

When I am just starting, I do two things first: add login verification to my main accounts and copy my most important client records somewhere else.

When I have one or two clients, I set expiration dates or separate permissions for shared files, agree to revoke access when the project ends, and note the last update time for each record.

When I start scaling, I put account handoffs, permission reviews, and incident contacts into a fixed process, so the team can still retrieve files after someone leaves. More complex security tools are not necessary for everyone. I evaluate them seriously only when I actually face multi-person collaboration or compliance requirements.