Claude Code helps move Railway services to Dokploy
@cleeeeeeeeement moved services from Railway to Dokploy on Hetzner with Claude Code doing the heavy lifting. A migration in 2 hours is reported by the poster; the post supplies a short infrastructure playbook, not a security audit.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Plan a migration of [services] from Railway to Dokploy on [VPS]. Inventory dependencies, secrets and data before changing anything. Propose access controls, backups, rollback and verification checks for my approval, then work only within the permissions I grant.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @cleeeeeeeeement
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Services moved from Railway to Dokploy on a Hetzner VPS in 2 hours, reported by the poster. No independent uptime or security verification is provided.
- Human involvement
- The poster selected the move and describes the infrastructure playbook. Exact permissions, deployment approvals and post-migration tests are not reported.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The poster chose to leave Railway following a notice they describe as requiring key rotation.
- The shared playbook starts with renting a VPS and locking down access before installing Dokploy.
- Applications are containerised for the move; Claude Code did the migration heavy lifting, reported by the poster.
@cleeeeeeeeement describes moving all of their services from Railway to Dokploy on Hetzner, with Claude Code doing the heavy lifting. The move took "2 hours", reported by the poster. The account frames the decision around a notice telling the user to rotate keys after malicious activity; that notice is the poster’s account, not an independently established provider incident.
The published playbook starts with renting a VPS and locking down access, followed by installing Dokploy and containerising applications. Claude Code is explicitly identified as the tool used for the migration. The source does not provide a command log, an application inventory or a detailed division of each infrastructure step between the person and the agent. It therefore supports an agent-assisted move, not a claim that every security and deployment decision was delegated without supervision.
The poster’s broader point is that readable logs, machine-accessible interfaces and control over the server matter more to an agent than a hosting dashboard’s appearance. The post also recommends centralising secrets in a vault, but does not establish that this was completed during the migration. Successful service transfer is reported by the poster; independent uptime, security validation and longer-term maintenance costs are not supplied.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @cleeeeeeeeement
Frequently asked questions
What infrastructure did the poster move to?
The post identifies Dokploy on a Hetzner VPS, with Claude Code doing the migration heavy lifting.
What migration method does the source describe?
Its short playbook covers renting a VPS, locking down access, installing Dokploy and containerising applications. It does not show a complete execution log.
Does the post establish a security incident or audited result?
No. The key-rotation notice and completed move are reported by the poster. The account is not independent evidence about the provider incident or the new server’s security.
More details
About this account
Claude Code performed the migration heavy lifting, reported by the poster; the source does not identify every autonomous action or provide an execution trace.
Written post and bio checked via public FxTwitter mirror. Results reported by the poster, not independently reproduced. The provider notice is attributed, not verified. Vault use is advice, not a demonstrated completed step. Suggested prompt is editorial, not an original quotation.
Credit: @cleeeeeeeeement
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Railway · Dokploy · Hetzner
Hosting migration · VPS · Self-hosting
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.